An error message such as "File Not Found" displays when anyProduction Reporting Remote methods are called. | Check that the necessary components are accessible. These components include SQRREM32.DLL, PTTCP32C.DLL, and PTFTP32C.DLL. The DLL files must reside within the Windows System directory or somewhere in the path. |
An error occurs when attempting to open a connection to a server using the Production Reporting ActiveX Control method RemoteOpen. | This typically indicates an invalid hostname, account login, or account password. It may also indicate that the server is down or is not accessible. Use the TCP/ IP ping utility to ensure that the server is up and is accessible. Use the TCP/IP ftp utility to ensure that you can log into the server using ftp. |
An error occurs when attempting to execute a command on a UNIX server. | This typically indicates that an invalid command was used or the permissions on the command are not correct. View the contents of the output file to see what error occurred. The filename of the output file is a parameter passed to the Production Reporting Remote methods RemoteExec and RemoteExecNoWait. When using the method RemoteExec, the output file is placed on the client PC. When using RemoteExecNoWait, the output file is placed on the remote server. An error can also indicate that the UNIX login does not have REXEC permission. Use the TCP/IP rexec utility to ensure that you have REXEC permission. This permission must be configured on the server. See your UNIX server documentation for more details, or ask your system administrator. |
An error occurs when attempting to run a report remotely. | This typically indicates that server components of Production Reporting Remote are not correctly configured. View the contents of the standard output file OUT (this is not the SPF file) or the error file, if it is exists, to see what error occurred. The filenames of the output file and the errors file are the same as the filename of theProduction Reporting program except that they have the file extension OUT and ERR, respectively. If an error file exists, the Production Reporting program ran but had problems. If an error file does not exist, the program that runs Production Reporting programs could not be started. Another cause of the problem could be that the Production Reporting program (script) running on the remote server requires additional resources, such as bitmaps, include files, and so on, that have not been copied to the server, or the report at runtime can not correctly locate them. When running remotely, it is generally the Production Reporting programmer’s responsibility to ensure that all the necessary conditions are fulfilled prior to executing the Production Reporting program. |
An error occurs when attempting to copy a file to or from a UNIX server. | This typically indicates an invalid filename or permissions. You must have read permission to the directory on the UNIX server to get files from it. You must have write permission to the directory on the UNIX server to put files into it. You must also have permission to overwrite the local file. |