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 and Trace 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:
Successful troubleshooting requires that all log files be generated during the same session. Without matching log files it is not possible to align the time stamps and determine which command from the Script Log generated which diagnostic rows in the Trace Log. The Script Log and Trace Log images shown above were created during the same session so 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. The first server is explicitly rejecting the logon attempt so you may need to consult the administrator of the remote site to verify your authentication credentials. The second server is unreachable over the network so the failure occurred before Robo-FTP even had a chance to attempt authentication. In the second situation you may need to contact your own network administrator to resolve the connectivity issue.
See also: Basic Logging, Advanced Logging, Debug Logging, Interactive Debugging