Messages on this page are sorted by SQLCODE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL Code | Msg Type | Number | SQL State | Message | Possible Cause |
|---|---|---|---|---|---|
| -1088L | Error | 2757 | WW069 | "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. |
| -1089L | Error | 2758 | 52W26 | "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. |
| -1090L | Error | 2759 | 08W94 | "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. |
| -1091L | Error | 2760 | 23508 | "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. |
| -1092L | Error | 2762 | 0A001 | "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. |
| -1093L | Error | 2763 | 54W09 | "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. |
| -1094L | Error | 2764 | WW070 | "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. |
| -1095L | Error | 2765 | WW071 | "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. |
| -1096L | Error | 2766 | WW072 | "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. |
| -1097L | Error | 2767 | 08W95 | "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. |
| -1098L | Error | 2768 | 08W96 | "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. |
| -1099L | Error | 2769 | 55W25 | "Transact-SQL outer joins are currently disabled" | The ability to specify a Transact-SQL outer join in a query is currently disabled by the setting of the tsql_outer_joins connection option. Transact-SQL outer joins are deprecated in this release of SQL Anywhere. Click here for a list of possible parameters and odbc states. |
| -1100L | Error | 2771 | WW045 | "The operation failed because column '%1''s type does not support streaming" | The only column types that support streaming are: BINARY, LONG BINARY, VARCHAR and LONG VARCHAR. This error could also occur when allocating a stream object twice on the same column. Click here for a list of possible parameters and odbc states. |
| -1101L | Error | 2772 | WW073 | "Column '%1' not part of any indexes in its containing table" | The specified column is not part of any indexes belonging to the containing table. Click here for a list of possible parameters and odbc states. |
| -1102L | Error | 2773 | WW074 | "Unable to retry download because upload is not finished" | The MobiLink server could not restart the download because the MobiLink server has not received the entire upload stream. Click here for a list of possible parameters and odbc states. |
| -1103L | Error | 2774 | WW075 | "No partial download was found" | A partial download was not found for the synchronizing user. This error could occur if trying to resume from a non-existent partial download or trying to rollback a non-existent partial download. Click here for a list of possible parameters and odbc states. |
| -1104L | Error | 2775 | 54W10 | "Too many users in database" | You have exceeded the maximum number of users permitted to access the database. The maximum number of users that are allowed granted access to a single UltraLite database is four. Click here for a list of possible parameters and odbc states. |
| -1106L | Error | 2777 | WW077 | "Too many publications specified for operation" | You have specified too many publications for the required operation. For example, when retrieving the last download timestamp, you are only allowed to select one publication. Click here for a list of possible parameters and odbc states. |
| -1107L | Error | 2778 | 54W11 | "Too many references to a BLOB" | You have exceeded the maximum number of references to a particular BLOB. In UltraLite you may have at most 256 references to any one particular BLOB. Click here for a list of possible parameters and odbc states. |
| -1108L | Error | 2779 | WW078 | "Unable to access the filesystem on the device" | On a Palm device, you have tried to utilize the VFS filesystem, but that feature has not been enabled on the device. Click here for a list of possible parameters and odbc states. |