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 |
|---|---|---|---|---|---|
| 28W09 | Error | 2266 | -313L | "The login ID '%1' has not been mapped to any database user ID" | You attempted to connect using a login ID that is not mapped to a database user ID and there is no guest database user ID, or you attempted to revoke a login ID that has not been mapped. This can also occur when attempting to connect using an integrated login ID that is a member of more than one mapped group. Click here for a list of possible parameters and odbc states. |
| 28W10 | Error | 2671 | -1003L | "Too many distinct group mappings for integrated user" | The integrated user does not have an explicit mapping in the database but does have group mappings. There are too many distinct group mappings. You must either reduce the number of distinct group mappings or add an explicit mapping for the user. Click here for a list of possible parameters and odbc states. |
| 28W11 | Error | 2713 | -1044L | "Invalid password: %1" | The attempt to create a new user ID or change a password failed. The function specified by the verify_password_function option disallowed the password. Click here for a list of possible parameters and odbc states. |
| 28W12 | Error | 2738 | -1069L | "Kerberos login failed" | The Kerberos login failed due to a failure of the client to authenticate the user's principal with the KDC or a failure of the server to authenticate the client. The most likely causes are the Kerberos principal may not be signed in, the principal's ticket may have expired, or the client, server, or KDC's system time are not within a few minutes of each other. The LogFile connection parameter or the server's -z option may provide more information. Click here for a list of possible parameters and odbc states. |
| 28W13 | Error | 2739 | -1070L | "Kerberos logins are not supported" | The client and/or server does not support Kerberos logins. Kerberos may not be supported by the platform, the Kerberos client software including the GSS-API runtime may not be installed or found on the client, or Kerberos was not enabled on the server. The LogFile connection parameter or the server's -z option may provide more information. Click here for a list of possible parameters and odbc states. |
| 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. |
| 28W16 | Error | 2776 | -1347L | "Use of authority '%1' is not supported on the current database" | The current database is an older database and does not have the capability to support given authority. You must upgrade your database to use this authority. 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. |