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 |
|---|---|---|---|---|---|
| 2486 | Error | 0AW11 | -839L | "Download failed because of conflicts with existing rows" | You attempted a download-only synchronization with modified rows in the UltraLite database. There 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. |
| 2487 | Error | 08W62 | -840L | "Incorrect or missing encryption key" | The database is encrypted with a key. There was no key given to start the database, or the key given was incorrect. Click here for a list of possible parameters and odbc states. |
| 2488 | Error | WJ026 | -841L | "The JDK version in '%1' does not match '%2'" | The JDK version specified in the CREATE DATABASE statement does not match the JDK version in the JDK JAR file. Click here for a list of possible parameters and odbc states. |
| 2489 | Error | WJ025 | -842L | "JDK '%1' is not a supported JDK" | Either the JDK version specified in the CREATE DATABASE statement is unsupported or the version in the manifest file of the JDK JAR file is unsupported. Click here for a list of possible parameters and odbc states. |
| 2490 | Error | 5RW37 | -843L | "Cannot find synchronization user with the name '%1'" | You misspelled the name of a synchronization site or you did not qualify it correctly with a user name. Click here for a list of possible parameters and odbc states. |
| 2491 | Error | 5RW39 | -844L | "Cannot find synchronization definition with the name '%1'" | You misspelled the name of a synchronization definition or you did not qualify it correctly with a user name. Click here for a list of possible parameters and odbc states. |
| 2492 | Error | 42U02 | -845L | "Owner '%1' used in a qualified column reference does not match correlation name '%2'" | Your query contains a qualified column reference to a table name, but either a correlation name has been used for that table, or the owner of the table does not match the owner name specified in the column reference. Remove the owner qualification, and qualify column references only by correlation name. Click here for a list of possible parameters and odbc states. |
| 2493 | Error | 42U03 | -846L | "SET clause for column '%1' used incorrectly" | Your UPDATE statement contains an invalid SET clause, for example, there are multiple SET clauses for the same column. Click here for a list of possible parameters and odbc states. |
| 2494 | Error | WJ027 | -847L | "Java SecurityManager class not found: %1" | The class specified is either not a SecurityManager subclass or cannot be found. Click here for a list of possible parameters and odbc states. |
| 2495 | Error | WJ028 | -848L | "Exception occurred while loading Java SecurityManager" | A Java exception occurred while loading the Java SecurityManager for this connection. Click here for a list of possible parameters and odbc states. |
| 2496 | Error | 42R01 | -849L | "Referential integrity actions other than RESTRICT not allowed for temporary tables" | You attempted to specify an unsupported referential integrity action for a temporary table. Click here for a list of possible parameters and odbc states. |
| 2497 | Error | 42R02 | -850L | "Tables related by key constraint must both be permanent, or both be temporary and not created with ON COMMIT DELETE ROWS. For global temporary tables they must both be shared if one is shared." | Tables involved in a key constraint relationship must both be permanent user tables or both be temporary tables not created with ON COMMIT DELETE ROWS. Change the definition of one or both tables using ALTER TABLE. Click here for a list of possible parameters and odbc states. |
| 2498 | Error | 08W63 | -851L | "Decryption error: %1" | An error occurred during decryption. Click here for a list of possible parameters and odbc states. |
| 2499 | Error | 52W42 | -852L | "Table name '%1' is ambiguous" | A statement has referred to a table name that is not unique. Preface the table name by an owner name. Click here for a list of possible parameters and odbc states. |
| 2500 | Warning | 01S02 | 121L | "Cursor option values changed" | The database server could not support the requested cursor option values for the associated query. Similar option settings were substituted. Click here for a list of possible parameters and odbc states. |
| 2501 | Error | 24000 | -853L | "Cursor not in a valid state" | You attempted to use a cursor that is not in a valid state for the attempted operation. For example, the cursor may have encountered an error. Click here for a list of possible parameters and odbc states. |
| 2502 | Error | 42W65 | -854L | "Function or column reference to '%1' in the ORDER BY clause is invalid" | You specified a function or column reference in the ORDER BY clause that is semantically invalid. For example, for DISTINCT queries the ORDER BY clause may only refer to items in the query's select list. Click here for a list of possible parameters and odbc states. |
| 2503 | Error | 42W66 | -855L | "Trigger name '%1' is ambiguous" | A statement has referred to a trigger name that is not unique. Qualify the trigger name with the table and/or owner name. Click here for a list of possible parameters and odbc states. |
| 2504 | Error | 07W08 | -856L | "Invalid sqllen field in SQLDA" | An invalid length was specified in a SQLDA sqllen field. All variable length types must have a non-negative length. The DT_BINARY and DT_VARCHAR types must have length greater than one. Click here for a list of possible parameters and odbc states. |
| 2505 | Error | 0AW12 | -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. |