TIBCO Foresight Products s and Troubleshooting July 2013 Two-second advantage
Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE. USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN LICENSE.PDF) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE LICENSE FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME. This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc. TIB, TIBCO, TIBCO Adapter, Predictive Business, Information Bus, The Power of Now, TIBCO ActiveMatrix BusinessWorks, TIBCO Foresight Archive and Retrieval System, TIBCO Foresight BI Bridge - BAM Extract, TIBCO Foresight Instream, TIBCO Foresight Operational Monitor, TIBCO Foresight Transaction Insight, and TIBCO Foresight Translator are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries. EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only. THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README.TXT FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM. THIS DOCUMENT IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON- INFRINGEMENT. THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME. THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES. Please see Licensing_Foresight_Products.pdf for licensing details. Copyright 1999-2013 TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Contact Information TIBCO Software Inc., Foresight Group 655 Metro Place South Suite 900 Dublin OH 43017 Phone: (614) 791-1600 Fax: (614) 791-1609 Web: http://foresight.tibco.com/ E-mail: FSSupport@TIBCO.com
Contents Seeing s... 2 Virus Checking and Foresight Products... 2 Archive... 2 Automator... 3 BI Bridge... 3 DataSwapper... 4 Document Splitter... 5 Foresight Service... 6 Instream Validation... 7 ICDAnnotator... 8 ISErrors... 9 ISIserver... 10 OpMon... 10 ReportMailer... 10 Response Generator... 11 ScenarioDetector... 12 Shuffler... 13 TI AlertProcessor... 13 TI Importer... 14 TIMatcher... 15 TI Purge... 15 TIUtilities... 16 TI Web Portal... 17 TPARouter... 18 Translator... 19 ValidationHighlighter... 20 s and Troubleshooting Page i 7/25/2013
Seeing s To display return codes when you run a script, put this line similar to this in the script right after running the program: UNIX echo "return code = " $? Windows @echo [ = %ERRORLEVEL%] This returns something like: [=100] Virus Checking and Foresight Products Exclude all TIBCO Foresight workflow subdirectories from virus checking. AlertProcessor AlertProcessor does not send return codes. If the program returns any value, it is assigned by the.net runtime. Archive (TIBCO Foresight Archive and Retrieval System) 100 Archive ran successfully. not 100 Archive did not run successfully. It will catch the thrown exception in the main entry routine, print the exception to its log, and then throw the exception to the JVM. This usually results in a 0 being returned by the JVM. Archiver.log Application log Web Service log Studio Workflow In Archive s Bin directory. Default location is Archive s Bin\Logs directory. Default location is Archive s Bin\log directory. The Archiver component has a LoggingDir property to specify the location of the log files. Also, look in the workflow s Logs directory. See Logging in ArchiveSystemsnnn.pdf. s and Troubleshooting Page 2 7/25/2013
Automator none From Foresight Studio From Command Line or ForesightService Log has the workflow name and is under the system. Example: C:\Foresight\Systems\InStreamDemoSystem\AutomatorLogs\1.0 As specified by -l command line parameter. -l without a path puts it under the workflow. Example: C:\Foresight\Systems\InStreamDemoSystem\Workflows\1.0\ InStreamDemoWorkflow\Logs See Log Files in Automator.pdf. BI Bridge (TIBCO Foresight BI Bridge - BAM Extract) none Log file Specified in LoggingConfig.txt. See Setting Up Logging in BI_Bridge.pdf. s and Troubleshooting Page 3 7/25/2013
DataSwapper FSDXSUCCESS 100 Dataswapper ran successfully. FSDXFAILED 110 Dataswapper did not run successfully. FSDXLIBFAILED 150 Dataswapper did not run successfully because it could not load one of its internal libraries. This is probably an installation problem. Contact TIBCO Foresight Technical Support. FSDXINITFAILED 180 Dataswapper did not run successfully because of a problem other than those listed below. Contact TIBCO Foresight Technical Support. FSDXEDIINPUT 200 Dataswapper could not access the EDI input file. FSDXEDIOUTPUT 201 Dataswapper could not open the EDI output file. FSDXINSTREAMINPUT 202 Dataswapper could not open the TIBCO Foresight Instream detail file. FSDXREPORT 203 Dataswapper could not open the report file. FSDXINIINPUT 205 Dataswapper could not open the INI configuration file. FSDXNOFINDKEY 206 Dataswapper could not locate a key for Replacement. FSDXBADMATCH 207 Dataswapper failed. The detail and EDI input files seem to mismatch. The segment for the replacement was not found in the expected location. Audit report Validation detail results file Use -r command-line parameter to specify the audit report file. Use ProcessRecord setup file parameter. Look for Dataswapper records: SBST, SBSTD, SBSTF, SBSTI, SBSTR. See Dataswapper.pdf. s and Troubleshooting Page 4 7/25/2013
Document Splitter FSDSSUCCESS 100 Docsplitter ran successfully. FSDSFAILED 110 Docsplitter did not run successfully. FSDSLIBFAILED 150 Docsplitter did not run successfully because it could not load one of its internal libraries. This is probably an installation problem. Contact TIBCO Foresight Technical Support. FSDSINITFAILED 180 Docsplitter did not run successfully because of a problem other than those listed below. Contact TIBCO Foresight Technical Support. DOCSP_FAILED 185 When running validation, Docsplitter, and Response Generator together in the API, Docsplitter failed. RESGEN_FAILED 186 When running validation, Docsplitter, and Response Generator together in the API, Response Generator failed. DOCSP_RESGEN_FAILED 187 When running validation, Docsplitter, and Response Generator together in the API, Docsplitter and Response Generator both failed. FSDSEDIINPUT 200 Docsplitter could not access the EDI input file. Binary data was encountered in the EDI input file. Bad segment tag or other document structure problem. FSDSEDIOUTPUT 201 Docsplitter could not open the EDI output file. FSDSINSTREAMINPUT 202 Docsplitter could not open the Instream detail file. FSDSREPORT 203 Docsplitter could not open the report file. FSDS997INPUT 204 Docsplitter could not open the input 997 file. FSDSINIINPUT 205 Docsplitter could not open the INI config file. Debug file Report file Content splitting map Splitting tree Use -b command-line parameter to specify a debug report. Use DebugOutputtoFile=1 setup file parameter. Use -r command-line parameter to specify the report. Use this in the setup file to see what values caused splitting: [Debugging] Content=1 Use this in the setup file to see what content went to each output file: [Debugging] TreeFinal =1 See DocumentSplitterTechnicalManual.pdf. s and Troubleshooting Page 5 7/25/2013
Foresight Service none Windows Event Viewer 1. Open Control Panel Administrative Tools Event Viewer System Log. 2. Double-click on each of the ForesightService lines created at the appropriate date and time. 3. See if the Description area shows the path to the FSService.ini file it is trying to open, and the command line it is trying to run. This will be the main way to troubleshoot startup problems. Windows Task Manager After startup, start Task Manager to see if the specified executable (usually ForesightAutomator.exe) has been started. If you see the executable in the task list, it has started and is running. See ForesightService.pdf. s and Troubleshooting Page 6 7/25/2013
Instream Validation (TIBCO Foresight Instream) 100 Validation ran successfully. 110 Validation did not run successfully. The command line syntax is incorrect. 112 A JNI EXECPTION was encountered when using the Java API. 120 There was a problem loading HVInStream.DLL library. 129 $dir.ini or fsdir.ini was found but cannot be opened. 130 There was a problem with initialization of the validation engine caused by a setup problem (i.e. registry setup error) or $dir.ini or fsdir.ini is missing or contains invalid paths. 131 $dir.ini or fsdir.ini cannot be found. 132 Cannot access the "BASEROOT" specified in the $dir.ini or fsdir.ini. 133 Cannot access the Database directory. 134 Generic failure to read ini settings. 140 A critical error prevented Validation from running successfully. 150 Cannot find or open FS_HIPAA.dat in the Bin directory. 160 Deprecated. Exceeded maximum allowable threads (only when using API for validation). 170 Deprecated. Exceeded maximum allowable processors (only when using API for validation). 180 The activity was cancelled by the user (when using API). 185 When running validation, Docsplitter, and Response Generator together from an API, Docsplitter failed. 186 When running validation, Docsplitter, and Response Generator together from an API, Response Generator failed. 187 When running validation, Docsplitter, and Response Generator together from an API, Response Generator and Docsplitter both failed. 188 DataSwapper failed when run from an API. 191 A critical trading partner automation error prevented Validation from running successfully. For more information, see *.TA1 in the same directory as the validation detail results file. 195 Cannot find the error message file. Check the [ErrMsgFile] of your $dir.ini or fsdir.ini file. 200 Configuration path error when using the -c command-line parameter. 201 The input file could not be accessed. Check filenames and paths. Put quotes around paths that contain spaces. 202 Output file could not be opened. Check filenames and paths. Put quotes around paths that contain spaces. s and Troubleshooting Page 7 7/25/2013
Validation detail results file TA1 file Report file Check GEN records. Check for EMSG records near the top. Look for a TA1 file if no guideline is specified. Use -r command-line parameter. See InstreamValidationTechnicalManual.pdf. ICDAnnotator 0 No problems found 1 Bad command line argument 2 File does not exist 3 Could not read from file 4 Could not write to file 5 Not an Instream results file 6 Database communication error 7 Configuration information invalid 99 Unexpected error occurred log Specified with -log and -v command-line parameters. Default: value from -r command-line parameter plus.tiicdannotator.log These parameters (-log, -v, and r) are not available in a configuration file. s and Troubleshooting Page 8 7/25/2013
ISErrors -d echoes the return code to the screen. 0 No errors matched the criteria. 1 An error matched the criteria. (ISErrors stops after finding one error that matches the criteria). 11 Setup problems such as parsing the config file. ShowAllDTLRecords ShowOnlyMatchingDTLRecord Configuration file entries that control amount of output to the screen. See ISErrors.pdf. s and Troubleshooting Page 9 7/25/2013
ISIserver none Server_n_log.txt Server_Thread_n_n_log.txt Screen display fslog directory under ISIserver s high-level directory. fslog directory under ISIserver s high-level directory. Set Display=ON in the [Server] section of ISIserver.config. See ISIServer.pdf. OpMon (TIBCO Foresight Operational Monitor) none Log file OMProcessor.log in Foresight Operational Monitor s root directory. See OperationalMonitorAdminnnn.pdf ReportMailer 100 Success 201 Invalid parameters 202 Invalid message body file 203 Send failure 204 Internal error See Reportmailer.pdf s and Troubleshooting Page 10 7/25/2013
Response Generator 100 Response generation succeeded. 110 Response generation failed. 180 Failed to initialize Response Generator. 185 When running validation, Docsplitter, and Response Generator together in the API, Docsplitter failed. 186 When running validation, Docsplitter, and Response Generator together in the API, Response Generator failed. 187 When running validation, Docsplitter, and Response Generator together in the API, Docsplitter and Response Generator both failed. 201 Could not open input file. 202 Could not open one or more output files. 203 Could not open the template file. 204 Requested an inappropriate response document for your original document, such as: If a 997 is requested for an incoming 997 If an 824 is requested for an incoming 824 or 997 If a 277 is requested for any document type other than an 837. 205 STRUS and STRUE records in detail file are mismatched. This can occur when ISA-IEA, GS-GE, and ST-SE segments are not paired properly. Also, be sure that you are using STRUS=1 and STRUE=1 in the validation profile (APF) to create STRUS and STRUE records in the validation detail file. 206 Could not open the specified file; the file either doesn t exist or can t be opened. Check the file for read access permission. Response generator failed. See ResponseGeneratorTechnicalManual.pdf. s and Troubleshooting Page 11 7/25/2013
ScenarioDetector 0 No problems found 1 Bad command line argument 2 File does not exist 3 Could not read from file 4 Could not write to file 5 Not an Instream results file 6 Database communication error 7 Configuration information invalid 8 Condition count does not match Z-record flag count 99 Unexpected error occurred log Specified with -log and -loglevel command-line parameters. Default: value from -in command-line parameter plus.scenariodetector.log These parameters (-log, -loglevel, and -in) are not available in a configuration file. s and Troubleshooting Page 12 7/25/2013
Shuffler 100 Success. The command executed successfully. 0 Parameter error. One or more of the parameters have been entered incorrectly. 1 Failed to access root directory. The specified root directory could not be accessed. Check filenames and paths. Put quotes around paths that contain spaces. 2 STC default file name failed. The default STC file could not be read. 3 Access input file failed. The input data file could not be accessed. Check filenames and paths. Put quotes around paths that contain spaces. 4 Access result file failed. The validation results file could not be accessed. Check filenames and paths. Put quotes around paths that contain spaces. 5 STC file name failed. The STC file name specified with the t option could not be found. Check filenames and paths. Put quotes around paths that contain spaces. 6 Read input file failed. The input data file could not be read. Check filenames and paths. Put quotes around paths that contain spaces. 7 Open output file failed. The validation detail output file could not be opened. Check filenames and paths. Put quotes around paths that contain spaces. 8 Open result file failed. The results file could not be opened. Check filenames and paths. Put quotes around paths that contain spaces. See Shuffler.pdf. TI AlertProcessor (TIBCO Foresight Transaction Insight - AlertProcessor) none Event log You can see some AlertProcessor events under Common Administration s Settings Event Log. s and Troubleshooting Page 13 7/25/2013
TI Importer 0 Importer ran successfully. 1 Problems with the command line parameters. 2 Could not find the input file. 3 Error parsing INI file. 5 Error processing transaction filter. 10 SQL error. 20 Could not find standard name in result file. 21 Unknown standard found in result file. 25 Guideline not based on guidelineplus. 30 Error parsing EDI. 35 Could not read error message translation file. 40 Could not load the Oracle library. 45 User pressed <Ctrl>-C or <Ctrl>-<break>. 50 Unknown error. Contact Foresight Technical Support. log Specified with -l command-line parameter or logfilename setting in Importer.ini. Default: Importer.log in the directory containing Importer.exe. See Importer.pdf. s and Troubleshooting Page 14 7/25/2013
TIMatcher TT TT 0 Successfully completed. 1 Invalid argument. 2 File not found. 3 File already processed. 4 Invalid file (doesn't look like an Instream results file). 5 File not imported into the Transaction Insight database yet. 6 FSUID not found. 7 Database error. 8 Configuration error. 9 Unable to open the log file. 99 Unknown. log file Specified with -log command-line parameter. See TIMatcher.pdf. TI Purge none Log file Specified in LoggingConfig.txt. See TIPurge.pdf. s and Troubleshooting Page 15 7/25/2013
TIUtilities TT TT 0 TIUtilities ran successfully. 1 TIUtilities did not run successfully because of problems with the command line parameters. 2 TIUtilities did not run successfully. You should get a specific error message explaining the problem. 3 TIUtilities did not run successfully due to an unknown error. Contact TIBCO Foresight Technical Support. Trace files Studio Workflow Specified by -td command-line parameter. Default is the current directory. To send trace messages to the console, use -tc command-line parameter. The TIUtilities component has a LogFileDirectory property to specify the location of the log files. Also, look in the workflow s Logs directory. See TIUtilities.pdf. s and Troubleshooting Page 16 7/25/2013
TI Web Portal Event log Under Common Administration, you can see system events under Settings Event Log. See Event Log in CommonAdministrationnnn.pdf. Also read the sections on Alerts and on Partner Assignment Errors. Microsoft ThrowIfMaxHttpCollectionKeysExceeded Errors Microsoft has a limit to the number of data elements on an ASP.NET form, and this limit can cause various errors when trying to load a TI page with a lot of data. Look for the text ThrowIfMaxHttpCollectionKeysExceeded in the message. An Internet search will provide more information about this setting. To resolve this, please add the following key within the <appsettings> section of the Web.config for each of your web servers. The value of 2000 should suffice in most cases. As always, please test before promoting to production. <appsettings> <add key="aspnet:maxhttpcollectionkeys" value="2000"></add> </appsettings> s and Troubleshooting Page 17 7/25/2013
TPARouter 0 Success. -1 Invalid command line. Example: missing parameter. -2 Could not access the input file. -3 Output path or output file error. -4 Command line logic problem. Examples: -o option is required when using -e option. -o option can't be used with -c option. -c option is required. Invalid FileType option. Invalid output path -5 Could not move or copy file. -6 Mapping failed - no match found. File remains in current location. -7 Program error. Please call TIBCO Foresight Technical Support. -8 File type error. The command line -e option can only be -ex12 or -eun. -9 Invalid -b parameter. See TPARouter.pdf. s and Troubleshooting Page 18 7/25/2013
Translator (TIBCO Foresight Translator) 100 Translation ran successfully. 105 Could not open the source schema. 106 Guidelines specified in the API are not the same guidelines used in the map. 110 Command line error or error loading INI file. 111 One of the documents being translated must be HL7 when using the HL7 plug-in. 112 A JNI EXECPTION was encountered when using the Java API. 117 The schema cannot be parsed or the XML data does not match it. 124 Configuration invalid. If this occurred when using the API, this is often because it cannot read the INI file. Check TRANSRoot. 131 Map doesn t match the convert call. 135 Database call failed. (Example: Attempting to convert EDI to XML by using an XML-to-EDI map.) 136 Database call failed when using ISIServer. 140 API return code for system failure. 154 Converting between this type of source and target is not supported. 155 Could not open the source guideline. 156 Could not open the target schema. 157 Could not open the target guideline. 158 Could not open the map file. 171 Configuration invalid. If this occurred when using the API, this is often because it cannot read the INI file. Check TRANSRoot. 172 Missing source guideline. 173 Missing target guideline. 174 Missing map. 175 Missing input data when using inputmemory while using API. 176 Cannot access input file when using inputbyfile while using API. 177 The source file separators are invalid as specified by separator in the API. 178 The target file separators are invalid as specified by separator in the API. 180 Failed on OutputFile or Options while using API. Cannot write the output file, or options like CALLBACKBUFFER and UNA are the wrong format. 199 The API is getting a JNI exception occurred and can t run Java. 201 There is an error in the input path. (Examples: An invalid or unreadable input file has been specified. A parameter, such as t, has been left empty.) s and Troubleshooting Page 19 7/25/2013
log file log in Translation Tool Specified with -r command-line parameter. Log goes in the same file as the output. Use the Log button on the Test pane s toolbar: Or see the log in Foresight Translator s bin\fslog directory. See Debugging and Logging in Translator.pdf. ValidationHighlighter 0 No error. 1 Bad parameter supplied. 2 File not found. 10 INI file parsing error. 30 Problem parsing Instream results file. 35 Error in standard C++ library. 40 Error creating HTML output. 50 Unknown error. See ValidationHighlighter.pdf. s and Troubleshooting Page 20 7/25/2013