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 |
|---|---|---|---|---|---|
| WT011 | Error | 2842 | -1166L | "Text indexes are not supported for this database." | The current database does not have catalog support for text indexes. To use this feature, upgrade your database to the most recent version. Click here for a list of possible parameters and odbc states. |
| WT012 | Error | 2844 | -1168L | "Cannot alter or drop a text configuration referenced by a text index." | It is not possible to alter or drop a text configuration referenced by a populated text index or currently being used by a text procedure. Either copy the configuration and alter the copy, or close all cursors on text procedures and truncate all indexes that use the configuration. Click here for a list of possible parameters and odbc states. |
| WT013 | Error | 2846 | -1169L | "Cannot access a table that is part of a text index." | It is not possible to directly manipulate tables created as part of a text index. Click here for a list of possible parameters and odbc states. |
| WT014 | Error | 2851 | -1174L | "Cannot create text configuration '%1' because option '%2' has an inappropriate setting" | You attempted an operation that needs to create or alter the database options settings for a text configuration, but one of the options is currently set to a value not permitted for a text configuration. Click here for a list of possible parameters and odbc states. |
| WT015 | Error | 2859 | -1182L | "Command not allowed on IMMEDIATE REFRESH text index" | You cannot use REFRESH TEXT INDEX or TRUNCATE TEXT INDEX on an index that is created with immediate refresh. You cannot alter a text index to use or stop using immediate refresh. Click here for a list of possible parameters and odbc states. |
| WT016 | Error | 2884 | -1207L | "Invalid use of NEAR operator in text query." | Only terms, prefixes, or other NEAR operators are allowed as arguments to a NEAR operator. Click here for a list of possible parameters and odbc states. |
| WT017 | Error | 2894 | -1216L | "The arguments to this procedure must be literal strings." | This procedure only accepts literal strings as arguments. Click here for a list of possible parameters and odbc states. |
| WT018 | Error | 2920 | -1240L | "The provided stoplist is too long." | A text configuration stop list must be less than 8000 bytes. Click here for a list of possible parameters and odbc states. |
| WT019 | Error | 2936 | -1253L | "The text index %1 needs to be refreshed" | There is a text index that matches the query, but it needs to be refreshed before it is used. Click here for a list of possible parameters and odbc states. |
| 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 | 2736 | -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 | 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. |