Messages on this page are sorted by SQLSTATE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL State | Msg Type | Number | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| 53W08 | Error | 2166 | -294L | "Format string argument number %1 is invalid" | You supplied an invalid argument number in the format string for a PRINT or RAISERROR statement. The number must be between 1 and 20 and must not exceed the number of arguments provided. Click here for a list of possible parameters and odbc states. |
| 53W09 | Error | 2218 | -609L | "Invalid data type for column in WRITETEXT or READTEXT" | You referenced a column in a WRITETEXT or READTEXT statement that is not defined for storing text or image data. Click here for a list of possible parameters and odbc states. |
| 54003 | Error | 2061 | -250L | "Identifier '%1' too long" | An identifier was specified is longer than 128 bytes. Click here for a list of possible parameters and odbc states. |
| 54W01 | Error | 2553 | -890L | "Statement size or complexity exceeds server limits" | The statement contains one or more constructs whose size make it impossible to process. Increasing the maximum cache size, page size, or stack size may resolve this error. Consider rewriting the query so that the internal limit is not exceeded. For example, if the query contains a large IN-list, consider inserting the IN-list's values into a temporary table. Then rewrite the query to join this temporary table to the other table(s) in the original statement. Click here for a list of possible parameters and odbc states. |
| 54W02 | Error | 2600 | -936L | "Too many constraints in database" | An attempt to create a new constraint failed because the corresponding system table is full. Reloading the database will reclaim any unused space. Click here for a list of possible parameters and odbc states. |
| 54W03 | Error | 2638 | -972L | "Database page size too small: %1" | You attempted to load statistics that were too large for the current database page size. Rebuilding this database with a larger page size could prevent this error. Click here for a list of possible parameters and odbc states. |
| 54W04 | Error | 2659 | -992L | "The specified listener could not be registered" | The specified listener could not be registered because the maximum number of listeners has been reached, the class name is already in use, or system resources are not available. Click here for a list of possible parameters and odbc states. |
| 54W05 | Error | 2668 | -1000L | "Temporary space limit exceeded" | The connection has exceeded its temporary-space usage limit. This limit is based in part on the amount of free-space remaining on the drive containing the temporary file. Try deleting unused files from the drive, or placing the temporary file on a drive with more space available. See the -dt server option to specify a directory for temporary files. Click here for a list of possible parameters and odbc states. |
| 54W06 | Error | 2639 | -973L | "The string is too long (%1)" | The string is longer than that allowed by the server. Click here for a list of possible parameters and odbc states. |
| 54W07 | Error | 2383 | -738L | "Password must be at least %1 characters" | The password is shorter than that allowed by the current min_password_length option setting. Click here for a list of possible parameters and odbc states. |
| 54W08 | Error | 2622 | -958L | "Password cannot be longer than %1 characters" | The password is longer than that allowed by the server. Click here for a list of possible parameters and odbc states. |
| 54W09 | Error | 2763 | -1093L | "The size of the character column, variable, or value data type exceeds 32767" | The declaration or conversion has specified a character type with byte length greater than 32767. Click here for a list of possible parameters and odbc states. |
| 54W10 | Error | 2775 | -1104L | "Too many users in database" | You have exceeded the maximum number of users permitted to access the database. The maximum number of users that are allowed granted access to a single UltraLite database is four. Click here for a list of possible parameters and odbc states. |
| 54W11 | Error | 2778 | -1107L | "Too many references to a BLOB" | You have exceeded the maximum number of references to a particular BLOB. In UltraLite you may have at most 256 references to any one particular BLOB. Click here for a list of possible parameters and odbc states. |
| 54W12 | Error | 2909 | -1230L | "Too many open cursors" | You exceeded the number of cursors allowed to be open on a single UltraLite database. Check to ensure you are freeing statements when you are done with them. Click here for a list of possible parameters and odbc states. |
| 54W13 | Error | 2914 | -1235L | "Too many columns in SELECT list" | You executed a statement with too many expressions in the SELECT list. The number of expressions within a SELECT list is limited to 60000. Click here for a list of possible parameters and odbc states. |
| 54W14 | Error | 2915 | -1236L | "Too many expressions in GROUP BY list" | You executed a statement with too many expressions in the GROUP BY list. The number of expressions within a GROUP BY list is limited to 60000. Click here for a list of possible parameters and odbc states. |
| 54W15 | Error | 2916 | -1237L | "Too many columns in procedure result set" | You executed a statement with too many expressions in the GROUP BY list. The number of expressions within a GROUP BY list is limited to 60000. You executed a CREATE PROCEDURE or ALTER PROCEDURE statement. The resulting number of columns in the result set of the procedure would exceed the server's limit. Click here for a list of possible parameters and odbc states. |
| 54W50 | Error | 2548 | -887L | "Virtual index creation with more than %1 columns" | You attempted to create a virtual index with more than the maximum number of columns. Click here for a list of possible parameters and odbc states. |
| 54W51 | Error | 2908 | -1229L | "Reorganize table is already being run on table \"%1\No message | There is already a REORGANIZE TABLE statement being run on this table. Only one such statement can be executing on a table at any time. Click here for a list of possible parameters and odbc states. |