Messages on this page are sorted by Sybase error code. Locate the appropriate code in the table below, and click the link for a full description of the message.
| Number | Msg Type | SQL State | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| 2669 | Error | 08W71 | -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. |
| 2670 | Error | WW062 | -1002L | "The option '%1' is not recognized" | The specified option was not recognized. The option may have been spelled incorrectly. Click here for a list of possible parameters and odbc states. |
| 2671 | Error | 28W10 | -1003L | "Too many distinct group mappings for integrated user" | The integrated user does not have an explicit mapping in the database but does have group mappings. There are too many distinct group mappings. You must either reduce the number of distinct group mappings or add an explicit mapping for the user. Click here for a list of possible parameters and odbc states. |
| 2672 | Error | 08W85 | -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. |
| 2673 | Error | 08W86 | -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 can not be read by this version. Click here for a list of possible parameters and odbc states. |
| 2674 | Error | 08W87 | -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. |
| 2675 | Error | 08W88 | -1007L | "Unable to start specified database: '%1' is an invalid transaction log" | The specified file is not a valid transaction log. Click here for a list of possible parameters and odbc states. |
| 2676 | Error | 08W72 | -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. |
| 2677 | Error | 08W73 | -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. |
| 2678 | Error | 08W74 | -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. |
| 2679 | Error | 08W75 | -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. |
| 2680 | Error | 08W76 | -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. |
| 2681 | Error | 42WE5 | -1398L | "VERIFY and RENAME cannot be used together in a RESTORE statement" | Since VERIFY will never write to any dbspaces, renaming dbspaces cannot be done during restore verification. Click here for a list of possible parameters and odbc states. |
| 2682 | Error | WT029 | -1394L | "Invalid external prefilter name specified." | External prefilter name specified in the text configuration is invalid. Click here for a list of possible parameters and odbc states. |
| 2683 | Error | WT026 | -1395L | "Invalid external term breaker name specified." | External term breaker name specified in the text configuration is invalid. Click here for a list of possible parameters and odbc states. |
| 2684 | Error | 08W80 | -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. |
| 2685 | Error | 08W81 | -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. |
| 2686 | Error | 08W82 | -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. |
| 2687 | Error | 08W83 | -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. |
| 2688 | Error | 08W84 | -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. |