Messages on this page are sorted by SQLSTATE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL State | Msg Type | Number | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| WE009 | Error | 2482 | -835L | "Event '%1' in use" | You have attempted to drop an event that is currently in use. Click here for a list of possible parameters and odbc states. |
| WE010 | Error | 2800 | -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. |
| WE011 | Warning | 2947 | 146L | "Event notification queue '%1' is full, notification discarded" | The named queue is full and will not receive any event notifications until notifications are read from the queue. The pending notification has been discarded. Click here for a list of possible parameters and odbc states. |
| WE012 | Warning | 2948 | 147L | "Event notifications lost on queue '%1'" | Event notifications have been lost on the named queue. This occurs if there are pending notifications when the queue is destroyed. The notifications are discarded. Click here for a list of possible parameters and odbc states. |
| WE013 | Warning | 2949 | 148L | "Event notification queue '%1' not found warning" | The named event notification queue was not found. The operation will be skipped. Click here for a list of possible parameters and odbc states. |
| WE014 | Error | 2950 | -1263L | "Event notification queue '%1' not found" | The named event notification queue was not found. The operation failed. Click here for a list of possible parameters and odbc states. |
| WE015 | Error | 2951 | -1264L | "Event object name '%1' is not valid" | The given name is not valid for an event object (notification queue or user event). Names are limited in length to 32 characters (bytes), and may not contain certain characters, like '*' or '@'. Click here for a list of possible parameters and odbc states. |
| WE016 | Error | 2952 | -1265L | "Event object named '%1' already exists" | An event object (notification queue or user event) with the given name already exists. Click here for a list of possible parameters and odbc states. |
| WE017 | Error | 2953 | -1266L | "No notification within timeout on queue '%1'" | The pending get-notification operation has timed out. No notification arrived before the given timeout elapsed. Click here for a list of possible parameters and odbc states. |
| WE018 | Error | 2954 | -1267L | "Event parameter '%1' not found" | The named event parameter was not found in the event notification. Click here for a list of possible parameters and odbc states. |
| WI002 | Error | 2862 | -1185L | "Index validation failed for table %1, index %2 with code: %3" | UltraLite database validation failed while validating the specified index. The code provides more specific information on the validation failure. Click here for a list of possible parameters and odbc states. |
| WI003 | Error | 2863 | -1186L | "Database page validation failed with code: %1" | UltraLite database validation failed while validating the database pages. The code provides more specific information on the validation failure. Click here for a list of possible parameters and odbc states. |
| WI004 | Error | 2208 | -311L | "Internal rollback log corrupted" | While processing a COMMIT or ROLLBACK, corruption was found in the internal rollback log. This is a fatal internal error. Click here for a list of possible parameters and odbc states. |
| WI005 | Error | 2120 | -189L | "Unable to find in index '%1' for table '%2'" | This is an internal error. If it can be reproduced, it should be reported to iAnywhere. You should be able to work around the error by dropping and recreating the index. Click here for a list of possible parameters and odbc states. |
| WI006 | Error | 2260 | -503L | No message | No additional information available. Click here for a list of possible parameters and odbc states. |
| WI008 | Error | 2261 | -504L | No message | No additional information available. Click here for a list of possible parameters and odbc states. |
| WI009 | Error | 2288 | -662L | "Cannot serialize Java object with class '%1'" | The Java object cannot be serialized as a persistent database column. Click here for a list of possible parameters and odbc states. |
| WI010 | Error | 2362 | -727L | "The optimizer was unable to construct a valid access plan" | The database server was unable to construct a valid access plan for the given request. This is a SQL Anywhere internal error. If it can be reproduced, it should be reported to iAnywhere. You may be able to work around this problem by modifying the query statement. Click here for a list of possible parameters and odbc states. |
| WI011 | Error | 2633 | -969L | "Required operators excluded" | The database server was unable to construct a valid access plan for the given request because required data flow operators were excluded by the exclude_operators option. Re-enable the required operators to execute the statement. Click here for a list of possible parameters and odbc states. |
| WI111 | Error | 2905 | -1227L | "Internal error, please contact Sybase IQ support. %1." | The multiplex DDL command (create/alter/drop) failed with internal error due to specified reason. Click here for a list of possible parameters and odbc states. |