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 |
|---|---|---|---|---|---|
| 2813 | Error | WC015 | -1140L | "Unable to start database \"%1\": CHAR collation or tailoring not supported on this platform" | The specified CHAR collation is not supported on the current platform. Click here for a list of possible parameters and odbc states. |
| 2814 | Error | WC016 | -1141L | "Unable to start database \"%1\": NCHAR collation or tailoring not supported on this platform" | The specified NCHAR collation is not supported on the current platform. Click here for a list of possible parameters and odbc states. |
| 2815 | Error | 57W04 | -1142L | "Use of statement '%1', which requires feature '%2', is not allowed" | You have attempted to use a statement which requires a feature that was disabled by the server administrator when the database server was started. Click here for a list of possible parameters and odbc states. |
| 2816 | Error | 55W27 | -1143L | "Encryption has not been enabled." | You attempted to use encryption without first enabling it. Call ULEnableStrongEncryption to enable encryption. Click here for a list of possible parameters and odbc states. |
| 2817 | Warning | 01005 | 140L | "Encryption has not been enabled." | An encryption key was provided, but encryption has not been enabled, nor is the database encrypted. Click here for a list of possible parameters and odbc states. |
| 2818 | Error | WC017 | -1144L | "'%1' cannot be used as the encoding specification for '%2' data" | The specified encoding cannot be used for interpreting the given data. For CHAR data, the encoding must be the database's CHAR character encoding and for NCHAR data, it must be the database's NCHAR character encoding. Click here for a list of possible parameters and odbc states. |
| 2819 | Error | 08W97 | -1145L | "Unable to connect: The server did not accept the requested encryption type" | The server only accepts certain encryption types, and the connection's encryption type is not one of the accepted types. The -ec server option is used to configure the encryption types that the server accepts. Click here for a list of possible parameters and odbc states. |
| 2820 | Error | WL009 | -1146L | "LOAD TABLE not allowed on temporary table which has foreign key references from another table" | The LOAD TABLE statement removes all rows in a temporary table upon failure. If a temporary table being loaded caused an error then the foreign rows would be orphaned. Click here for a list of possible parameters and odbc states. |
| 2821 | Error | 08W98 | -1147L | "Database '%1' cannot be started on this platform. See http://ianywhere.com/developer/product_manuals/sqlanywhere/notes/en/endian_corruption_warning.html" | It was determined that the database may be corrupt. More information and instructions on how to proceed are available at: http://ianywhere.com/developer/product_manuals/sqlanywhere/notes/en/endian_corruption_warning.html Click here for a list of possible parameters and odbc states. |
| 2824 | Error | 0AW19 | -1148L | "Feature not supported by the client version or the client interface" | You have attempted to use a feature which the server supports but the client does not. In order to use the feature, you must upgrade the client library or use a different client interface. Some features are not supported by the JConnect or Open Client client interfaces. Click here for a list of possible parameters and odbc states. |
| 2825 | Error | 08W99 | -1149L | "Database '%1' cannot be started on this platform. See http://ianywhere.com/developer/product_manuals/sqlanywhere/notes/en/endian_cant_change_platform.html" | It was determined that the database cannot be started on the current platform because doing so could possibly cause an endian related database file corruption. It will continue to start without problems on a platform with the opposite endian. More information and instructions on how to proceed are available at: http://ianywhere.com/developer/product_manuals/sqlanywhere/notes/en/endian_cant_change_platform.html Click here for a list of possible parameters and odbc states. |
| 2826 | Error | WW091 | -1150L | "The SQL scripts DLL cannot be loaded" | The SQL scripts DLL cannot be loaded. The DLL might be missing or the version found might not match the version of the database server being used. Click here for a list of possible parameters and odbc states. |
| 2827 | Error | WL010 | -1151L | "The logging type ( '%1' ) specified is invalid, not supported or incompatible" | The logging type specified for LOAD TABLE is not supported for the version of the database being used, is incompatible with other specifications of the statement or is not supported for the specific table being loaded into. Click here for a list of possible parameters and odbc states. |
| 2828 | Error | 08WA0 | -1152L | "Password has expired" | You attempted to connect using a valid user ID, but with an expired password. You can change your password by supplying the NewPassword connection parameter along with the current expired password. Click here for a list of possible parameters and odbc states. |
| 2829 | Error | 08WA1 | -1153L | "Password has expired but cannot be changed because the database is read-only" | You attempted to connect to a read-only database using a valid user ID, but with an expired password. The password cannot be changed unless the database is started without the -r option on the database server command line. Removing -r will permit modifications to the database. Click here for a list of possible parameters and odbc states. |
| 2830 | Error | 55W28 | -1154L | "Traced query (%1, %2) does not exist" | You attempted to generate a graphical plan for a query saved by diagnostic tracing, identified by a logging_session_id and query id. However, no such query exists in this database. If it was traced, it was sent to a different database. Click here for a list of possible parameters and odbc states. |
| 2831 | Error | WL011 | -1155L | "Unable to close the cursor on table \"%1\". LOAD TABLE cannot be executed." | You cannot perform LOAD TABLE on a temporary table that has an open cursor on it. An attempt to close the cursor failed. A failed LOAD TABLE would cause all of the rows in the temporary table to be deleted thereby invalidating the cursor. Click here for a list of possible parameters and odbc states. |
| 2832 | Error | WT001 | -1156L | "Argument \"%1\" must be a column reference." | The CONTAINS argument must be a column reference. Click here for a list of possible parameters and odbc states. |
| 2833 | Error | WT002 | -1157L | "All column reference arguments must refer to the same table." | All column references in a CONTAINS query must refer to the same table. Click here for a list of possible parameters and odbc states. |
| 2834 | Error | WT003 | -1158L | "No matching text index." | A single text index must exist on all columns referenced in a CONTAINS query. Click here for a list of possible parameters and odbc states. |