SQL Server Errors or Failures from Error: 30026 to Error: 30046

SQLServerF1

Error: 30026, Severity: 16, The search property list ‘%.*ls’ already exists in the current database. Duplicate search property list names are not allowed. Rerun the statement and specify a unique name for the search property list. For a list of the search property lists on the curre

Error: 30027, Severity: 10, The full-text index is in an inconsistent state because the search property list of the full-text index was reconfigured using the WITH NO POPULATION clause. To bring the full-text index into a consistent state, start a full population using the statement
Error: 30028, Severity: 17, Failed to get pipeline interface for ‘%ls’, resulting in error: 0x%X. There is a problem communicating with the host controller or filter daemon host.
Error: 30029, Severity: 17, The full-text host controller failed to start. Error: 0x%X.
Error: 30030, Severity: 16, The search property ‘%.*ls’ does not exist, or you do not have permission to perform this action. Verify that the correct search property is specified and that you have the permission required by the Transact-SQL statement. For a list of the search proper

Error: 30031, Severity: 17, A full-text master merge failed on full-text catalog ‘%ls’ in database ‘%.*ls’ with error 0x%08X.
Error: 30032, Severity: 16, The stoplist ‘%.*ls’ does not contain fulltext stopword ‘%.*ls’ with locale ID %d. Specify a valid stopword and locale identifier (LCID) in the Transact-SQL statement.
Error: 30033, Severity: 16, The stoplist ‘%.*ls’ already contains full-text stopword ‘%.*ls’ with locale ID %d. Specify a unique stopword and locale identifier (LCID) in the Transact-SQL statement.
Error: 30034, Severity: 16, Full-text stoplist ‘%.*ls’ cannot be dropped because it is being used by at least one full-text index. To identify which full-text index is using a stoplist: obtain the stoplist ID from the stoplist_id column of the sys.fulltext_indexes catalog view, and
Error: 30035, Severity: 16, The search property ‘%.*ls’ already exists in the search property list. Specify a search property name that is unique within the specified search property list. For a list of the search properties on the current database, use the sys.registered_search_pro

Error: 30036, Severity: 16, Search property list ‘%.*ls’ cannot be dropped because it is being used by at least one full-text index. To identify the full-text indexes that are using the search property list, obtain the search property list id from the property_list_id column of the
Error: 30037, Severity: 16, An argument passed to a fulltext function is not valid.
Error: 30038, Severity: 17, Fulltext index error during compression or decompression. Full-text index may be corrupted on disk. Run dbcc checkdatabase and re-populate the index.
Error: 30039, Severity: 17, Data coming back to the SQL Server process from the filter daemon host is corrupted. This may be caused by a bad filter. The batch for the indexing operation will automatically be retried using a smaller batch size.
Error: 30040, Severity: 10, During a full-text crawl of table or indexed view ‘%ls’, an unregistered property, ‘%ls’, was found in batch ID %d. This property will be indexed as part of the generic content and will be unavailable for property-scoped full-text queries. Table or indexe
Error: 30041, Severity: 10, The master merge started at the end of the full crawl of table or indexed view ‘%ls’ failed with HRESULT = ‘0x%08x’. Database ID is ‘%d’, table id is %d, catalog ID: %d.
Error: 30043, Severity: 16, Stopwords of zero length cannot be added to a full-text stoplist. Specify a unique stopword that contains at least one character.
Error: 30044, Severity: 16, The user does not have permission to alter the current default stoplist ‘%.*ls’. To change the default stoplist of the database, ALTER permission is required on both new and old default stoplists.
Error: 30045, Severity: 17, Fulltext index error during compression or decompression. Full-text index may be corrupted on disk. Run dbcc checkdatabase and re-populate the index.
Error: 30046, Severity: 16, SQL Server encountered error 0x%x while communicating with full-text filter daemon host (FDHost) process. Make sure that the FDHost process is running. To re-start the FDHost process, run the sp_fulltext_service ‘restart_all_fdhosts’ command or restart th

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.

 

Leave a Reply

Your email address will not be published. Required fields are marked *