Messages on this page are sorted by SQLSTATE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL State | Msg Type | Number | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| WW065 | Error | 2711 | -1042L | "Cannot add a comment to a table declared as LOCAL TEMPORARY" | You attempted to add a comment to a table that has been declared as LOCAL TEMPORARY. This is not allowed. Click here for a list of possible parameters and odbc states. |
| WW066 | Error | 2751 | -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. |
| WW067 | Error | 2752 | -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. |
| WW068 | Error | 2756 | -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. |
| WW069 | Error | 2757 | -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. |
| WW070 | Error | 2764 | -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. |
| WW071 | Error | 2765 | -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. |
| WW072 | Error | 2766 | -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. |
| WW073 | Error | 2772 | -1101L | "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. |
| WW074 | Error | 2773 | -1102L | "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. |
| WW075 | Error | 2774 | -1103L | "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. |
| WW077 | Error | 2777 | -1106L | "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. |
| WW078 | Error | 2779 | -1108L | "Unable to access the file system on the device" | On a Palm device, you have tried to utilize the VFS file system, but that feature has not been enabled on the device. Click here for a list of possible parameters and odbc states. |
| WW079 | Error | 2780 | -1109L | "Unable to perform requested operation since this database uses keyless encryption" | The operation you requested on the encryption key failed since the UltraLite database uses keyless encryption. This can occur when you try to change the encryption key for a database that uses keyless encryption (obfuscation for example). Click here for a list of possible parameters and odbc states. |
| WW080 | Error | 2781 | -1110L | "UltraLite cannot synchronize because a synchronization is already running" | You attempted to synchronize an UltraLite database which is already synchronizing. You must wait until the current synchronization completes before starting another. UltraLite allows most operations to run concurrently with synchronization, but only a single synchronization can be active at a time. This is generally caused by two different threads attempting a synchronize call or statement at the same time. Click here for a list of possible parameters and odbc states. |
| WW081 | Error | 2782 | -1111L | "Information for synchronization was not provided" | You must supply information for synchronization in the synchronization call. Click here for a list of possible parameters and odbc states. |
| WW082 | Error | 2783 | -1112L | "Specified file system volume not found for database '%1'" | The file system volume you specified in the database file name was not found. Check the volume name or ordinal. Click here for a list of possible parameters and odbc states. |
| WW083 | Error | 2789 | -1117L | "A row cannot be stored because it exceeds the database page size" | You attempted to insert or update a row which is too large to be stored on a database page. For UltraLite, with the exception of BLOB columns, a row must fit entirely on a single database page. Larger page sizes may be used to accommodate larger rows. Click here for a list of possible parameters and odbc states. |
| WW084 | Error | 2794 | -1122L | "Exceeded maximum of '%1' allowable parameters" | The maximum allowable parameters for the given web client procedure or function has been exceeded. Click here for a list of possible parameters and odbc states. |
| WW085 | Error | 2795 | -1123L | "Invalid mime type '%1'" | The mime type specifier is invalid. Click here for a list of possible parameters and odbc states. |