Sometimes a script does not perform as expected even after debugging the command syntax. In this situation you may need to contact Technical Support and send them copies of both the Script Log and the Trace Log generated when the problem occurred. If both of these log files were not enabled when the problem occurred you'll need to enable them and re-run the script so that you have copies of both log files available before either attempting to troubleshoot the problem yourself or contacting support.
The Script Log lists all commands executed and status messages returned. Sometimes you can use this Help file to solve problems recorded in the Script Log. For example, you could determine which script command caused the error and then look up the proper syntax. The command's topic page in this Help file may provide all the assistance that you require. That said, successful troubleshooting usually requires access to both the Script Log, Trace Log and sometimes also the Session Log. Consider the following Script Log file that shows two failed FTPLOGON connection attempts:
In the Script Log above, both connection attempts failed with result code number 1152. The only detectable differences between the two connection attempts are the server address and the time of the attempt. This is insufficient information to accurately troubleshoot these connection attempts. If we also had the Trace Log shown below we could determine that although the result codes were identical, the two connection attempts failed for completely different reasons:
As you can see in the image above, the Trace Log contains diagnostic information intended for Robo-FTP support personnel.
Successful troubleshooting requires that all log files be generated during the same session. Without matching log files, support personnel are not able to align the time stamps and determine which command from the Script Log generated which diagnostic rows in the Trace Log. Since both the Script Log and Trace Log above were created during the same session, we can compare the time stamps and determine that the first FTPLOGON command failed because the server rejected the user's credentials and the second FTPLOGON command failed because the network connection timed out. This information is crucial because it suggests two vastly different solutions.
See also: Basic Logging, Advanced Logging, Interactive Debugging