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 |
|---|---|---|---|---|---|
| 28W14 | Error | 2743 | -1074L | "Login mode '%1' not permitted by login_mode setting" | You attempted to connect using a login mode not included in the current login_mode database option setting. Change the option setting or connect using a different login mode. Click here for a list of possible parameters and odbc states. |
| 28W15 | Error | 2889 | -1212L | "Connection disallowed by login policy for this user" | A connection attempt was disallowed based on the login policy for the user. It may be necessary for a user with DBA authority to reset this user via the ALTER USER statement. Click here for a list of possible parameters and odbc states. |
| 2D501 | Error | 2152 | -273L | "COMMIT/ROLLBACK not allowed within trigger actions" | You attempted to execute a statement that is not allowed while performing a trigger action. COMMIT and ROLLBACK statements cannot be executed from a trigger. Click here for a list of possible parameters and odbc states. |
| 33000 | Error | 2248 | -642L | "Invalid SQL descriptor name" | You attempted to deallocate a descriptor that has not been allocated. Click here for a list of possible parameters and odbc states. |
| 37505 | Error | 2100 | -154L | "Wrong number of parameters to function '%1'" | You supplied an incorrect number of parameters to a database function. Click here for a list of possible parameters and odbc states. |
| 38W01 | Error | 2575 | -910L | "System command failed with return code %1" | A non-zero return code resulted when executing a system command. Click here for a list of possible parameters and odbc states. |
| 3B001 | Error | 2174 | -220L | "Savepoint '%1' not found" | You attempted to rollback to a savepoint that does not exist. Click here for a list of possible parameters and odbc states. |
| 3B002 | Error | 2175 | -221L | "ROLLBACK TO SAVEPOINT not allowed" | You attempted a ROLLBACK TO SAVEPOINT within an atomic operation to a savepoint established before the atomic operation. Click here for a list of possible parameters and odbc states. |
| 3BW01 | Error | 2177 | -213L | "Savepoints require a rollback log" | You cannot use savepoints when the database server is running in bulk mode without a rollback log. Click here for a list of possible parameters and odbc states. |
| 3BW02 | Error | 2176 | -222L | "Result set not allowed from within an atomic compound statement" | You used a SELECT statement with no INTO clause or a RESULT CURSOR statement within an atomic compound statement. Click here for a list of possible parameters and odbc states. |
| 40000 | Error | 2189 | -300L | "Run time SQL error -- %1" | An internal database error occurred. If it can be reproduced, it should be reported to iAnywhere. You may be able to work around this problem by modifying the associated query statement. Click here for a list of possible parameters and odbc states. |
| 40001 | Error | 2194 | -306L | "Deadlock detected" | You attempted to read or write a row and it is locked by another user. Also, the other user is blocked directly or indirectly on your own transaction. This is a deadlock situation and your transaction has been chosen as the one to rollback. Click here for a list of possible parameters and odbc states. |
| 40W01 | Error | 2190 | -301L | "Internal database error %1 -- transaction rolled back" | An internal database error occurred. If it can be reproduced, it should be reported to iAnywhere. A ROLLBACK statement has been automatically executed. Click here for a list of possible parameters and odbc states. |
| 40W02 | Error | 2191 | -302L | "Terminated by user -- transaction rolled back" | You canceled a statement while the database was executing. A ROLLBACK statement has been automatically executed. Click here for a list of possible parameters and odbc states. |
| 40W03 | Error | 2192 | -304L | "Disk full '%1' -- transaction rolled back" | Your hard disk is out of space. A ROLLBACK statement has been automatically executed. Click here for a list of possible parameters and odbc states. |
| 40W04 | Error | 2193 | -305L | "I/O error %1 -- transaction rolled back" | SQL Anywhere has detected a problem with your hard disk. A ROLLBACK statement has been automatically executed. Click here for a list of possible parameters and odbc states. |
| 40W05 | Error | 2513 | -303L | "Disk write failure '%1' -- transaction rolled back" | A disk write failed. A ROLLBACK statement has been automatically executed. Click here for a list of possible parameters and odbc states. |
| 40W06 | Error | 2195 | -307L | "All threads are blocked" | You attempted to read or write a row and it is locked by another user. Also, all other threads (see the -gn server option) are blocked waiting for a lock to be released. This is a deadlock situation and your transaction has been chosen as the one to rollback. Click here for a list of possible parameters and odbc states. |
| 40W07 | Error | 2196 | -308L | "Connection was terminated" | Your database connection has been terminated and your transaction has been rolled back. The connection may have been terminated because a DBA executed a DROP CONNECTION statement, or because the database server was shut down, or because your network connection to the database server was interrupted. Click here for a list of possible parameters and odbc states. |
| 40W08 | Error | 2361 | -309L | "Memory error -- transaction rolled back" | The UltraLite runtime has received an unexpected error from the system calls being used to store the UltraLite database. For example, a write to persistent memory failed. This is an internal error and indicates faulty or corrupt persistent storage on the device. A ROLLBACK statement has been automatically executed. Click here for a list of possible parameters and odbc states. |