SQL Server Errors or Failures from Error: 30047 to Error: 30068

Error: 30047, Severity: 16, The user does not have permission to %.*ls stoplist ‘%.*ls’.

Error: 30048, Severity: 10, Informational: Ignoring duplicate thesaurus rule ‘%ls’ while loading thesaurus file for LCID %d. A duplicate thesaurus phrase was encountered in either the _{section of an expansion rule or the section of a replacement rule. This causes an ambig
Error: 30049, Severity: 17, Fulltext thesaurus internal error (HRESULT = ‘0x%08x’)
Error: 30050, Severity: 16, Both the thesaurus file for lcid ‘%d’ and the global thesaurus could not be loaded.
Error: 30051, Severity: 16, Phrases longer than 512 unicode characters are not allowed in a thesaurus file. Phrase: ‘%ls’.
Error: 30052, Severity: 16, The full-text query has a very complex NEAR clause in the CONTAINS predicate or CONTAINSTABLE function. To ensure that a NEAR clause runs successfully, use only six or fewer terms. Modify the query to simplify the condition by removing prefixes or repeate
Error: 30053, Severity: 16, An error has occurred during the full-text query. Common causes include: word-breaking errors or timeout, FDHOST permissions/ACL issues, service account missing privileges, malfunctioning IFilters, communication channel issues with FDHost and sqlservr.exe}

_{Error: 30055, Severity: 10, Full-text catalog import has started for full-text catalog ‘%ls’ in database ‘%ls’.
Error: 30056, Severity: 10, Full-text catalog import has finished for full-text catalog ‘%ls’ in database ‘%ls’. %d fragments and %d keywords were processed.
Error: 30057, Severity: 10, Upgrade option ‘%ls’ is being used for full-text catalog ‘%ls’ in database ‘%ls’.
Error: 30058, Severity: 16, Properties of zero length cannot be added to a search property list. Specify a search property name that contains at least one character and that is unique to the specified search property list. For a list of the search properties on the current database,
Error: 30059, Severity: 16, A fatal error occurred during a full-text population and caused the population to be cancelled. Population type is: %s; database name is %s (id: %d); catalog name is %s (id: %d); table name %s (id: %d). Fix the errors that are logged in the full-text craw}

_{Error: 30060, Severity: 16, The import population for database %ls (id: %d), catalog %ls (id: %d) is being cancelled because of a fatal error (‘%ls’). Fix the errors that are logged in the full-text crawl log. Then resume the import either by detaching the database and re-attaching
Error: 30061, Severity: 17, The SQL Server failed to create full-text filterdata directory. This might be because FulltextDefaultPath is invalid or SQL Server service account does not have permission. Full-text blob indexing will fail until this issue is resolved. Restart SQL Server
Error: 30062, Severity: 17, The SQL Server failed to load FDHost service group sid. This might be because installation is corrupted.
Error: 30063, Severity: 10, Warning: SQL Server could not set fdhost.exe processor affinity to %d because the value is not valid.
Error: 30064, Severity: 17, SQL Server failed to set security information on the full-text FilterData directory in the FTData folder. Full-text indexing of some types of documents may fail until this issue is resolved. You will need to repair the SQL Server installation.
Error: 30065, Severity: 10, Filegroup ‘%ls’ is offline, readonly, or no data file. Full-text population on table ‘%ls’ is not resumed. Resume full-text population after fixing the filegroup status.
Error: 30067, Severity: 10, Warning: The detach operation cannot delete a full-text index created on table ‘%ls’ in database ‘%ls’ because the index is on a read-only filegroup. To drop the full-text index, re-attach the database, change the read-only filegroup to read/write access
Error: 30068, Severity: 10, During the database upgrade, the full-text filter component ‘%ls’ that is used by catalog ‘%ls’ was successfully verified. Component version is ‘%ls’; Full path is ‘%.*ls’.}

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.