Messages on this page are sorted by Sybase error code. Locate the appropriate code in the table below, and click the link for a full description of the message.
| Number | Msg Type | SQL State | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| 2065 | Error | 42W01 | -120L | "User '%1' already has GRANT permission" | You attempted to give GRANT OPTION permission to a user that already has it. Click here for a list of possible parameters and odbc states. |
| 2066 | Error | 42501 | -121L | "Permission denied: %1" | You do not have the required permission to perform the specified action. The message specifies the actual permission required and the object being acted upon. Click here for a list of possible parameters and odbc states. |
| 2067 | Error | 42W02 | -122L | "Operation would cause a group cycle" | You attempted to add a member to group that would result in a member belonging to itself. The membership may be direct or indirect. Click here for a list of possible parameters and odbc states. |
| 2068 | Error | 42W03 | -123L | "User '%1' is not a user group" | You attempted to add a member to group, but the user ID specified as a group has not been granted GROUP permission. Click here for a list of possible parameters and odbc states. |
| 2069 | Error | 42W34 | -312L | "User '%1' already has membership in group '%2'" | You attempted to give a membership in a group to a user that already has such membership. Click here for a list of possible parameters and odbc states. |
| 2070 | Error | 07W02 | -130L | "Invalid statement" | The statement identifier generated by a PREPARE passed to the database for a further operation is invalid. Click here for a list of possible parameters and odbc states. |
| 2071 | Error | 42W04 | -131L | "Syntax error near '%1' %2" | The database server cannot understand the statement you are trying to execute. If you used a keyword (such as DATE) for a column name, try enclosing the keyword in quotation marks ("DATE"). Click here for a list of possible parameters and odbc states. |
| 2072 | Error | 42W48 | -687L | "Syntax error, cannot specify IQ specific options without specifying IQ PATH" | The database server cannot understand the statement you are trying to execute. If you used a keyword (such as DATE) for a column name, try enclosing the keyword in quotation marks ("DATE"). Click here for a list of possible parameters and odbc states. |
| 2073 | Error | 26501 | -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. |
| 2074 | Error | 07W03 | -133L | "Invalid prepared statement type" | This is an internal error. If it can be reproduced, it should be reported to iAnywhere. Click here for a list of possible parameters and odbc states. |
| 2075 | Error | 0A000 | -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. |
| 2076 | Error | 0AW02 | -611L | "Transact-SQL feature not supported" | You attempted to use a Transact-SQL feature that is not supported in SQL Anywhere. Click here for a list of possible parameters and odbc states. |
| 2077 | Error | 0AW01 | -135L | "Language extension" | You used a SQL statement that may be valid in some versions of SQL, but not in SQL Anywhere. Click here for a list of possible parameters and odbc states. |
| 2078 | Error | 52W13 | -138L | "Dbspace '%1' not found" | You tried to access a dbspace that the database server could not find. Click here for a list of possible parameters and odbc states. |
| 2079 | Error | 52012 | -139L | "More than one table is identified as '%1'" | You identified two tables in the same FROM clause with the same correlation name. Click here for a list of possible parameters and odbc states. |
| 2080 | Error | 08004 | -140L | "User ID '%1' does not exist" | You used a user ID that does not exist. Click here for a list of possible parameters and odbc states. |
| 2081 | Error | 42W33 | -141L | "Table '%1' not found" | You misspelled the name of a table, or you did not qualify a table name with the owner name. For example, you might have referred to "Employees" instead of "DBA"."Employees". Click here for a list of possible parameters and odbc states. |
| 2082 | Error | 52W02 | -142L | "Correlation name '%1' not found" | You misspelled a correlation name, or you used a table name instead of the correlation name. Click here for a list of possible parameters and odbc states. |
| 2083 | Error | 52005 | -834L | "Column '%1' not found in table '%2'" | You misspelled the name of a column, or the column you are looking for is in a different table. Click here for a list of possible parameters and odbc states. |
| 2084 | Error | 52002 | -144L | "Column '%1' found in more than one table -- need a correlation name" | You have not put a correlation name on a column that is found in more than one of the tables referenced in a query. You need to add a correlation name to the reference. Click here for a list of possible parameters and odbc states. |