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 |
|---|---|---|---|---|---|
| 2719 | Error | 22030 | -1050L | "Cannot return NULL result as requested data type" | You tried to retrieve a value from the database that was NULL and assign it to a variable that cannot be NULL. Click here for a list of possible parameters and odbc states. |
| 2720 | Error | 42WB6 | -1051L | "Cannot create a materialized view because option '%1' has an inappropriate setting" | You attempted to create a materialized view, but one of the database options is currently set to a value not permitted while creating a materialized view. Click here for a list of possible parameters and odbc states. |
| 2721 | Error | 42WB7 | -1052L | "Cannot update materialized view because option '%1' has an inappropriate setting" | You attempted to update/refresh a materialized view but one of the database options is currently set to a value that is not permitted while updating a materialized view, or, the option's setting does not match the value when the view was created. Click here for a list of possible parameters and odbc states. |
| 2722 | Error | 42W85 | -1053L | "'%1' is an invalid value for '%2'" | You supplied an invalid value for an option. Some options only allow numeric values and some options only allow true or false. Also, many options do not permit the empty string as a value. Click here for a list of possible parameters and odbc states. |
| 2723 | Error | 55W23 | -1054L | "Snapshot isolation disabled or pending" | Snapshot isolation is disabled or its activation is still pending. You must enable snapshot isolation before using it. Click here for a list of possible parameters and odbc states. |
| 2724 | Error | WT024 | -1390L | "An incremental refresh is not possible when handles are exhausted." | Incremental refresh of a MANUAL or AUTO REFRESH text index is not possible when handles are exhausted. You need to rebuild the text index before you can use incremental refresh. Click here for a list of possible parameters and odbc states. |
| 2725 | Error | WT025 | -1391L | "Invalid stoplist value." | The value specified for the stoplist is not valid. Click here for a list of possible parameters and odbc states. |
| 2726 | Error | WB016 | -1057L | "BACKUP clause '%1' conflicts with '%2'" | Clauses specified in the BACKUP STATEMENT are mutually exclusive. Click here for a list of possible parameters and odbc states. |
| 2727 | Error | WT023 | -1389L | "The value for the stoplist cannot be NULL." | The value for a text configuration stoplist cannot be NULL. To remove a stoplist, use the ALTER TEXT CONFIGURATION...DROP STOPLIST statement. Click here for a list of possible parameters and odbc states. |
| 2728 | Error | 08WA5 | -1384L | "Unable to stop specified database: %1" | The database server was unable to stop the specified database. Click here for a list of possible parameters and odbc states. |
| 2729 | Error | 5RW38 | -1060L | "Operation conflict with publication type" | You attempted to perform an operation not applicable to the type of publication. For example, you applied operations specific to a scripted upload publication to a logscan publication. Click here for a list of possible parameters and odbc states. |
| 2730 | Error | 42WB8 | -1061L | "Table created or altered after start of snapshot" | A snapshot transaction attempted to use a table that was created or altered after the transaction began. Click here for a list of possible parameters and odbc states. |
| 2731 | Error | 42WB9 | -1062L | "Statement not allowed during snapshot" | A connection with an outstanding snapshot attempted to use CREATE INDEX, DROP INDEX, ALTER INDEX or ALTER TABLE. Make sure all cursors for the connection are closed. Click here for a list of possible parameters and odbc states. |
| 2732 | Error | 08W93 | -1063L | "Unable to start database %1: Cannot use read-only mode if auditing is enabled" | The specified database has auditing enabled, and cannot be started read-only. Click here for a list of possible parameters and odbc states. |
| 2733 | Error | 42WBA | -1064L | "Update conflict on snapshot transaction" | A snapshot transaction attempted to update or delete a row that was changed by another transaction after the snapshot began. Click here for a list of possible parameters and odbc states. |
| 2734 | Error | 42WBB | -1065L | "Attempt to use snapshot isolation in a non-snapshot transaction" | A transaction tried to use snapshot isolation but did not begin with snapshot isolation. Click here for a list of possible parameters and odbc states. |
| 2735 | Error | WO027 | -1066L | "File system error: %1" | This error results from an error in the underlying file system that was encountered while accessing a file directory as a proxy table. Click here for a list of possible parameters and odbc states. |
| 2736 | Error | 08WA3 | -1372L | "The server is not able to establish TCP/IP connections." | This database server is not able to establish TCP/IP connections. The personal server (dbeng) does not permit TCP/IP connections by default. This error may also occur if a network server (dbsrv) was started with the -xd command line option. The ability to establish TCP/IP connections is required to use diagnostic tracing and application profiling. Click here for a list of possible parameters and odbc states. |
| 2737 | Error | 52W43 | -1068L | "Default dbspace '%1' not found" | You tried to create a table with the default_dbspace option set to a dbspace that could not be found. Click here for a list of possible parameters and odbc states. |
| 2738 | Error | 28W12 | -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. |