Laserfiche WebLink
TSTool Documentation Troubleshooting <br />Error <br />Possible solutions <br />data type) have <br />then filling in values from the database. The output period (or maximum if not <br />- 9 9 9 or other <br />specified) may be such that time series values were not found in the database <br />missing values. <br />and were set to the missing data value of - 9 9 9. Use fill commands to fill the <br />missing data within the requested period. <br />TSTool fails on <br />TSTool may run out of memory on queries (hundreds or thousands of time <br />large queries or <br />series, depending on machine memory). More time series may be able to be <br />displays out of <br />handled if run in batch mode because GUI resources are minimized. To <br />memory error. <br />increase the amount of memory that TSTool will use: <br />1. If running on Windows using the TSTool.exe program (the default <br />configuration), increase the value of the — XmXNNNm option in the <br />bin (TSTool. 14j. ini file under the software installation folder. <br />2. If running on Windows using the TSTool. bat file, change the - XmXNNNm <br />option after the JRE program name to tell Java to allow more memory <br />(increase the number of MB NNN as appropriate for the amount of memory <br />available on the machine — use a high number to force using hard disk <br />swap space if desired). <br />3. If running on Linux or Unix using the tstool script, change the - XmXNNNm <br />option after the JRE program name to tell Java to allow more memory <br />(increase the number of MB NNN as appropriate for the amount of memory <br />available on the machine — use a high number to force using hard disk <br />swap space if desired). <br />Unexpected failure. <br />If there was an error in input that was serious, TSTool may quit processing <br />input. See the log file for details. If the log file does not offer insight, contact <br />support. Specific causes of failure may include: <br />1. TSTool has been developed using a version of Java that is indicated in the <br />metadata for software files. Trying to use an older Java version may cause <br />unexpected errors. This will only be a problem in custom installations <br />where the default Java distributed with TSTool is not used. To determine <br />the Java version that is being used to run TSTool and that was used to <br />create the software, use Tools ... Diagnostics and select the Allow debug <br />checkbox. Then use the Help ... About TSTool menu item and press Show <br />Software /System Details to display information that includes the Java <br />version that is being used to run TSTool. <br />2. An unforeseen issue may be occurring. Contact support. You may need to <br />provide the data and command file being used, which will allow <br />troubleshooting and also allow developers to add additional tests to be run <br />before software is released. <br />Unable to find files <br />The working directory is assumed to be the same as the location of the most <br />correctly. <br />recently opened or saved command file. The current working directory is <br />generally displayed by editor dialogs that use a path and can also be displayed <br />using File... Properties... TSTool Session. If files are not being found, verify <br />that the path to the file is correct, whether specified as an absolute path or <br />relative to the command file. <br />When used with the <br />1. TSTool tries to list the ODBC DSN that are available for HydroBase <br />HydroBase input <br />databases. It does so by running the shellcon.exe program, typically <br />type for a Microsoft <br />installed in Icdsslbin if TSTool is used with CDSS. If this directory is not <br />Access database, an <br />in the PATH environment variable, the program will not be found and an <br />error occurs <br />error will occur. The PATH normally will include the directory after <br />111 Troubleshooting - 3 <br />