The full-text word-breaker component '%1!s!' used to populate catalog '%2!s!' in a previous SQL Server release is not the current version (component version is '%3!s!', full path is '%4!s!', language requested is %5!s!, language used is %6!s!). This may cause search results to differ slightly from previous releases. To avoid this, rebuild the full-text catalog using the current version of the word-breaker component.
The full-text population on table '%1!s!' cannot be started because the full-text catalog is importing data from existing ...
The full-text protocol handler component '%1!s!' used to populate catalog '%2!s!' in a previous SQL Server release is not ...
The full-text query did not use the value specified for the OPTIMIZE FOR query hint. Only single terms are allowed as values ...
The full-text query has a very complex NEAR clause in the CONTAINS predicate or CONTAINSTABLE function. To ensure that a ...
The full-text word-breaker component '%1!s!' used to populate catalog '%2!s!' in a previous SQL Server release is not the ...
The fulltext catalog upgrade failed because of an inconsistency in metadata between sys.master_files and sys.fulltext_catalogs ...
The fulltext filter daemon host (FDHost) process has stopped abnormally. This can occur if an incorrectly configured or malfunctioning ...
The fulltext query did not use the value specified for the OPTIMIZE FOR hint because the query contained more than one type ...
The fulltext stoplist '%1!s!' already exists in the current database. Duplicate stoplist names are not allowed. Rerun the ...