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 |
|---|---|---|---|---|---|
| 0A003 | Error | 2945 | -1261L | "This server is not licensed to support '%1' connections" | You attempted to use a connection protocol or api that is not licensed in this edition of SQL Anywhere. Click here for a list of possible parameters and odbc states. |
| 0A004 | Error | 2946 | -1262L | "This edition of SQL Anywhere is not available on this platform" | This edition of SQL Anywhere is not available on this platform. You must use a different license key to use SQL Anywhere on this platform. Click here for a list of possible parameters and odbc states. |
| 0AQ48 | Error | 2597 | -933L | "A log is required for IQ databases" | IQ databases require the use of a transaction log file. Click here for a list of possible parameters and odbc states. |
| 0AW01 | Error | 2077 | -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. |
| 0AW02 | Error | 2076 | -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. |
| 0AW03 | Error | 2230 | -627L | "Disallowed language extension detected in syntax near '%1' on line %2" | The statement you are trying to execute contains syntax that is not allowed with the current setting of the option sql_flagger_error_level. Modify the offending statement or set the sql_flagger_error_level option to a different value. Click here for a list of possible parameters and odbc states. |
| 0AW04 | Error | 2154 | -275L | "Triggers and procedures not supported in runtime server" | You attempted to call a stored procedure or have modified a row in a table on which a trigger is defined and you are using the runtime server. Triggers and stored procedures are not supported in the runtime server. You must run the full server to use these features. Click here for a list of possible parameters and odbc states. |
| 0AW05 | Error | 2335 | -707L | "Statement is not allowed in passthrough mode" | You tried to execute a statement that cannot be executed while in passthrough mode. For example, you may have executed a batch statement. Click here for a list of possible parameters and odbc states. |
| 0AW06 | Error | 2337 | -709L | "Computed columns are not supported in this database" | The current database is an older database and does not have catalog support for computed (materialized) columns. To use this feature, upgrade your database to the most recent version. Click here for a list of possible parameters and odbc states. |
| 0AW07 | Error | 2395 | -749L | "Feature not available with UltraLite" | You attempted to execute a statement or use a feature that is not supported in an UltraLite database. Click here for a list of possible parameters and odbc states. |
| 0AW08 | Error | 2401 | -755L | "You cannot synchronize or upgrade with uncommitted transactions" | You attempted to synchronize or upgrade the schema of an UltraLite database and there are changes in the UltraLite database that have not been committed. Click here for a list of possible parameters and odbc states. |
| 0AW09 | Error | 2441 | -794L | "Synchronization server failed to commit the upload" | You attempted to synchronize an UltraLite database. During the synchronization session, a complete upload stream was sent that could not be committed to the consolidated database. The reason for the upload failure can be found in the synchronization log file. Click here for a list of possible parameters and odbc states. |
| 0AW10 | Error | 2446 | -799L | "DTC transactions are not supported on this platform" | You tried to enlist a DTC transaction on a platform that does not support this feature. Click here for a list of possible parameters and odbc states. |
| 0AW11 | Error | 2486 | -839L | "Download failed because of conflicts with existing rows" | You attempted a download-only synchronization with modified rows in the UltraLite database. These was a conflict between one or more rows in the download stream and rows in the UltraLite database. Click here for a list of possible parameters and odbc states. |
| 0AW12 | Error | 2505 | -857L | "Synchronization failed due to an error on the server: %1" | Synchronization failed at the server. More details can be found in the synchronization log file. Click here for a list of possible parameters and odbc states. |
| 0AW13 | Error | 2517 | -867L | "Cannot change synchronization user_name when status of the last upload is unknown" | The MobiLink server uses the user_name to track synchronizations. If the status of the previous upload is unknown then you must resolve this condition before changing the user. Click here for a list of possible parameters and odbc states. |
| 0AW14 | Error | 2557 | -894L | "Plan can not be generated for this type of statement" | You tried to get the execution plan for a statement type that is not supported. Click here for a list of possible parameters and odbc states. |
| 0AW15 | Error | 2698 | -1029L | "Support for materialized views is not available for this database" | The statement being executed requires support for materialized views, but the database being used does not have the materialized view capability. Click here for a list of possible parameters and odbc states. |
| 0AW16 | Error | 2740 | -1071L | "The %1 algorithm is not available in FIPS mode" | The specified algorithm is not available when the server is running in FIPS mode. Click here for a list of possible parameters and odbc states. |
| 0AW17 | Error | 2790 | -1118L | "Cannot change the MobiLink remote id when the status of the last upload is unknown" | The MobiLink server uses the remote id to track synchronization progress. If the status of the previous upload is unknown then you must resolve this condition before changing the remote id. Click here for a list of possible parameters and odbc states. |