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 |
|---|---|---|---|---|---|
| 08W93 | Error | 2732 | -1063L | "Unable to start database %1: Cannot use read-only mode if auditing is enabled" | The specified database has auditing enabled, and cannot be started read-only. Click here for a list of possible parameters and odbc states. |
| 08W94 | Error | 2759 | -1090L | "Function '%1' has invalid parameter '%2' ('%3')" | An error occurred while evaluating a parameter. Click here for a list of possible parameters and odbc states. |
| 08W95 | Error | 2767 | -1097L | "ATTACH TRACING could not connect to the tracing database" | A connection to the tracing database could not be established. Check your connection string and verify that other clients can connect. Note that if you are trying to attach tracing to another server, it is possible that the connection is being blocked by a firewall. Click here for a list of possible parameters and odbc states. |
| 08W96 | Error | 2768 | -1098L | "A tracing connection is already active" | This database is already participating in a tracing connection, either as the sender (the database being traced) or as the receiver (the tracing database). A database can only send or receive one stream of tracing data at a time. Click here for a list of possible parameters and odbc states. |
| 08W97 | Error | 2819 | -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. |
| 08W98 | Error | 2821 | -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. |
| 08W99 | Error | 2825 | -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. |
| 08WA0 | Error | 2828 | -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. |
| 08WA1 | Error | 2829 | -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. |
| 08WA2 | Error | 2856 | -1179L | "Unable to start database server: missing license file" | It was not possible to start the database server because the server license file was not found. The server license file has the same name as the server executable with the extension ".lic". Click here for a list of possible parameters and odbc states. |
| 08WA5 | Error | 2728 | -1384L | "Unable to stop specified database: %1" | The database server was unable to stop the specified database. Click here for a list of possible parameters and odbc states. |
| 09W02 | Error | 2118 | -187L | "Illegal cursor operation attempt" | You attempted an illegal cursor operation. For example, you may be attempting to OPEN a cursor for a statement that is neither a SELECT nor a BATCH. Click here for a list of possible parameters and odbc states. |
| 09W03 | Error | 2610 | -946L | "Result set not permitted in '%1'" | You attempted to execute a SELECT statement in a context where a result set is not permitted. Click here for a list of possible parameters and odbc states. |
| 09W04 | Error | 2130 | -199L | "INSERT/DELETE on cursor can modify only one table" | You attempted to insert into a cursor and have specified values for more than one table, or you attempted to delete from a cursor that involves a join. Insert into one table at a time. For DELETE, use the FROM clause to specify the table you want to delete from. Click here for a list of possible parameters and odbc states. |
| 09W05 | Error | 2164 | -295L | "Cannot uniquely identify rows in cursor" | You opened a UNIQUE cursor on a SELECT statement for which a set of columns uniquely identifying each row cannot be generated. One of the tables may not be defined with a primary key or uniqueness constraint, or the SELECT statement may involve a UNION, INTERSECT, EXCEPT, or GROUP BY. Click here for a list of possible parameters and odbc states. |
| 09W06 | Error | 2294 | -668L | "Cursor is restricted to FETCH NEXT operations" | An illegal FETCH operation has been detected for a NO SCROLL cursor. For a forward-only cursor the only permitted FETCH operations are FETCH RELATIVE 0 and FETCH NEXT (FETCH RELATIVE 1). Click here for a list of possible parameters and odbc states. |
| 09W07 | Error | 2300 | -674L | "Statement's size limit is invalid" | FIRST or TOP n are used in a SELECT statement to limit the size of a result. The size limit must be a constant integer greater than 0 and less than 32767. Click here for a list of possible parameters and odbc states. |
| 09W08 | Error | 2379 | -734L | "Cannot update or delete an all-NULL row from table '%1'" | You attempted to modify or delete a row in the specified table, which is part of the NULL-supplying side of an outer join. However, the cursor is currently positioned on a derived row that contains an all-NULL row for this table, which is the result of the failure of one or more ON conditions to evaluate to TRUE. Verify that the UPDATE or DELETE statement is correct. Click here for a list of possible parameters and odbc states. |
| 0A000 | Error | 2075 | -134L | "Feature '%1' not implemented" | You attempted to carry out an operation or use a feature that is not implemented in this version of SQL Anywhere. Click here for a list of possible parameters and odbc states. |
| 0A001 | Error | 2762 | -1092L | "The method you attempted to invoke was not enabled for your application" | You attempted to call a method or use a feature that has not been enabled. In UltraLite features are enabled using ULEnable functions or by using ULInitDatabaseManager instead of ULInitDatabaseManagerNoSQL. Click here for a list of possible parameters and odbc states. |