version 11.2 (Modified)
This table lists the error codes generated by the 4D Database Engine. These codes cover errors that occur at a low level of the database engine, such as user interruption, privilege errors, and damaged objects.
Code | Description |
4001 | Invalid table number requested by a Plug-In |
4002 | Invalid record number requested by a Plug-In |
4003 | Invalid field number requested by a Plug-In |
4004 | Access to a table's current record requested by a Plug-in while there is no current record |
1006 | Program interrupted by useruser pressed Alt-click (Windows) or Option-click (Mac OS) |
-1 | Unknown entry point requested by a Plug-In |
-9750 | The source form is not editable. |
-9751 | The source form is not accessible by the user. |
-9752 | The user form cannot be created. |
-9753 | The source form does not exist. |
-9754 | This command cannot be used from a dialog window. |
-9755 | The user form does not have a name. |
-9756 | There is no user structure file. |
-9757 | The user form does not exist. |
-9758 | The user form already exists. |
-9759 | The Object Library could not be opened. |
-9800 | One of the processes modified the access rights. |
-9850 | Invalid area parameter passed to an external command. |
-9851 | Invalid parameter number 1. |
-9852 | Invalid parameter number 2. |
-9853 | Invalid parameter number 3. |
-9854 | Invalid parameter number 4. |
-9855 | Invalid parameter number 5. |
-9909 | No window available to run the form. |
-9910 | Soap fault. |
-9911 | Parser fault. |
-9912 | HTTP fault. |
-9913 | Network fault. |
-9914 | Internal fault. |
-9915 | The document's reference is invalid. |
-9916 | The element is not open. |
-9917 | The type of the array passed in parameter is invalid. |
-9918 | The name of the element is invalid. |
-9919 | This encoding is not supported. |
-9920 | The type of the node is invalid |
-9921 | Attempt to write a XML Prolog on a non empty document |
-9922 | Lack the parameter value in the attributes definition |
-9923 | The attribute name is not valid |
-9924 | The file must be opened in read only |
-9925 | The referenced element is null. |
-9926 | The referenced element is invalid. |
-9927 | The referenced element is not the "root". |
-9928 | The name of the element is unknown. |
-9929 | The index for this element is invalid. |
-9930 | There is no attribute with this name for this element. |
-9931 | The index for this attribute is invalid. |
-9932 | The XML DLL is not loaded. |
-9933 | The XML file is not valid. |
-9934 | The XML file is not well-formed. |
-9935 | The XML file is not valid or is not well-formed. |
-9936 | Password extern code does not correspond to the database one |
-9937 | Password System is locked by another user. |
-9938 | The current record has been changed from within the trigger. |
-9939 | External routine not found. |
-9940 | 4D Extension initialization failed. |
-9941 | Unknown EX_GESTALT selector. |
-9942 | 4D Client licensing scheme is incompatible with this version of 4D Server. |
-9943 | 4D Connectivity Plug-ins version error. |
-9944 | The user does not belong to the 4D Open access group. |
-9945 | CD-ROM 4D Runtime error; writing operations are not allowed. |
-9946 | Unable to clear the named selection because it does not exist. |
-9947 | The "Allow 4D Open connections" check box has not been selected. |
-9948 | A modal dialog is activated. |
-9949 | License or privilege error. |
-9950 | Invalid data segment number. |
-9951 | This field has no relation. |
-9952 | Invalid data segment header. |
-9953 | There is no Log file. |
-9954 | There is no current record. |
-9955 | QuickTime is not installed. |
-9956 | Versions of 4D Client and 4D Server are different. |
-9957 | The choice list is locked. |
-9958 | The process could not be started. |
-9959 | The backup process has already been started by another user or process. |
-9960 | 4D Backup is not installed on the server. |
-9961 | The backup process is not currently running. |
-9962 | The backup cannot be run because the server is shutting down. |
-9963 | Invalid record number requested by a workstation. |
-9964 | Bad sort definition table sent by a workstation. |
-9965 | Bad search definition table sent by a workstation. |
-9966 | Invalid type requested by a workstation. |
-9967 | The record could not be modified because it could not be loaded. |
-9968 | Invalid selected record number requested by workstation. |
-9969 | Invalid field type requested by workstation. |
-9970 | Field is not indexed. |
-9971 | Field number is out of range requested by workstation. |
-9972 | Table number is out of range requested by workstation. |
-9973 | The TRIC resources are not the same. |
-9974 | Record has already been deleted. |
-9975 | Transaction index page could not be loaded. |
-9976 | Backup in progress; no modification allowed. |
-9977 | The selection does not exist. |
-9978 | Bad user password. |
-9979 | Unknown user. |
-9980 | The file cannot be created because the structure is locked. |
-9981 | Invalid field name/field number definition table sent by the workstation. |
-9982 | The record was not loaded because it is not in the selection on the workstation. |
-9983 | The same external package is installed twice. |
-9984 | Transaction has been cancelled because of a duplicated index key error. |
-9985 | Recursive integrity. |
-9986 | Record locked during an automatic deletion action. |
-9987 | Some other records are already related to this record. |
-9988 | The form cannot be loaded. Either the form or the structure is damaged. |
-9989 | Invalid structure (database needs to be repaired). |
-9990 | Time-out error. |
-9991 | Privileges error. |
-9992 | Wrong password. |
-9993 | Menu bar is damaged (database needs to be repaired). |
-9994 | Serial communication interrupted by the useruser pressed Ctrl-Alt-Shift (Windows) |
or Command-Option-Shift (Mac OS). | |
-9995 | Demo limit has been reached. |
-9996 | Stack is full (too much recursion or nested calls). |
-9997 | Maximum number of records has been reached. |
-9998 | Duplicated key. |
-9999 | No more room to save the record. (see note 4) |
-10500 | Invalid record address (database needs to be repaired). |
-10501 | Invalid index page (index needs to be repaired). |
-10502 | Invalid record structure (data file needs to be repaired). |
-10503 | Record # is out of range (during GOTO RECORD, or data file needs to be repaired). |
(see note 3) | |
-10504 | Index page # is out of range (index needs to be repaired). |
-10505 | Client and server have version numbers that are incompatible. |
-10506 | Limit of the Standard Edition version. |
-10507 | This version does not allow a compiled database to be opened. |
-10508 | Project method not found. |
-10509 | Can't open database "". |
-10510 | Can't load component "". |
-10511 | Can't call command "" from a component. |
-10512 | The encoding is not supported |
-10513 | Can't call {cmd_name} command from a 4D remote machine. |
-10514 | The maximum number of concurrent users for your license has been reached |
-10515 | Your attempt to connect to 4D Server has been denied |
-10516 | The server is running a maintenance operation, please reconnect later. |
-10517 | Failed to synchronize {folder_name} folder. |
-10600 | This BLOB could not be read. It may be damaged. |
Notes
1. While some of the errors listed reflect serious problems, i.e., -10502 Invalid record structure (data file needs to be repaired), other errors may occur on a regular basis and can be managed using an ON ERR CALL project method. For example, it is common to handle the error 9998 Duplicated key if your application offers opportunities to create duplicated values for a table that includes an indexed field whose Unique property is set.
2. Some of the errors listed never occur at the 4D language level. They can occur and be handled at a low level by database engine routines or when using 4D Backup or 4D Open.
3. The error -10503 Record # is out of range generally means that your code (for example, the GOTO RECORD command) is attempting to access a record that no longer exists (or has never existed). In certain more unusual cases, this error may mean that the database needs repairing.
4. The error -9999 No more room to save the record occurs when the data file of your database is full or located on a full volume. This error can also be generated if the data file is locked or located on a locked volume.
See Also