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 |
|---|---|---|---|---|---|
| 2799 | Error | 42W3B | -1127L | "Positioned update operation attempted on a view with an INSTEAD OF trigger" | You attempted a positioned update, positioned delete, put, or wide insert operation that would involve an INSTEAD OF trigger on a view (possibly nested). These operations are not supported with INSTEAD OF triggers on views. Click here for a list of possible parameters and odbc states. |
| 2800 | Error | WE010 | -1128L | "Start date/time for non-recurring event '%1' is in the past" | You have specified an event starting date or time that has already passed, and the event is not recurring. Click here for a list of possible parameters and odbc states. |
| 2801 | Error | WW086 | -1129L | "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. |
| 2802 | Error | WW087 | -1130L | "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. |
| 2803 | Error | WW088 | -1131L | "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. |
| 2804 | Error | WW089 | -1132L | "Maximum row size for table '%1' would be exceeded" | You tried to create or alter a table with a maximum row size greater than 64 KB. 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 64 KB. Click here for a list of possible parameters and odbc states. |
| 2805 | Error | 42W3C | -1133L | "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. |
| 2806 | Error | 42W3D | -1134L | "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. |
| 2807 | Error | 42WE1 | -1331L | "The function '%1' requires the use of the '%2' clause" | You have attempted to invoke the specified function without the use of a mandatory SQL clause within the context of the function. 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. |
| 2808 | Error | 2201B | -1135L | "Invalid regular expression: %1 in '%2'" | The specified regular expression is invalid. Click here for a list of possible parameters and odbc states. |
| 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 access feature is not supported on this platform" | You attempted to use a remote data access feature; however, remote data access is 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 ULEnableAesDBEncryption or ULEnableAesFipsDBEncryption 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. |