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 |
|---|---|---|---|---|---|
| WT020 | Error | 2970 | -1283L | "A CONTAINS query is not allowed on the view or derived table '%1'." | A view or derived table can only be queried using CONTAINS if it does not use TOP, FIRST, DISTINCT, GROUP BY, or FOR XML. In addition, the list of columns to search must all come from a single base table in the FROM clause of the view. They cannot come from multiple tables, or from another view or derived table in the FROM clause. Click here for a list of possible parameters and odbc states. |
| WT021 | Error | 2992 | -1304L | "Could not create a new text index for this table with the same settings as \"%1\No message | Two text indexes with the same column list and configuration settings cannot be created for a table. Click here for a list of possible parameters and odbc states. |
| WT022 | Error | 3050 | -1370L | "Text queries cannot contain more than 300 terms." | A text query should contain 300 terms or less. Click here for a list of possible parameters and odbc states. |
| WT023 | Error | 2727 | -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. |
| WT024 | Error | 2724 | -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. |
| WT025 | Error | 2725 | -1391L | "Invalid stoplist value." | The value specified for the stoplist is not valid. Click here for a list of possible parameters and odbc states. |
| WT026 | Error | 2683 | -1395L | "Invalid external term breaker name specified" | External term breaker name specified in the text configuration is invalid. Click here for a list of possible parameters and odbc states. |
| WT027 | Error | 2718 | -1396L | "Error initializing external prefilter" | The external prefilter could not be initialized because of an internal error. Click here for a list of possible parameters and odbc states. |
| WT028 | Error | 2717 | -1393L | "Error initializing external term breaker" | The external term breaker could not be initialized because of an internal error. Click here for a list of possible parameters and odbc states. |
| WT029 | Error | 2682 | -1394L | "Invalid external prefilter name specified" | External prefilter name specified in the text configuration is invalid. Click here for a list of possible parameters and odbc states. |
| WT030 | Error | 2652 | -1492L | "Could not create a text index without external prefilter library on column \"%1\No message | A text configuration object with a specified external prefilter library is required to build a text index on a binary column. Click here for a list of possible parameters and odbc states. |
| WT031 | Error | 2644 | -1493L | "Could not create a text index with external prefilter library on column \"%1\No message | A text configuration object without external prefilter library is required if any column in the text index is not of a binary or string data type. Click here for a list of possible parameters and odbc states. |
| WT032 | Error | 2642 | -1504L | "Error from external library: -%1: %2" | The external library used by the text index has reported the specified error. Click here for a list of possible parameters and odbc states. |
| WT033 | Error | 2596 | -1511L | "Text indexes are not allowed across server types." | Text indexes are not allowed across server types if the query is processed in full-passthrough mode. Click here for a list of possible parameters and odbc states. |
| WT034 | Error | 2561 | -1512L | "Text index with external prefilter cannot contain both binary and string columns" | One or more, but not all, of the columns specified for the text index is of type binary, and the text configuration object has a prefilter library specified. Text indexes using a prefilter library can contain either binary columns or string data type columns, but not both. Click here for a list of possible parameters and odbc states. |
| WT035 | Error | 2530 | -1522L | "Database needs to be upgraded to support the use of external libraries with text indexes." | The current database does not have catalog support for prefilter and term breaker external libraries. To use this feature, upgrade your database to the most recent version. Click here for a list of possible parameters and odbc states. |
| WT036 | Error | 2010 | -1526L | "Text index %1 cannot be used with text procedure %2" | The specified text procedure cannot be used with the text index. The text procedure charset has to correspond to the charset of the text index it is accessing. Click here for a list of possible parameters and odbc states. |
| WU001 | Error | 3166 | -1498L | "'%1' is an unknown property" | The specified property is unknown. Click here for a list of possible parameters and odbc states. |
| WW001 | Error | 2215 | -606L | "The pattern is too long" | The pattern for the LIKE operator is too long. All patterns of 126 characters or less are supported. Some patterns as long as 254 characters are supported, depending on their contents. Patterns longer than 254 characters are not supported. Click here for a list of possible parameters and odbc states. |
| WW002 | Error | 2216 | -607L | "Cannot stop the database server" | The server has determined that it cannot be shut down at this time. Normally, this error should not occur. Click here for a list of possible parameters and odbc states. |