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 |
|---|---|---|---|---|---|
| 08W65 | Error | 2528 | -876L | "Client out of memory" | A failure occurred when the database client was trying to allocate memory. Click here for a list of possible parameters and odbc states. |
| 08W66 | Error | 2558 | -895L | "Encryption error: %1" | An error occurred during encryption. Click here for a list of possible parameters and odbc states. |
| 08W67 | Error | 2598 | -934L | "Unable to start specified database: Server must be upgraded to start database %1" | The database server was unable to start the database since the database version is newer than the server version. The server must be upgraded to at least the version of the database to be able to start the database. Click here for a list of possible parameters and odbc states. |
| 08W68 | Error | 2599 | -935L | "Unable to start specified database: Log file error" | The database server was unable to start the database since the log file is missing, for a different database, or some other reason. Check the server messages window for more details. Click here for a list of possible parameters and odbc states. |
| 08W69 | Error | 2605 | -941L | "jConnect does not support encryption" | You supplied an encryption type for a connection using jConnect. jConnect does not support encryption. Click here for a list of possible parameters and odbc states. |
| 08W70 | Error | 2643 | -976L | "Could not load the encryption DLL \"%1\No message | An attempt to load the encryption DLL failed. Click here for a list of possible parameters and odbc states. |
| 08W71 | Error | 2669 | -1001L | "Parameter '%1' in procedure or function '%2' does not have a default value" | An attempt was made to use DEFAULT as a procedure or function argument, but the corresponding parameter does not have a default value. Click here for a list of possible parameters and odbc states. |
| 08W72 | Error | 2676 | -1008L | "Unable to start specified database: '%1' is an invalid transaction log mirror" | The specified file is not a valid transaction log mirror. Click here for a list of possible parameters and odbc states. |
| 08W73 | Error | 2677 | -1009L | "Unable to start specified database: The transaction log '%1' or its mirror '%2' is invalid" | The transaction log differs from the transaction log mirror. Either the transaction log or its mirror is invalid. Click here for a list of possible parameters and odbc states. |
| 08W74 | Error | 2678 | -1010L | "Unable to start specified database: '%1' not expecting any operations in transaction log" | The transaction log contains operations, but the database server was not expecting any. Click here for a list of possible parameters and odbc states. |
| 08W75 | Error | 2679 | -1011L | "Unable to start specified database: Unknown encryption algorithm" | The database is encrypted with an algorithm not supported by this server. Click here for a list of possible parameters and odbc states. |
| 08W76 | Error | 2680 | -1012L | "Unable to start specified database: '%1' must be upgraded to start with this server (capability %2 missing)" | The specified database must be upgraded to start with this server. Click here for a list of possible parameters and odbc states. |
| 08W80 | Error | 2684 | -1016L | "Unable to start specified database: Cannot use log file '%1' since it has been used more recently than the database file" | The transaction log file has been used more recently than the database file. Click here for a list of possible parameters and odbc states. |
| 08W81 | Error | 2685 | -1017L | "Unable to start specified database: '%1': transaction log file not found" | The transaction log file was not found. Click here for a list of possible parameters and odbc states. |
| 08W82 | Error | 2686 | -1018L | "Unable to start specified database: Cannot use log file '%1' since the offsets do not match the offsets in the database file" | The transaction log file has an offset that does not match the offset expected by the database file. Click here for a list of possible parameters and odbc states. |
| 08W83 | Error | 2687 | -1019L | "Unable to start specified database: Cannot use log file '%1' since the database file has been used more recently" | The database file has been used more recently than the transaction log file. Click here for a list of possible parameters and odbc states. |
| 08W84 | Error | 2688 | -1020L | "Unable to start specified database: Cannot use log file '%1' since it is shorter than expected" | The transaction log file is shorter than expected. Click here for a list of possible parameters and odbc states. |
| 08W85 | Error | 2672 | -1004L | "Unable to start specified database: '%1' is not a database" | The specified file is not a valid database file. Click here for a list of possible parameters and odbc states. |
| 08W86 | Error | 2673 | -1005L | "Unable to start specified database: '%1' was created by a different version of the software" | The specified database file was created by a different version of the software, and it cannot be read by this version. Click here for a list of possible parameters and odbc states. |
| 08W87 | Error | 2674 | -1006L | "Unable to start specified database: '%1' is not a valid database file" | The specified file is not a valid database. Click here for a list of possible parameters and odbc states. |