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 |
|---|---|---|---|---|---|
| 24501 | Error | 2112 | -180L | "Cursor not open" | You attempted to use a cursor that has not been opened. Click here for a list of possible parameters and odbc states. |
| 24502 | Error | 2111 | -172L | "Cursor already open" | You attempted to OPEN a cursor that is already open. Click here for a list of possible parameters and odbc states. |
| 24503 | Error | 2128 | -197L | "No current row of cursor" | You attempted to perform an operation on the current row of a cursor, but the cursor is not positioned on a row. The cursor is before the first row of the cursor, after the last row, or is on a row that has since been deleted. Click here for a list of possible parameters and odbc states. |
| 24504 | Error | 2467 | -820L | "Invalid scroll position '%1'" | You attempted to scroll to a position that is not supported. Scroll positions must be between -2147483647 and 2147483646. Click here for a list of possible parameters and odbc states. |
| 24W01 | Error | 2109 | -170L | "Cursor has not been declared" | You attempted to OPEN a cursor that has not been declared. Click here for a list of possible parameters and odbc states. |
| 26501 | Error | 2073 | -132L | "SQL statement error" | The statement identifier (generated by PREPARE) passed to the database for a further operation is invalid. Click here for a list of possible parameters and odbc states. |
| 28000 | Error | 2039 | -103L | "Invalid user ID or password" | You supplied an invalid user ID or an incorrect password. Click here for a list of possible parameters and odbc states. |
| 28W01 | Error | 2041 | -104L | "Invalid user ID or password on preprocessed module" | You specified an invalid user ID or password when a module was preprocessed. Click here for a list of possible parameters and odbc states. |
| 28W02 | Error | 2257 | -205L | "Integrated logins are not permitted" | The login_mode database option is set to Standard, and you attempted an integrated login. Change the option setting or supply an explicit user ID. Click here for a list of possible parameters and odbc states. |
| 28W03 | Error | 2258 | -206L | "Integrated logins are required, standard logins are not permitted" | The login_mode database option is set to Integrated, and you attempted a standard login. Change the option setting or use an integrated login. Click here for a list of possible parameters and odbc states. |
| 28W04 | Error | 2259 | -245L | "Integrated login failed" | The integrated login failed. You may not have a system account on the server machine. Click here for a list of possible parameters and odbc states. |
| 28W05 | Error | 2262 | -246L | "Integrated logins are not supported for this database" | The current database is an older database and does not have the information to map integrated login IDs to database user IDs. You must upgrade your database to use integrated logins. Click here for a list of possible parameters and odbc states. |
| 28W06 | Error | 2263 | -247L | "The integrated login ID guest can only be mapped to the guest database user ID" | You attempted to map the guest login ID to something other than guest. Click here for a list of possible parameters and odbc states. |
| 28W07 | Error | 2264 | -248L | "Cannot map a login ID to the sys or public user ID" | You attempted to map a login ID to either SYS or PUBLIC. Click here for a list of possible parameters and odbc states. |
| 28W08 | Error | 2265 | -249L | "The login ID '%1' is already mapped to user ID '%2'" | You attempted to map a login ID twice. Click here for a list of possible parameters and odbc states. |
| 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. |