| Prev | Status Codes and Messages | Next |
-5040 to -1000
SQL Relational Database Engine Status Codes
This section lists status codes returned by the SQL Relational Database Engine (SRDE). Should you encounter an error code that is not listed in this section, be sure to record the steps taken to get the particular error you received and notify Technical Support at Pervasive Software.
-1003: Invalid API parameter
A parameter was passed to an invalid internal API.
-1011: Out of memory
This status code may be returned in one of the following situations:
- The engine tried to allocate memory and was unsuccessful. Free up some resources and try again.
- An application error occurred.
- An allocation error occurred.
- An unintended recursion occurred.
-1020: No more file handles
While trying to open a file, a handle was not returned. Close some of your open programs and files and try again.
-1024: File share violation
There was an attempt to open a file that is read only or the specified user does not have the proper rights to open the file. Record the steps taken to get this error and notify Technical Support at Pervasive Software.
-1026: Record size limit exceeded
The record length was larger than the maximum allowed and some data has been truncated. Record the steps taken to get this error and notify Technical Support at Pervasive Software.
-1032: File access denied
There was an attempt to open a file that is read only or the specified user does not have the proper rights to open the file. Record the steps taken to get this error and notify Technical Support at Pervasive Software.
-1040: Too many columns defined
The maximum number of columns that can be defined is 1600 in a select statement; and 1536 elsewhere. Reduce the number of columns to within a valid range and try again.
-1113: Too many active sessions
- The number of active sessions has exceeded the maximum specified in your server access configuration. Either increase the number of active session available or close some of the sessions and try again.
- For NetWare servers: the number of active sessions has reached the maximum allowed (4,906) and cannot be increased.
- For Windows NT servers: the number of active sessions has reached the upper limit of your memory and cannot be increased.
-1206: Non-db file or corrupted db
The file specified is not a valid database name or the database is corrupt.
-1207: Database exclusively locked
There was an attempt to access a database that has been exclusively locked by another user. Wait until the user removes the exclusive lock before continuing.
-1302: Table is exclusively locked
There was an attempt to access a table that has been exclusively locked by another user. Wait until the user removes the exclusive lock before continuing.
-1303: Table already exists
The name you specified for a table already exists in the dictionary. Select another name or remove the current table definition before trying again.
-1304: Table is in use, cannot perform operation
The requested operation cannot be performed because another user is accessing or modifying the table. Try the operation again.
-1305: No such table or object
The table or object your tried to access does not exist. Check for the correct name and path and try again.
-1309: No DDLs without exclusive lock
You must perform an exclusive lock on the desired database before using DDL statements.
-1403: Duplicate index exists
You have attempted to define the same index more than once in this definition. Rewrite the statement so the index is defined only once.
-1404: No such index
You tried to access an index that does not exist. Check the name and path and try again.
-1504: Null not valid
Null is not a valid parameter in the operation performed.
-1507: No such column
The column specified does not exist. Specify a correct column name.
-1508: Field is already defined
The field specified for this table has already been defined.
-1513: Index column type not supported by Isam
You cannot create an index on column types BIT, LONGVARCHAR, or LONGVARBINARY. You must create the index using a different column type.
-1603: Currency not on a record
A query required a temporary table and there was no unique row identifier (index) to correlate the temporary table to the result set. Adding an index to the order by or group by column will often resolve this problem.
-1605: Illegal duplicate key
This status code is returned in the following situations:
- An entry was made into one of the system tables to satisfy a request from the SRDE level to create a database element with the same name (column, table, constraint).
- You attempted to add a unique index to a column which already contains non-unique values.
-1809: Permission denied
The user does not have the appropriate rights for that action. Check the user permissions and try again. If this problem persists, check with your system administrator.
-1810: You are not authorized to perform this operation
The user does not have the appropriate rights for that action. Check the user permissions and try again. If this problem persists, check with your system administrator.
-1902: Unable to logon. An invalid Username/Password may have been specified
An invalid username or password may have been specified. Check your password and try again. If you continue to have problems, check with your system administrator.
-1903: Invalid account name
Either a user with the specified user name or a group with the specified group name does not exist. Check your user/group name and try again. If you continue to have problems, check with your system administrator.
-1905: Invalid password
The password specified was not correct. Check your password and try again. If you continue to have problems, check with your system administrator.
-1907: Access denied
The user does not have the proper permissions to access the file.
-3017: Invalid path/filename
The path/filename for the data file is too long.
-3018: Invalid data type conversion to an identity column
An attempt was made to alter a data type to an identity column.
-3019: Cannot drop a system table
An attempt was made to drop a system table.
-3020: Invalid USING path/filename
The path/filename that you have specified is invalid. Specify a simple, relative path between 1-64 characters.
-3021: Invalid IN DICTIONARY
IN DICTIONARY is not allowed on bound databases.
-3022: Invalid BLOB/CLOB data type in legacy table that contains NOTE/LVAR
A NOTE/LVAR cannot coexist with a LONGVARCHAR/LONGVARBINARY. NOTE/LVAR must first be altered to a LONGVARCHAR/LONGVARBINARY.
-3023: Data type mismatch
Data conversion failed because data cannot be converted due to data type mismatch or data overflow.
-3024: String or binary data truncation error
An attempt was made to convert a char/binary data to a char/binary column that has less bytes.
-3025: Arithmetic overflow error
An attempt was made to convert a number to a numeric column that has less precisions.
-3026: Invalid NULL conversion
You cannot convert the value NULL into a not nullable column.
-3027: Invalid foreign key constraint name
The foreign key constraint name that you have specified is invalid. Specify a name between 1-20 characters.
-3028: Invalid password
The password that you have specified is invalid. Specify a password between 1-8 characters.
-3029: Invalid group or user name
The group or user name that you have specified is invalid. Specify a group or user name between 1-30 characters.
-3030: Invalid procedure or trigger name
The procedure or trigger name that you have specified is invalid. Specify a name between 1-30 characters.
-3031: MKC library cannot be loaded
The attempt to load MKC library failed. Ensure that MKC.DLL is located in the
pvsw\bindirectory.-3032: Column in use by primary key
An attempt was made to delete all indexes referencing a column. An index was encountered that is used in the primary key.
-3033: Column in use by foreign key
An attempt was made to delete all indexes referencing a column. An index was encountered that is used in the foreign key.
-3034: Type cannot be null
The requested operation cannot be performed on a column definition that is nullable.
-3035: Length of the foreign key is incompatible
You cannot define a foreign key if the column it references has a different type or attribute.
-3036: Scale of the foreign key is incompatible
You cannot define a foreign key if the column it references has a different type or attribute.
-3037: Precision of the foreign key is incompatible
You cannot define a foreign key if the column it references has a different type or attribute.
-3038: Data Type of the foreign key is incompatible
You cannot define a foreign key if the column it references has a different data type.
-3039: Trigger dependency
You cannot drop the referenced table because a trigger refers to it.
-3040: Group already exists
A group with the specified group name already exists. Use a different group name. If you continue to have problems, check with your system administrator.
-3041: User already exists
A user with the specified user name already exists. Use a different user name. If you continue to have problems, check with your system administrator.
-3043: Table referenced by foreign key
Cannot drop the table because it is referenced by a foreign key.
-3044: Too many levels of trigger recursion
A trigger cannot be recursively called more than 30 times.
-3045: Index in use by foreign key
Cannot drop the index because it is referred to by a foreign key.
-3046: Integrity Constraint Violation
Nullable columns are not allowed in this operation.
-3047: RI no matching primary key
You tried to create a foreign key before defining a primary key. Define a primary key before continuing.
-3048: Invalid page size
The page size specified is invalid. Specify a page size between 512-4,096 bytes (4,096 is the default).
-3049: Invalid free space threshold
The free space specified is not valid. Specify a free space percentage of 5, 10, 20, or 30 percent.
-3050: Invalid page number
The page number specified is not valid. Specify a page number between 1-65,535.
-3051: The dictionary is in use
The dictionary you are trying to access is already locked by another user. Wait until that user has unlocked the dictionary and try again.
-3052: Dictionary already exists
A dictionary with the specified name already exists in that directory. Use a different dictionary name or path.
-3053: RI table does not exist
There was an attempt to define referential integrity upon a table that does not exist. Check the table name and try again.
-3054: Duplicate savepoint name error
The specified savepoint name already exists.
-3055: Only one Alternate Collating Sequence per index
There can be only one ACS on a given index.
-3056: Add Nullable column in legacy table
Cannot create true null column in a legacy table.
-3057: Conflicting collation
There are attributes of the Column Collating Sequence that conflict with the column definition.
-3058: Drop last column
Cannot drop the last column of a table. A table must contain at least one column.
-3059: Database could not find dictionary files
The dictionary files for the specified database could not be found. Make sure the dictionary files exist and are in the proper directory.
-3060: Constraint already exists
The specified constraint name already exists.
-3061: Invalid constraint name
While creating a column constraint name, the constraint name was too long, null, or had an invalid character.
-3062: Database has no security
You tried to set security privileges on a database that was not marked secure. Enable security on the database.
-3063: Database already secured
You cannot secure a database that has already been secured.
-3064: Alter legacy table
Cannot perform an alter table on a legacy table.
-3065: Invalid login
Either an invalid user name was used or the password failed. Make sure you are using the proper login information. If you continue to have problems, check with your system administrator.
-3066: Group not found
A group with the specified group name does not exist. Specify a valid group name. If you continue to have problems, check with your system administrator.
-3067: Group not empty
A group may not be deleted if there are still valid users in that group. Remove any user names before deleting the group.
-3068: Not allowed to define synonym for Public
Public is a default group and you are not allowed to change or add a synonym for the Public group.
-3069: Not allowed to drop Public
Public is a default group and cannot be dropped from the list of groups.
-3070: Not allowed to drop Administrator
Administrator is a default user and cannot be dropped from the list of users.
-3071: Cannot revoke synonym privileges
You cannot revoke privileges to a synonym; you must revoke privileges to the group the synonym refers to.
-3072: Cannot grant synonym privileges
You cannot grant privileges to a synonym; you must grant privileges to the group to which the synonym refers.
-3073: Privileges cannot be revoked from Administrator
Administrator is a default user and you cannot revoke privileges from the Administrator user name.
-3075: Conversion rename error
While converting a database, a file could not be renamed.
-3076: Conversion delete error
While converting a database, a file could not be deleted.
-3077: Bad index name
The index name is either too long or null.
-3078: Bad column name
The column name is either too long or null.
-3079: Bad table name
The table name is either too long or null.
-3080: Data not bound
You cannot bind a database that is already bound. A database can be bound only once.
-3081: Wrong DDF bind information
The binding information does not match the information specified in the Data Dictionary Files.
-3082: DDF already bound
You cannot bind a Data Dictionary File that is already bound.
-3083: DDF not bound
You cannot unbind a Data Dictionary File that is not bound.
-3084: Shared DDF
You cannot bind a database that uses shared Data Dictionary Files.
-3085: Shared data file
You cannot bind a database that uses shared data files.
-3086: Index in use by primary key
You cannot drop the index because it is referenced by a primary key.
-3087: Primary key already exists
The table already has a primary key defined. You must delete the existing primary key and recreate it.
-3088: Incompatible file version
The file specified is from MicroKernel v6.x or before and must be migrated to the current version of MicroKernel before it can be used.
-3089: Inconsistent multipath
A foreign key cannot reference the table it is in.
-3090: Delete connected cycle
While defining a foreign key, there was a foreign key delete rule violation.
-3091: Self referencing delete not cascade
You must have a delete cascade defined in the foreign key to be able to do a self-referencing delete.
-3092: RI synchronization
The binding information in the Data Dictionary File and data files does not match.
-3093: Trigger RI conflict
If a delete trigger exists on the table, a delete cascade in a foreign key is not allowed.
-3094: Invalid delete rule
Delete name rules or attributes are not valid.
-3095: Invalid update rule
Update name rules or attributes are not valid.
-3096: Object in use
Cannot delete a stored procedure, trigger or view while in use.
-3097: Invalid collate
The collating sequence has a bad name, cannot be used, or may be corrupt.
-3098: Number out of range
The range for the specified number is invalid. Check the range for the option specified and enter a correct number.
-3099: Foreign key invalid database name
While creating a foreign key, the database name specified is either too long or it is null.
-3358: Not allowed to unbind database and change data locations at the same time
See "2342: Not allowed to unbind database and change data locations at the same time"
-3359: Not allowed to bind database and change data locations at the same time
See "2341: Not allowed to bind database and change data locations at the same time"
-3360: Not allowed to create data dictionary and unbind database at the same time
See "2340: Not allowed to create data dictionary and unbind database at the same time"
-3362: Not allowed to change the dictionary location and create dictionary files at the same time
See "2338: Not allowed to change the dictionary location and create dictionary files at the same time"
-3363: Not allowed to change data dictionary location and unbind database at the same time
See "2337: Not allowed to change data dictionary location and unbind database at the same time"
-3364: Not allowed to change data dictionary location and bind database at the same time
See "2336: Not allowed to change data dictionary location and bind database at the same time"
-3365: Not allowed to change data locations and change name at the same time
See "2335: Not allowed to change data locations and change name at the same time"
-3366: Not allowed to create a data dictionary files and change name at the same time
See "2334: Not allowed to create a data dictionary files and change name at the same time"
-3367: Not allowed to unbind database and change name at the same time
See "2333: Not allowed to unbind database and change name at the same time"
-3368: Not allowed to bind database and change name at the same time
See "2332: Not allowed to bind database and change name at the same time"
-3369: Not allowed to change data dictionary location and change name at the same time
See "2331: Not allowed to change data dictionary location and change name at the same time"
-3370: Data file for a table is bound, but does not need to be bound
See "2330: Data file for a table is bound, but does not need to be bound"
-3371: Data file for a table is not bound
See "2329: Data file for a table is not bound"
-3374: Data dictionary files are bound, but do not need to be bound
See "2326: Data dictionary files are bound, but do not need to be bound"
-3375: Data dictionary files are already bound
See "2325: Data dictionary files are already bound"
-3376: Data dictionary files are not bound
See "2324: Data dictionary files are not bound"
-3383: Cannot create DDF files for the bound database
See "2316: Cannot create DDF files for the bound database"
-3385: Cannot create DBNAMES.CFG file
See "2314: Cannot create DBNAMES.CFG file"
-3386: The bound database cannot share data dictionary files
See "2313: The bound database cannot share data dictionary files"
-3387: The bound database cannot share table data files
See "2312: The bound database cannot share table data files"
-3390: The database is in use
See "2309: The database is in use"
-3391: The specified RI flag is invalid
See "2308: The specified RI flag is invalid"
-3392: Cannot open DBNAMES.CFG file
See "2307: Cannot open DBNAMES.CFG file"
-3393: DBNAMES.CFG could not be updated
See "2306: DBNAMES.CFG could not be updated"
-3394: The specified path for data dictionary or data file locations is invalid
See "2305: The specified path for data dictionary or data file locations is invalid"
-3395: The database type is invalid
See "2304: The database type is invalid"
-3396: The database name must be unique; the specified database name already exists
See "2303: The database name must be unique; the specified database name already exists"
-3397: Invalid buffer length
See "2302: Invalid buffer length"
-3398: The database name is invalid
See "2301: The database name is invalid"
-3399: No more database names are defined
See "2300: No more database names are defined"
-3473: The Pervasive Network Services Layer was unable to resolve the given filename into a valid path
See "3126: The Pervasive Network Services Layer was unable to resolve the given filename into a valid path"
-3474: The Pervasive Network Services Layer was unable to resolve the Novell Directory Services name into a NetWare server name
See "3125: The Pervasive Network Services Layer was unable to resolve the Novell Directory Services name into a NetWare server name"
-3475: Pervasive Network Services Layer task table is full
See "3124: Pervasive Network Services Layer task table is full"
-3476: Pervasive Network Services Layer detected an invalid session information level
See "3124: Pervasive Network Services Layer task table is full"
-3477: Pervasive Network Services Layer authentication length is too small
See "3124: Pervasive Network Services Layer task table is full"
-3478: Pervasive Network Services Layer detected an invalid authority object
See "3124: Pervasive Network Services Layer task table is full"
-3479: Pervasive Network Services Layer detected an invalid authority type
See "3124: Pervasive Network Services Layer task table is full"
-3480: No authentication context is available
See "3119: No authentication context is available"
-3481: Pervasive Network Services Layer detected an invalid address family
See "3119: No authentication context is available"
-3482: Pervasive Network Services Layer CST full
See "3119: No authentication context is available"
-3483: Pervasive Network Services Layer received a data overflow
See "3119: No authentication context is available"
-3484: Pervasive Network Services Layer encountered a transport failure
See "3115: Pervasive Network Services Layer encountered a transport failure"
-3485: The routing table of the Pervasive Network Services Layer is full
See "3114: The routing table of the Pervasive Network Services Layer is full"
-3487: Failure during receive from the target server
See "3112: Failure during receive from the target server"
-3488: Failure during send to the target server
See "3111: Failure during send to the target server"
-3489: The network layer is not connected
See "3110: The network layer is not connected"
-3490: More data queued to Pervasive Network Services Layer
See "3110: The network layer is not connected"
-3491: The Pervasive Network Services Layer detected an invalid session
See "3108: The Pervasive Network Services Layer detected an invalid session"
-3492: The Pervasive Network Services Layer is out of memory
See "3107: The Pervasive Network Services Layer is out of memory"
-3493: The Pervasive Network Services Layer encountered a connection failure
See "3106: The Pervasive Network Services Layer encountered a connection failure"
-3494: No available transport protocol for the Pervasive Network Services Layer
See "3105: No available transport protocol for the Pervasive Network Services Layer"
-3495: The Pervasive Network Services Layer encountered a permission error
See "3104: The Pervasive Network Services Layer encountered a permission error"
-3496: Server name not found by Pervasive Network Services Layer
See "3103: Server name not found by Pervasive Network Services Layer"
-3776: The task table of the MicroKernel router is full
See "3023: The task table of the MicroKernel router is full"
-3777: The MicroKernel router could not send the request to the remote engine because the specified data buffer length resulted in a data packet object that is too large
See "3022: The MicroKernel router could not send the request to the remote engine because the specified data buffer length resulted in a data packet object that is too large"
-3778: The MicroKernel router received a badly formatted data packet
See "3021: The MicroKernel router received a badly formatted data packet"
-3779: An error occurred while loading the MicroKernel
See "3020: An error occurred while loading the MicroKernel"
-3780: The MicroKernel router encountered a semaphore error
See "3019: The MicroKernel router encountered a semaphore error"
-3781: The file is already closed
See "3018: The file is already closed"
-3782: Data buffer of the local engine is too small
See "3017: Data buffer of the local engine is too small"
-3783: The MicroKernel router encountered an internal error
See "3016: The MicroKernel router encountered an internal error"
-3784: The MicroKernel router encountered an initialization error
See "3015: The MicroKernel router encountered an initialization error"
-3785: The MicroKernel router cannot find an engine
See "3014: The MicroKernel router cannot find an engine"
-3786: The remote engine is inaccessible to the MicroKernel router because the networking component is not loaded
See "3013: The remote engine is inaccessible to the MicroKernel router because the networking component is not loaded"
-3787: Local engine is not accessible to the MicroKernel router
See "3012: Local engine is not accessible to the MicroKernel router"
-3788: Thunk not possible - the Win32 MicroKernel router could not be found or is incompatible
See "3011: Thunk not possible - the Win32 MicroKernel router could not be found or is incompatible"
-3789: NetWare API DLLs are not loaded
See "3010: NetWare API DLLs are not loaded"
-3790: NETinterface.DLL is not loaded
See "3009: NETinterface.DLL is not loaded"
-3791: Invalid configuration for MicroKernel router
See "3008: Invalid configuration for MicroKernel router"
-3793: The MicroKernel router detected an invalid session
See "3006: The MicroKernel router detected an invalid session"
-3794: The MicroKernel router encountered an operating system error
See "3005: The MicroKernel router encountered an operating system error"
-3795: The MicroKernel is not responding to the MicroKernel router
See "3004: The MicroKernel is not responding to the MicroKernel router"
-3796: The MicroKernel router detected an incompatible network component
See "3003: The MicroKernel router detected an incompatible network component"
-3797: The MicroKernel router resource DLL is unavailable
See "3002: The MicroKernel router resource DLL is unavailable"
-3798: Local access is unavailable to the MicroKernel router
See "3001: Local access is unavailable to the MicroKernel router"
-3799: The MicroKernel router encountered a memory allocation error
See "3000: The MicroKernel router encountered a memory allocation error"
-4837: The client table is full. Try increasing the number of Active Clients in the MicroKernel Database Engine System Resource setting
See "162: The client table is full. Try increasing the number of Active Clients in the MicroKernel Database Engine System Resource setting"
-4838: The maximum number of user count licenses has been reached
See "161: The maximum number of user count licenses has been reached"
-4848: The nesting level is too deep
See "161: The maximum number of user count licenses has been reached"
-4850: SQL Trigger
-4851: A roll forward error occurred
See "148: A roll forward error occurred"
-4852: The log segment is missing
See "147: The log segment is missing"
-4853: Duplicate sys key
See "146: Duplicate system key"
-4856: The MicroKernel cannot allow unauthorized access to files in a secure MicroKernel database
See "143: The MicroKernel cannot allow unauthorized access to files in a secure MicroKernel database"
-4859: The savepoint ID is invalid
See "140: The savepoint ID is invalid"
-4860: The MicroKernel has detected an unacceptable value in the key number
See "139: The MicroKernel has detected an unacceptable value in the key number"
-4861: The NULL indicator position is invalid
See "138: The NULL indicator position is invalid"
-4863: The MicroKernel cannot find the specified Alternate Collating Sequence in the file
See "136: The MicroKernel cannot find the specified Alternate Collating Sequence in the file"
-4864: The specified ISR table is corrupt or otherwise invalid
See "135: The specified ISR table is corrupt or otherwise invalid"
-4865: The MicroKernel cannot read the International Sorting Rule
See "134: The MicroKernel cannot read the International Sorting Rule"
-4866: More than 5 concurrent users attempted to access the same data file
See "133: More than 5 concurrent users attempted to access the same data file"
-4867: The file has reached its size limit
See "132: The file has reached its size limit"
-4869: The MicroKernel ran out of system locks
See "130: The MicroKernel ran out of system locks"
-4884: The file is owned by another Microkernel engine acting as a Gateway
See "116: The file is owned by another Microkernel engine acting as a Gateway"
-4885: The MicroKernel cannot access the archival logging dump file
See "115: The MicroKernel cannot access the archival logging dump file"
-4886: The archival log for the specified file is invalid
See "114: The archival log for the specified file is invalid"
-4887: The MicroKernel cannot find the archival log for the specified file
See "113: The MicroKernel cannot find the archival log for the specified file"
-4888: The specified file is in use by another client
See "112: The specified file is in use by another client"
-4889: The specified filename was not found in the archival logging configuration file
See "111: The specified filename was not found in the archival logging configuration file"
-4890: The MicroKernel cannot access the archival logging configuration file
See "110: The MicroKernel cannot access the archival logging configuration file"
-4891: An unknown error was encountered either creating or accessing a semaphore
See "109: An unknown error was encountered either creating or accessing a semaphore"
-4892: The application attempted to perform a chunk operation on a pre-v6.0 file
See "107: The application attempted to perform a chunk operation on a pre-v6.0 file"
-4893: The MicroKernel cannot perform a Get Next Chunk operation
See "106: The MicroKernel cannot perform a Get Next Chunk operation"
-4894: The file cannot be created with Variable-tail Allocation Tables (VATs)
See "105: The file cannot be created with Variable-tail Allocation Tables (VATs)"
-4895: The MicroKernel does not recognize the locale
See "104: The MicroKernel does not recognize the locale"
-4896: The chunk offset is too big
See "103: The chunk offset is too big"
-4897: Insufficient stack space is available
See "102: Insufficient stack space is available"
-4898: Insufficient operating system memory is available
See "101: Insufficient operating system memory is available"
-4899: No cache buffers are available
See "100: No cache buffers are available"
-4900: The Btrieve Requester is unable to access the NetWare Runtime server
See "99: The Btrieve Requester is unable to access the NetWare Runtime server"
-4901: Internal transaction error
See "98: The MicroKernel detected an internal transaction error"
-4902: The data buffer is too small
See "97: The data buffer is too small"
-4903: A communications environment error occurred
See "96: A communications environment error occurred"
-4904: The session is no longer valid
See "95: The session is no longer valid"
-4905: The application encountered a permission error
See "94: The application encountered a permission error"
-4906: The record lock types are incompatible
See "93: The record lock types are incompatible"
-4907: The transaction table is full
See "92: The transaction table is full"
-4908: The application encountered a server error
See "91: The application encountered a server error"
-4909: The redirected device table is full
See "90: The redirected device table is full"
-4910: A name error occurred
See "89: A name error occurred"
-4911: The application encountered an incompatible mode error
See "88: The application encountered an incompatible mode error"
-4912: The handle table is full
See "87: The handle table is full"
-4913: The file table is full
See "86: The file table is full"
-4914: File is locked
-4915: Record is locked
See "84: The record or page is locked"
-4916: The MicroKernel attempted to update or delete a record that was read outside the transaction
See "83: The MicroKernel attempted to update or delete a record that was read outside the transaction"
-4917: The MicroKernel lost positioning
See "82: The MicroKernel lost positioning"
-4918: The MicroKernel encountered a lock error
See "81: The MicroKernel encountered a lock error"
-4919: The MicroKernel encountered a record-level conflict
See "80: The MicroKernel encountered a record-level conflict"
-4920: A programming error occurred
See "79: A programming error occurred"
-4921: The MicroKernel detected a deadlock condition
See "78: The MicroKernel detected a deadlock condition"
-4922: The application encountered a wait error
See "77: The application encountered a wait error"
-4923: There is a conflict on the referenced file
See "76: There is a conflict on the referenced file"
-4925: The MicroKernel aborted the transaction
See "74: The MicroKernel aborted the transaction"
-4926: The RI definition is out of sync
See "73: The RI definition is out of sync"
-4927: The MicroKernel cannot open the RI referenced file
See "72: The MicroKernel cannot open the RI referenced file"
-4928: There is a violation of the RI definitions
See "71: There is a violation of the RI definitions"
-4930: The Delete operation specified a file that is damaged
See "69: The Delete operation specified a file that is damaged"
-4931 The MicroKernel cannot perform the RI Delete Cascade operation
See "68: The MicroKernel cannot perform the RI Delete Cascade operation"
-4932: The MicroKernel cannot open the SQL data dictionary files
See "67: The MicroKernel cannot open the SQL data dictionary files"
-4933: The maximum number of open databases has been exceeded
See "66: The maximum number of open databases has been exceeded"
-4934: The field offset is incorrect
See "65: The field offset is incorrect"
-4935: The filter limit has been reached
See "64: The filter limit has been reached"
-4936: The data buffer parameter specified on an Insert Extended operation is invalid
See "63: The data buffer parameter specified on an Insert Extended operation is invalid"
-4937: The descriptor is incorrect
See "62: The descriptor is incorrect"
-4938: The work space is too small
See "61: The work space is too small"
-4939: The specified reject count has been reached
See "60: The specified reject count has been reached"
-4940: The specified file already exists
See "59: The specified file already exists"
-4941: The compression buffer length is too short
See "58: The compression buffer length is too short"
-4942: An expanded memory error occurred
See "57: An expanded memory error occurred"
-4943: An index is incomplete
See "56: An index is incomplete"
-4944: The application specified an invalid attribute for an AUTOINCREMENT key
See "55: The application specified an invalid attribute for an AUTOINCREMENT key"
-4945: The variable-length portion of the record is corrupt
See "54: The variable-length portion of the record is corrupt"
-4946: The language interface version is invalid
See "53: The language interface version is invalid"
-4947: An error occurred while writing to the cache
See "52: An error occurred while writing to the cache"
-4948: The owner name is invalid
See "51: The owner name is invalid"
-4949: The file owner is already set
See "50: The file owner is already set"
-4950: The extended key type is invalid
See "49: The extended key type is invalid"
-4951: The alternate collating sequence definition is invalid
See "48: The alternate collating sequence definition is invalid"
-4952: The number of files opened exceeds the maximum allowed
See "47: The number of files opened exceeds the maximum allowed"
-4953: Access to the requested file is denied
See "46: Access to the requested file is denied"
-4954: The specified key flags are invalid
See "45: The specified key flags are invalid"
-4955: The specified key path is invalid
See "44: The specified key path is invalid"
-4956: The specified record address is invalid
See "43: The specified record address is invalid"
-4957: A file previously opened in Accelerated mode was not closed
See "42: A file previously opened in Accelerated mode was not closed"
-4958: The MicroKernel does not allow the attempted operation
See "41: The MicroKernel does not allow the attempted operation"
-4959: The file access request exceeds the maximum number of files allowed
See "40: The file access request exceeds the maximum number of files allowed"
-4960: A Begin Transaction operation must precede an End/Abort Transaction operation
See "39: A Begin Transaction operation must precede an End/Abort Transaction operation"
-4961: The MicroKernel encountered a transaction control file I/O error
See "38: The MicroKernel encountered a transaction control file I/O error"
-4962: Another transaction is active
See "37: Another transaction is active"
-4963: The application encountered a transaction error
See "37: Another transaction is active"
-4964: The application encountered a directory error
See "35: The application encountered a directory error"
-4965: The specified extension name is invalid
See "34: The specified extension name is invalid"
-4966: The MicroKernel cannot unload
See "33: The MicroKernel cannot unload"
-4967: The file cannot be extended
See "32: The file cannot be extended"
-4968: The file is already extended
See "31: The file is already extended"
-4969: The file specified is not a MicroKernel file
See "30: The file specified is not a MicroKernel file"
-4970: The key length is invalid
See "29: The key length is invalid"
-4971: The record length is invalid
See "28: The record length is invalid"
-4972: The key position is invalid
See "27: The key position is invalid"
-4973: The number of keys specified is invalid
See "26: The number of keys specified is invalid"
-4974: The application cannot create the specified file
See "25: The application cannot create the specified file"
-4975: The page size or data buffer size is invalid
See "24: The page size or data buffer size is invalid"
-4976: The position block parameter is not 128 bytes long
See "23: The position block parameter is not 128 bytes long"
-4977: The data buffer parameter is too short
See "22: The data buffer parameter is too short"
-4978: The key buffer parameter is too short
See "21: The key buffer parameter is too short"
-4979: The MicroKernel or Btrieve Requester is inactive
See "20: The MicroKernel or Btrieve Requester is inactive"
-4980: The application encountered an unrecoverable error
See "19: The application encountered an unrecoverable error"
-4981: The disk is full
4983: The application encountered an expansion error
See "16: The application encountered an expansion error"
-4984: The application encountered an I/O error during pre-imaging
See "15: The application encountered an I/O error during pre-imaging"
-4985: The MicroKernel cannot create or open the pre-image file
See "14: The MicroKernel cannot create or open the pre-image file"
-4986: The MicroKernel could not open the extension file for an extended file
See "13: The MicroKernel could not open the extension file for an extended file"
-4987: The MicroKernel cannot find the specified file
See "12: The MicroKernel cannot find the specified file"
-4988: The specified filename is invalid
See "11: The specified filename is invalid"
-4989: The key field is not modifiable
See "10: The key field is not modifiable"
-4990: The operation encountered the end-of-file
See "9: The operation encountered the end-of-file"
-4991: The current positioning is invalid
See "8: The current positioning is invalid"
-4992: The key number has changed
See "7: The key number has changed"
-4993: The key number parameter is invalid
See "6: The key number parameter is invalid"
-4994: The record has a key field containing a duplicate value
You attempted to create a stored procedure with the same name as an existing stored procedure. Follow these steps to recover:
- Change the name of the stored procedure. (Note: Sometimes when you create a procedure with a SQL statement, you may not get a message from PCC confirming that the statement was successful.)
- Run the statement again.
- Run a SELECT *from X$proc# statement to get a list of the defined stored procedures. From this list, you can determine whether or not the procedure was actually created.
Also see "5: The record has a key field containing a duplicate key value"
-4995: The application cannot find the key value
See "4: The application cannot find the key value"
-4996: The file is not open
-4997: The application encountered an I/O error
See "2: The application encountered an I/O error"
-4998: The operation parameter is invalid
See "1: The operation parameter is invalid"
-5202: Record is locked
An attempt was made to access a record that is locked by another user. Wait until the record is unlocked and try again.
-5204: Table is not open
The MicroKernel was unable to open the table. Make sure you have the proper access rights and table privileges.
-5208: Invalid date
The format used for the date is incorrect. Check for the correct ODBC date format and try again.
-5219: Translation failed
The ODBC driver failed to translate the data between the data source and the application. Check if the application is using SQLSetConnectOption to override the default translation dll.
-5220: Invalid procedure name
This procedure name does not exist. Check the name of the procedure called and try again.
-5221: Invalid predicate name
The ODBC driver does not support this predicate. Consult the Pervasive.SQL Programmer's Reference for valid predicates.
-5222: Invalid Code Page value
The code page value in the configuration file is invalid. Refer to the Pervasive.SQL Advanced Operations Guide for valid configuration settings.
| Prev Status Codes |
Contents Up | Next -199 to -100 |