Laserfiche WebLink
<br /> Troubleshooting - 1 <br />8 Troubleshooting <br />Version 1 0.12 .0 0 , 20 1 2 -0 9 -10 <br /> <br />This chapter discusses how to troubleshoot TSTool problems. Section 8.1 – Obsolete Commands lists <br />obsolete commands, which may no longer be supported by current software and should be phased out. <br /> <br />TSTool ca n run in interactive mode with a graphical user interface (GUI) and in batch mode. In both <br />cases a log file contains messages from the program. By default, t he log file is created in the logs <br />directory under the main installation directory. It is recomm ended that the S tartLog() command be <br />inserted as the first command in each command file, using the name of the commands file in its name. <br />The log file can then be viewed using the Tools…Diagnostics features (see Chapter 3 – Getting <br />Started ). However, in most cases, the log file should only be used for major troubleshooting because it <br />contains technical details that may not be understandable by the user. The error -handling features of the <br />GUI provide a status for each command. Often, an error in an early command leads to additional errors in <br />other commands and therefore fixing the first error can resolve multiple problems. <br /> <br />The most common problems are program configuration (see the Installation and Configuration <br />Appendix ), user input error (see the comma nds reference for command syntax), and data errors for <br />various input types (see below and see also the input type appendices). Other problems should be <br />reported to the TSTool developers (use the Help…About menu to list support contacts). Y ou may need <br />to email the log file to support to help determine the nature of a problem. <br /> <br />W hen running the TSTool GUI, major problems will be indicated with an icon next to the offending <br />command (see Chapter 3 – Getting Started for a summary of command error handling feat ures). When <br />running in batch mode, warnings are only printed to the log file. In either case, the log file viewer can be <br />used to pinpoint the source of problems . If the run has been successful the GUI will show no problem <br />indicators and the log file wil l contain primarily status messages, which provide useful information about <br />data processing . <br /> <br />The following table summarizes common errors and their fixes. If an error is occurring in batch mode, it <br />is useful to run via the GUI to utilize error feedback f eatures. Errors specific to a database are discussed <br />in the documentation for the database (see input type and datas tore appendices). <br /> <br />109