Trappable Error Codes

Some errors may be reported without error descriptions. These errors are Clarion trappable errorcodes. [Click here] for detail information on Internet Control Socket errors (HTTP, SMTP, Mail, Message) - These errors should usually be reported to your vendor or InnQuest Software.

2 File Not Found - The requested file does not exist in the specified directory.

3 Path Not Found - The directory name specified as part of the path does not exist.

4 Too Many Open Files - The total number of file handles available has been used. Check the FILES= setting in the CONFIG.SYS file, or the user's or network's simultaneous open files setting in a network environment.

5 Access Denied - The file has already been opened by another user for exclusive access, has been left in a locked state, or you do not have network rights to open the file. This error can also occur when no disk space is available.

7 Memory Corrupted - Some unknown memory corruption has occurred.

8 Insufficient Memory - There is not enough unallocated memory left to perform the operation. Closing other applications may free up enough memory.

15 Invalid Drive - An attempt to read a non-existent disk drive has failed.

30 Entry Not Found - A GET to QUEUE has failed. For GET(Q,key), the matching key value was not found, and for GET(Q,pointer), the pointer is out of range.

32 File Is Already Locked - An attempt to LOCK a file has failed because another user has already locked it.

33 Record Not Available - Usually an attempt to read past the end or beginning of file with NEXT or PREVIOUS. May also be posted by PUT or DELETE when no record was read before the attempted PUT or DELETE. Use CTRL+T and rebuild this file.

35 Record Not Found - For a GET(File,key), the matching key field value was not found.

36 Invalid Data File - Some unknown data file corruption has occurred, or the OWNER attribute does not match the password used to encrypt the file. Restore from backup.

37 File Not Open - An attempt to perform some operation that requires the file be already open has failed because the file is not open. Report this error to InnQuest Software along with information on what you were doing.

38 Invalid Key File - Some unknown key file corruption has occurred. - Use CTRL+T and rebuild this file.

40 Creates Duplicate Key - An attempt to ADD or PUT a record with key field values that duplicate another existing record in the file has been made to a file with a key that does not allow duplicate entries.

43 Record Is Already Held - An attempt to HOLD a record has failed because another user has already held it.

45 Invalid Filename - The filename does not meet the definition of a valid DOS filename.

46 Key File Must Be Rebuilt - Some unknown key corruption has occurred that requires the BUILD statement to re-build the key. - Use CTRL+T and rebuild the file.

47 Invalid Record Declaration - The data file on disk does not match the file's declaration in the .EXE, usually because you have changed the file's definition in the Data Dictionary and have not yet converted the existing data file to the new format. See How do I handle an Error 47. Click here for more information when getting this error when running reports or dayend close. DO NOT REBUILD THIS FILE USING CTRL+T when you get this error.

48 Unable To Log Transaction - A transaction logout or pre-image file cannot be written to disk. This usually occurs because no disk space is available, or the user does not have the proper network rights. Reboot computer, remove the topspeed.tcf file from the roomMaster directory, and rebuild the file using CTRL+T.

52 File Already Open - An attempt to OPEN a file that has already been opened by this user.

54 No Create Attribute - An attempt to execute the CREATE procedure on a file whose declaration does not include the CREATE attribute. Report this error to InnQuest Software

55 File Must Be Shared - An attempt to open a file for exclusive access that must be shared. (Legacy error, no longer used)

56 LOGOUT Already Active - An attempt to issue a second LOGOUT statement while a transaction is already in progress.

57 Invalid Memo File - Some unknown memo file corruption has occurred. For Clarion data files, this could come from a corrupt .MEM file "signature" or pointers to the memo file in the data file that are "out of sync" (usually due to copying files from one location to another and copying the wrong .MEM file).

63 Exclusive Access Required - An attempt to perform a BUILD(file), BUILD(key), EMPTY(file) or PACK(file) was made when the file had not been opened with exclusive access.

64 Sharing Violation - An attempt to perform some action on a file which requires that the file be opened for shared access.

65 Unable To ROLLBACK Transaction - An attempt to ROLLBACK a transaction has failed for some unknown reason.

78 Invalid Number Of Parameters - You did not pass the correct number of parameters to a procedure called in an EVALUATE statement.

79 Unsupported Data Type In File - The file driver has detected a field in the file declared with a data type that is not supported by the file system the driver is designed to access.

81 Unknown Error Posted - The file driver has detected some error from the backend file system that it cannot get further information about.

88 Invalid Key Length - An attempt to CREATE a Clarion file driver KEY or INDEX with more than 245 characters. Other file drivers can also return this error when their file system key length limits are exceeded.

89 Record Changed By Another Station - The WATCH statement has detected a record on disk that does not match the original version of the record about to be updated in a network situation.

90 File Driver Error - The file driver has detected some other error reported by the file system. You can use the FILEERRORCODE and FILEERROR procedures to determine exactly what native error the file system is reporting. Use CTRL+T and rebuild the file when all users are out of the system. If the file persist, restore from backup.

91 No Logout Active - The COMMIT or ROLLBACK statement has been issued outside of a transaction frame (no LOGOUT statement has been executed).

800 Illegal Expression - The EVALUATE procedure has detected an error in the syntax of the expression it is attempting to evaluate. Check your runtime variable calculation for validity.

801 Variable Not Found - The EVALUATE procedure has not found a variable used in the expression it is attempting to evaluate. You must first BIND all variables used in the expression for them to be visible to EVALUATE. Check your runtime variable calculation for validity.