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 |
|---|---|---|---|---|---|
| 2400 | Error | 08W54 | -754L | "Parse error: %1" | An invalid data source name was used in the connection string. Click here for a list of possible parameters and odbc states. |
| 2401 | Error | 0AW08 | -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. |
| 2402 | Error | WJ021 | -756L | "Cannot uniquely identify column '%2' of table '%1' in the current JDBC resultset" | Failed to identify a column in a JDBC resultset with the given table name and column name. This can happen if the given names are not found or if they are ambiguous. Click here for a list of possible parameters and odbc states. |
| 2403 | Error | 5RW10 | -289L | "Multiple consolidated users cannot be defined" | You attempted to grant consolidated permissions when your database already has a consolidated user, or attempted to grant consolidated permissions to multiple users in a single statement. Click here for a list of possible parameters and odbc states. |
| 2404 | Error | 55W08 | -757L | "Modifications not permitted for read-only database" | You attempted an update operation on a database that was declared as read-only. Click here for a list of possible parameters and odbc states. |
| 2405 | Error | WJ022 | -758L | "The database does not support the Java Virtual Machine" | The Java Virtual Machine could not be started because the database does not have the proper support. It may be that the database was created with an older version of the software, or was created with the Java support disabled. If the database was created with an older version of the software the database should be upgraded to the most recent version. If the database was created with Java support disabled, then the instjava.sql script should be run against the database to enable Java support. Click here for a list of possible parameters and odbc states. |
| 2406 | Error | 07W05 | -759L | "SQLDA data type invalid" | The data type specified for a SQLDA variable is invalid. Click here for a list of possible parameters and odbc states. |
| 2407 | Error | 07W06 | -760L | "Invalid SQL identifier" | An invalid identifier was supplied through the C language interface. For example, you may have supplied a NULL string for a cursor name. Click here for a list of possible parameters and odbc states. |
| 2408 | Error | WJ023 | -762L | "'%1' is not a public Java class, and cannot be referenced from SQL" | Only public Java classes installed into the database are accessible from SQL. Click here for a list of possible parameters and odbc states. |
| 2409 | Error | WJ024 | -763L | "'%1' is not a public Java reference, and cannot be referenced from SQL" | The dotted expression is neither a public Java class nor a Java variable. Click here for a list of possible parameters and odbc states. |
| 2410 | Error | 08W55 | -764L | "Server not found and unable to autostart" | Could not connect to a server, and was unable to autostart a server. Autostart may have failed because no database file was supplied. Click here for a list of possible parameters and odbc states. |
| 2411 | Error | 5RW11 | -765L | "Synchronization message type '%1' not found" | You referred to a synchronization message type that is not defined in this database. Click here for a list of possible parameters and odbc states. |
| 2412 | Warning | WB011 | 119L | "Unable to open backup log '%1'" | The server was unable to open the backup log to record the execution of a BACKUP or RESTORE statement. Check the settings of the environment variables used to locate the backup log file. The directory to contain the log must already exist. Click here for a list of possible parameters and odbc states. |
| 2413 | Error | 42U00 | -766L | "View references '%1', which is a temporary object. Views can only refer to permanent objects" | Views must refer only to permanent objects, not to temporary objects such as local temporary tables. Click here for a list of possible parameters and odbc states. |
| 2414 | Error | 5RW12 | -767L | "Cannot find synchronization subscription with the name '%1'" | You misspelled the name of a synchronization subscription or you did not qualify it correctly with a user name. Click here for a list of possible parameters and odbc states. |
| 2415 | Error | 5RW13 | -768L | "Cannot subscribe to '%1'" | Some publications cannot be subscribed to, such as a synchronization publication. Click here for a list of possible parameters and odbc states. |
| 2416 | Error | 5RW14 | -769L | "Cannot modify synchronization entry using ALTER PUBLICATION" | You attempted to modify a synchronization entry using an ALTER PUBLICATION statement. Click here for a list of possible parameters and odbc states. |
| 2417 | Error | 5RW15 | -770L | "Cannot modify publication entry using ALTER SYNCHRONIZATION" | You attempted to modify a publication entry using an ALTER SYNCHRONIZATION statement. Click here for a list of possible parameters and odbc states. |
| 2418 | Error | WE001 | -771L | "Event '%1' not found" | You have attempted to reference an event with a name that does not exist in the database. Click here for a list of possible parameters and odbc states. |
| 2419 | Error | WE002 | -772L | "Event '%1' already exists" | You have attempted to create an event with a name that already exists in the database. Click here for a list of possible parameters and odbc states. |