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 |
|---|---|---|---|---|---|
| 2809 | Error | 2200C | -1136L | "Invalid use of escape character '%1'" | The specified escape character cannot be used. Click here for a list of possible parameters and odbc states. |
| 2810 | Error | 2200B | -1137L | "Escape character conflict '%1'" | The specified escape character cannot be used. Click here for a list of possible parameters and odbc states. |
| 2811 | Error | WW090 | -1138L | "The mirror '%1' does not match database '%2'" | The named mirror file does not correspond to the database file. This could happen if the database was not shut down properly, or if the wrong mirror file was specified. The mirror file must be moved or discarded before proceeding, or a different mirror specified. Click here for a list of possible parameters and odbc states. |
| 2812 | Error | 0AW18 | -1139L | "The Remote Data Services feature is not supported on this platform" | You attempted to use a Remote Data Services feature, however, Remote Data Services are not supported on this platform. Click here for a list of possible parameters and odbc states. |
| 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. |
| 2822 | Error | QFA62 | -1320L | "Error raised by user-defined function: %1" | An error was raised by a user-defined function. Click here for a list of possible parameters and odbc states. |
| 2823 | Error | 42WE0 | -1330L | "The function '%1' does not allow use of the '%2' clause" | You have attempted to use the specified SQL clause within the context of a function that does not permit such use. Note that the function may have been used directly in the query or indirectly within a named window. 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. |