COPIAFACTS Program Error Messages

The COPIAFACTS server engine program includes an extensive set of error-checking functions, and monitors internal processes for errors as well as detecting errors in the various command files. The standard error messages are listed in the following sections. In some countries, error messages may be provided translated into languages other than English.

Error messages have four-digit numbers, and possibly a two-digit suffix. The suffix allows Copia staff to track the precise source of an error when the same error may result from more than one operation.

During program startup, as much as possible is checked and the program will not run if errors are found. During normal program operation, every effort is made to continue processing if errors occur. If an error does not need to stop program operation, then it also defaults to not displaying on the screen or in the error trace file. You need to enable trace to display or trace to file in the COPIAFACTS program, or the F4 or F5 keys (see Keyboard Functions), to view or file respectively these non-critical error messages.

Error messages are divided into eight different categories, distinguished by the leading digit of the four-digit error number. Some messages are clearly marked as "Warning:" and in this case the error will not usually have caused the call to fail, although it may not be processed as expected.

In some cases the error message listed in this section will reference a 'Windows error number'.  You can use the provided utility WINERR to display the text corresponding to a Windows error number.

0xxx Startup Errors

Category 0 messages (numbers less than 1000) are used for setup errors, before the main status screen appears. The messages always cause the program to terminate.

1xxx Initialization Errors

Messages in the 1000 range are initialization errors. They are always cause termination of the program. Mostly they refer to problems with the initialization of the voice and fax hardware.

2xxx Configuration Errors

Messages in the 2000 range result from errors in processing the configuration file. Again, they always cause termination of the program.

3xxx User Profile Errors

Messages numbered 3000 and above do not cause the program to terminate and do not appear in the trace area unless 'trace to display' is enabled. The 3000 range messages result from errors in the User Profile.

An error on the initial load of the default user profile causes error 2060 or 2061 and therefore does stop the program, but errors reloading a user profile during normal processing do not stop the program though they will cause the call to fail.

4xxx Run-Time Errors

The 4000-range messages are internal program errors, the majority of which should never appear in normal operation. If you see this category of error and neither the message nor the description here indicates how you can fix the problem, please contact Copia or your CopiaFacts supplier. Usually the call will fail after an error of this type.

5xxx IIF Errors

Messages in the 5000 range are the result of errors in .IIF files. These messages are listed in the following sections. The message or the notes will indicate the corrective action needed. Usually the call will fail after an error of this type.

6xxx FS File Errors

Messages in the 6000 range are the result of errors in .FS files. These messages are listed in the following sections. The message or the notes will indicate the corrective action needed. Usually the call will fail after an error of this type.

7xxx MBX/MCF Errors

Messages in the 5000 range are the result of errors in .MBX and .MCF files. These messages are listed in the following sections. The message or the notes will indicate the corrective action needed. Usually the incoming call will fail after an error of this type.

All messages other than those with numbers below 1000 are displayed or written in the trace file on two lines, the first giving the context in which the error occurred. Other un-numbered single-line trace messages may also appear if debugging is enabled. The debugging messages are not documented here. They will always appear in English even when an external message file in another language is available.

To avoid confusion of the various meanings of the word "line", a line number in an error message preceded by "#" always refers to the text line number of the command in a control file; without "#" it refers to a logical phone line number or e-mail thread.