1000 | LOCAL_ERR_EXECUTABLE | Failed to load SQR.DLL or launch SQR.EXE. | Ensure that Production Reporting is installed correctly, that SQR.INI is in the system directory, and that SQRDIR is pointing to where SQR.DLL resides. |
1001 | LOCAL_ERR_GENERAL | Failed to run Production Reporting. | Check that all components required by Production Reporting are available. |
1002 | LOCAL_ERRDAT_FILE | Failed to process the file SQRERR.DAT. | Check that SQRERR.DAT is present and accessible by SQR.EXE. This error can also indicate that there are not enough system resources, such as file handles, available. |
1003 | LOCAL_COMMAND_LINE | Invalid command line option specified. | Correct the command line option passed to the LocalRun method. |
1004 | LOCAL_ERR_CREATE_SQT | Failed to create the SQT file. | Check that there is enough disk space available. This error can also indicate that there are not enough system resources, such as file handles, available. |
1005 | LOCAL_ERROR_COMPILE | Failed to compile Production Reporting. | Modify Production Reporting source code as necessary. |
1006 | LOCAL_ERR_READ_SQT | Failed to open or read the SQR or SQT file specified in the command line. | Check that the specified SQR or SQT file is present. This error can also indicate that there are not enough system resources, such as file handles, available. |
1007 | LOCAL_ERR_WRITE_LIS | Failed to create or write the LIS file. | Check that there is enough disk space available. This error can also indicate that there are not enough system resources, such as file handles, available. |
1008 | LOCAL_ERR_WRITE_ERR | Failed to create or write the ERR file. | Check that there is enough disk space available. This error can also indicate that there are not enough system resources, such as file handles, available. |
1009 | LOCAL_ERR_WRITE_LOG | Failed to create or write the LOG file. | Check that there is enough disk space available. This error can also indicate that there are not enough system resources, such as file handles, available. |
1010 | LOCAL_ERR_READ_POSTSCRI | Failed to open or read the file POSTSCRI.STR. | Check that POSTSCRI.STR is present and accessible by SQR.EXE. This error can also indicate that there are not enough system resources, such as file handles, available. |
1011 | LOCAL_ERR_RECURSIVE | Production Reporting cannot be called recursively. | Production Reporting attempted to run another Production Reporting program. Modify Production Reporting logic as necessary. |
1012 | LOCAL_ERR_WINDOWS | Failed to allocate memory or a system resource. | Check that there are enough memory or system resources available. |
1013 | LOCAL_ERR_INTERNAL | Production Reporting caused an internal error. | This typically indicates that Production Reporting attempted an invalid operation, using too large of an array for example. Modify Production Reporting logic as necessary. |
12000 | REMOTE_ERR_NOT_CONNECTED | Attempted an Production Reporting Remote method when no connection is open. | Add program logic to prevent calling the method when no connection is open. Use RemoteIs Connected to determine if a connection is open. |
12102 | REMOTE_ERR_BUSY | An Production Reporting Remote operation is already in progress. | Add program logic to prevent calling an Production Reporting Remote method until the last method completes. This typically occurs because of the way Production Reporting Remote methods operate in the background. When an Production Reporting Remote method that operates in the background is called, it releases control back to the windows message queue until the background method completes. |
12103 | REMOTE_ERR_ABORTED | An Production Reporting Remote operation was aborted by the RemoteCancel method. | No action necessary. |
12104 | REMOTE_ERR_FAILED | An Production Reporting Remote operation failed. | Check that there are enough memory or system resources available. |
12105 | REMOTE_ERR_NO_TIMERS | Failed to allocate a Windows timer. | Check that enough Windows timers are available. A finite number of Windows timers are available on the system. Other applications may be using Windows timers. Close those applications to make the timers available. |
12106 | REMOTE_ERR_TIMER_LOOKUP | Failed to locate the Windows timer number internally. | This should never occur. If it does occur, contact customer support. |
12107 | REMOTE_ERR_MEMORY | Failed to allocate memory. | Check that there are enough memory or system resources available. |
12108 | REMOTE_ERR_FILE_OPEN | Failed to open the specified file. | Check that the specified file is present and accessible by SQRREM.DLL. This error can also indicate that there are not enough system resources, such as file handles, available. |
12109 | REMOTE_ERR_TIMEOUT | The Production Reporting Remote operation timed out. | This occurs when the Production Reporting Remote operation takes more time than specified by the time-out value. Check that the time-out value, specified by the "TimeOut" entry in the [SQR Remote] section of SQR.INI, is set to an appropriate value. The timeout is set to 30 seconds by default. (See”[SQR Remote] Section” in Volume 2 of the Production Reporting Developer's Guide for more information.) For example, copying a very large file over a slow network connection may require a large time-out value. This error can also indicate that the specified hostname or IP address passed to RemoteConnect is invalid. |
12110 | REMOTE_ERR_INV_ARG | Invalid argument passed to the Production Reporting Remote method. | Modify the program source code as necessary. |
12111 | REMOTE_ERR_DELETE | Failed to delete remote file using FTP delete file capability. | Check that the remote file has write permissions. Use an FTP utility, one is typically supplied with your TCP/IP product, to attempt to delete the specified file. |
12112 | REMOTE_ERR_TYPE | Failed to set the file type to ASCII or binary using the FTP type capability. | This should never occur. If it does occur contact customer support. |
12115 | REMOTE_ERR_SQR | Production Reporting ran, but it generated errors. | This indicates that Production Reporting caused an error. This is typically attributed to failure to connect to the database, failure to compile the Production Reporting program source code, or failure in the Production Reporting program logic. See the contents of the ERR file for details of the error. If it is needed, modify Production Reporting source code as necessary. |
12116 | REMOTE_ERR_GEN_UNIQUE | Failed to generate a unique file name. | The RemoteRun method attempts to generate a unique filename by generating a random filename starting with the characters "sq", "sq029342.sqr" for example. It attempts this many times before aborting with this error. Retry the operation. If this occurs many times, the remote directory may be filled with garbage files with the "sq*.sqr" filename. Delete the garbage files from the remote directory. |
12117 | REMOTE_ERR_CONNECTED | Attempted to reconnect, but the current connection can not be disconnected. | Check your program logic to ensure that the connection can be disconnected before trying to make another connection. |
12118 | REMOTE_ERR_RUNNING | Production Reporting is still running at the time RemoteGetResults is called. | If Production Reporting processes a large amount of data, it may take a long time to run the report. Use RemoteGetResults at a later time to detect when Production Reporting has completed. If it takes an unreasonable amount of time to run Production Reporting , it may indicate that Production Reporting has hung waiting for some resource that is not available. In this situation, modify Production Reporting source code as necessary. |
12119 | REMOTE_ERR_SQR_CMD | Failed to invoke Production Reporting to run Production Reporting Remote Production Reporting Remote uses the REXEC capability to execute an Production Reporting program on the UNIX server. It does this by using REXEC to run the remote script. The remote script runs the startup script for the account to set the necessary environment variables; then, the remote script runs the Production Reporting executable. The Production Reporting executable runs the Production Reporting program. | See the contents of the OUT file for details of the error. This typically indicates that the UNIX account is not configured properly. To check the account: Check that the appropriate remote script is present in the home directory of the UNIX account. The filename of the remote script is "rsqr.csh" for C Shell based accounts and "rsqr.sh" for Bourne shell and Korn shell based accounts. Check that the remote script has execute permissions. Check that the startup script for the UNIX account, ".login" for C Shell based accounts and ".profile" for Bourne shell and Korn shell based accounts, does not perform an invalid operation that causes the shell to terminate. In general, the "$TERM" variable is not set so the script should not utilize it and the standard input is redirected to "/ dev/null" so the script should attempt to directly read from it. Check that the startup script sets the appropriate environment. In general, it should set the SQRDIR variable, the database environment variables, and the SQRDIR into the UNIX PATH. Check that theProduction Reporting executable is present on the UNIX server and can be accessed using the contents of the UNIX PATH.
|
12120 | REMOTE_ERR_FTP_LOGIN | Failed to log into the server using FTP. | Check that the specified hostname, username, and password are correct. Also check that the account has FTP permission. Use an FTP utility, one is typically supplied with your TCP/IP stack, to attempt to log into the UNIX account. |
12121 | REMOTE_ERR_REXEC_LOGIN | Failed to log into the server using REXEC. | Check that the specified hostname, username, and password are correct. Also check that the account has REXEC permission. Use an REXEC utility, one is typically supplied with your TCP/IP product, to attempt to execute a command such as "ls -l" utilizing the specified UNIX account. |
12122 | REMOTE_LOCFILE_PERM | Invalid permissions on local file. | Check that the specified local file is not set with read only permission. Use the "attrib" utility to change the permission. |
12123 | REMOTE_ERR_FTP_GET | Failed to get the file from the server using FTP. | Check the FTP permissions to the remote file. Use an FTP utility, one is typically supplied with your TCP/IP product, to attempt to get the file from the UNIX server. |
12124 | REMOTE_ERR_FTP_PUT | Failed to put the file to the server using FTP. | Check the FTP permissions to the remote file. Use an FTP utility, one is typically supplied with your TCP/IP product, to attempt to put the file to the UNIX server. |
12125 | REMOTE_ERR_FTP_NAMELIST | Failed to get a directory listing from the server using FTP. | Check the FTP permissions to the remote directory. Use an FTP utility, one is typically supplied with your TCP/IP product, to perform an "ls" operation on remote directory of the UNIX server. |
12126 | REMOTE_ERR_FTP_PWD | The FTP print working directory operation failed. | Check that the user account has read permissions to the working directory on the remote server. |
12127 | REMOTE_ERR_UNKNOWN_SERVER | Attempted to open a connection to an unknown server type. | When a connection is opened to a remote server,Production Reporting Remote performs a print working directory operation. It checks for the returned string to determine the server type. An ":\" in the string indicates a Windows server, and a "/" indicates a UNIX server. You must use a Windows or UNIX based server. |
12129 | REMOTE_ERR_REMOTE_ NOT_FOUND | Attempted to retrieve or otherwise read a remote file that does not exist. | Check that the specified filename is correct. |
12130 | REMOTE_ERR_REXEC | Failed to execute a command using REXEC. | Make sure you have permission on the server to execute commands remotely using REXEC. |