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 |
|---|---|---|---|---|---|
| 2749 | Error | 42WBE | -1080L | "Cannot revoke these permissions while user '%1' is actively replicating transactions" | You attempted to revoke permissions from a user while there are transactions currently being replicated for that user. This is not allowed. Click here for a list of possible parameters and odbc states. |
| 2750 | Error | 55W24 | -1081L | "Could not refresh tracing: at least one enabled tracing level must be specified" | Table sa_diagnostic_tracing_level contains no rows (tracing levels) or no tracing levels are enabled. Click here for a list of possible parameters and odbc states. |
| 2751 | Error | WW066 | -1082L | "Could not refresh tracing: invalid tracing specification on sa_diagnostic_tracing_level row %1" | You specified an invalid combination of values for the tracing level. Some invalid combinations are: specified condition is not valid for the tracing type, or specified tracing type is not valid for the scope. Click here for a list of possible parameters and odbc states. |
| 2752 | Error | WW067 | -1083L | "Could not refresh tracing: failed to find object %1 on row %2" | You misspelled the object name, or you did not qualify the name with user (and, possibly, table) name. For example, you might have referred to Employees instead of "DBA"."Employees", or you might have referred to Employees_trigger instead of "DBA"."Employees"."Employees_trigger". Click here for a list of possible parameters and odbc states. |
| 2753 | Error | 57W02 | -1084L | "Use of feature '%1' is not allowed" | You have attempted to use a feature that was disabled by the server administrator when the database server was started. Click here for a list of possible parameters and odbc states. |
| 2754 | Error | 42WC0 | -1085L | "Duplicate key column (%1)" | You supplied a duplicate column name in the list of columns for the key of a primary key, foreign key, or unique constraint, or an index. Click here for a list of possible parameters and odbc states. |
| 2755 | Error | 42Z00 | -1086L | "Write access was denied" | A write attempt to an UltraLite database in read-only mode was denied. Note that UltraLite databases cannot be modified while sending an upload to MobiLink. Click here for a list of possible parameters and odbc states. |
| 2756 | Error | WW068 | -1087L | "Could not refresh tracing: volatile_statistics have to be collected in order for %1 specified on row %2 to be collected" | Volatile statistics have to be collected in order for the non-volatile and connection statistics to be collected. Click here for a list of possible parameters and odbc states. |
| 2757 | Error | WW069 | -1088L | "ATTACH TRACING TO LOCAL DATABASE cannot be used with a strongly encrypted database" | The local database is strongly encrypted, so you cannot use the LOCAL DATABASE clause of the ATTACH TRACING statement. You must specify a connection string with the encryption key for the database. Click here for a list of possible parameters and odbc states. |
| 2758 | Error | 52W26 | -1089L | "Invalid commit action for shared temporary table" | A global shared temporary table must be declared as ON COMMIT PRESERVE ROWS or NOT TRANSACTIONAL. Click here for a list of possible parameters and odbc states. |
| 2759 | Error | 08W94 | -1090L | "Function '%1' has invalid parameter '%2' ('%3')" | An error occurred while evaluating a parameter. Click here for a list of possible parameters and odbc states. |
| 2760 | Error | 23508 | -1091L | "Constraint '%1' violated: Invalid value in table '%2'" | You attempted an insert or update that violates a CHECK constraint. A CHECK constraint is violated if it evaluates to FALSE; it is deemed to hold if the condition evaluates to TRUE or UNKNOWN. Click here for a list of possible parameters and odbc states. |
| 2761 | Warning | 01W25 | 138L | "Publication predicates were not evaluated" | Publication predicates were not evaluated because UltraLite was initialized without SQL support. The table will be uploaded as if no publication predicate was specified for the table. Click here for a list of possible parameters and odbc states. |
| 2762 | Error | 0A001 | -1092L | "The method you attempted to invoke was not enabled for your application" | You attempted to call a method or use a feature that has not been enabled. In UltraLite features are enabled using ULEnable functions or by using ULInitDatabaseManager instead of ULInitDatabaseManagerNoSQL. Click here for a list of possible parameters and odbc states. |
| 2763 | Error | 54W09 | -1093L | "The size of the character column, variable, or value data type exceeds 32767" | The declaration or conversion has specified a character type with byte length greater than 32767. Click here for a list of possible parameters and odbc states. |
| 2764 | Error | WW070 | -1094L | "The http header '%1' is reserved and cannot be modified" | The specified http header is reserved and cannot be modified. Click here for a list of possible parameters and odbc states. |
| 2765 | Error | WW071 | -1095L | "The specified http header contains illegal or non-ASCII characters" | Http headers must contain printable ASCII characters. Click here for a list of possible parameters and odbc states. |
| 2766 | Error | WW072 | -1096L | "The specified http header is malformed" | The http header is missing the colon delimiter or a folding construct is malformed. Click here for a list of possible parameters and odbc states. |
| 2767 | Error | 08W95 | -1097L | "ATTACH TRACING could not connect to the tracing database" | A connection to the tracing database could not be established. Check your connection string and verify that other clients can connect. Note that if you are trying to attach tracing to another server, it is possible that the connection is being blocked by a firewall. Click here for a list of possible parameters and odbc states. |
| 2768 | Error | 08W96 | -1098L | "A tracing connection is already active" | This database is already participating in a tracing connection, either as the sender (the database being traced) or as the receiver (the tracing database). A database can only send or receive one stream of tracing data at a time. Click here for a list of possible parameters and odbc states. |