Messages on this page are sorted by SQLCODE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL Code | Msg Type | Number | SQL State | Message | Possible Cause |
|---|---|---|---|---|---|
| -1129L | Error | 2801 | WW086 | "The '%1' attribute contains mismatched parentheses within '%2'" | The value of the attribute is not valid due to mismatched parenthesis (or possibly braces if specifying a port option). Click here for a list of possible parameters and odbc states. |
| -1130L | Error | 2802 | WW087 | "The '%1' attribute is missing a comma within '%2'" | The value of the attribute is not valid due to a missing comma. Click here for a list of possible parameters and odbc states. |
| -1131L | Error | 2803 | WW088 | "The attribute '%1' sets an option '%2' that is incompatible with '%3'" | The options specified for this attribute are not compatible. Click here for a list of possible parameters and odbc states. |
| -1132L | Error | 2804 | WW089 | "Maximum row size for table '%1' would be exceeded" | You tried to create or alter a table with a maximum row size greater than 64KB. In UltraLite, tables must be defined such that the maximum row size (the sum of the bytes required to store each column) is less than 64KB. Click here for a list of possible parameters and odbc states. |
| -1133L | Error | 2805 | 42W3C | "Invalid trigger type for view '%1'" | You attempted to create a trigger on a view, but the type of trigger is supported on base tables only. Only INSTEAD OF triggers can be created on views. Click here for a list of possible parameters and odbc states. |
| -1134L | Error | 2806 | 42W3D | "Triggers cannot be created on materialized view '%1'" | You attempted to create a trigger on a materialized view. A materialized view is not a valid target for a trigger. Click here for a list of possible parameters and odbc states. |
| -1135L | Error | 2808 | 2201B | "Invalid regular expression: %1 in '%2'" | The specified regular expression is invalid. Click here for a list of possible parameters and odbc states. |
| -1136L | Error | 2809 | 2200C | "Invalid use of escape character '%1'" | The specified escape character cannot be used. Click here for a list of possible parameters and odbc states. |
| -1137L | Error | 2810 | 2200B | "Escape character conflict '%1'" | The specified escape character cannot be used. Click here for a list of possible parameters and odbc states. |
| -1138L | Error | 2811 | WW090 | "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. |
| -1139L | Error | 2812 | 0AW18 | "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. |
| -1140L | Error | 2813 | WC015 | "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. |
| -1141L | Error | 2814 | WC016 | "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. |
| -1142L | Error | 2815 | 57W04 | "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. |
| -1143L | Error | 2816 | 55W27 | "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. |
| -1144L | Error | 2818 | WC017 | "'%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. |
| -1145L | Error | 2819 | 08W97 | "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. |
| -1146L | Error | 2820 | WL009 | "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. |
| -1147L | Error | 2821 | 08W98 | "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. |
| -1148L | Error | 2824 | 0AW19 | "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. |