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 |
|---|---|---|---|---|---|
| WW055 | Error | 2653 | -986L | "Invalid procedure type '%1'" | A procedure or function was specified with an invalid type. Click here for a list of possible parameters and odbc states. |
| WW056 | Error | 2654 | -987L | "Invalid procedure subtype '%1' for type '%2'" | A procedure or function was specified with an invalid subtype for the given procedure type. Click here for a list of possible parameters and odbc states. |
| WW057 | Error | 2655 | -988L | "Invalid response from the HTTP server" | The response from the remote HTTP server was invalid. It may have been empty, malformed, missing header information, and so on. Click here for a list of possible parameters and odbc states. |
| WW058 | Error | 2656 | -989L | "NAMESPACE attribute is not valid with procedure type '%1'" | The NAMESPACE attribute is only applicable to procedures of type SOAP. Click here for a list of possible parameters and odbc states. |
| WW059 | Error | 2657 | -990L | "The secure connection to the remote host failed: %1" | The server was unable to initiate a secure connection with the remote host. Click here for a list of possible parameters and odbc states. |
| WW060 | Error | 2658 | -991L | "Clause '%1' has invalid attribute '%2'" | The attribute value specified on the procedure is not valid. Click here for a list of possible parameters and odbc states. |
| WW061 | Warning | 2666 | 136L | "The database was created" | The specified UltraLite database was created using the specified schema when the connection was opened. Click here for a list of possible parameters and odbc states. |
| WW062 | Error | 2670 | -1002L | "The option '%1' is not recognized" | The specified option was not recognized. The option may have been spelled incorrectly. Click here for a list of possible parameters and odbc states. |
| WW063 | Error | 2699 | -1030L | "Secure HTTP connections are not supported on this platform" | A Secure HTTP connection was attempted, but is not supported on this platform. Click here for a list of possible parameters and odbc states. |
| WW064 | Error | 2703 | -1034L | "The '%1' attribute is not valid with procedure type '%2'" | This attribute is not applicable to the given procedure type. Click here for a list of possible parameters and odbc states. |
| 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. |