March 18, 2019 at 8:53 am
Got this error message on a Sunday at 3:13 PM. Environment is SQL Server 2016 SP1 Standard Edition, Windows Server 2012 R2 Standard. While there's activity on the server, usage should be down about 50%. Googling this does not provide much unless you are using SQL Server 2008 R2.
Full message: "The fulltext filter daemon host (FDHost) process has stopped abnormally. This can occur if an incorrectly configured or malfunctioning linguistic component, such as a wordbreaker, stemmer or filter has caused an irrecoverable error during full-text indexing or query processing. The process will be restarted automatically." Actual error code: "Error: 30089, Severity: 17, State: 1."
Any comments / URLs would be appreciated - thank you.
March 22, 2019 at 2:55 pm
bobba - Monday, March 18, 2019 8:53 AMGot this error message on a Sunday at 3:13 PM. Environment is SQL Server 2016 SP1 Standard Edition, Windows Server 2012 R2 Standard. While there's activity on the server, usage should be down about 50%. Googling this does not provide much unless you are using SQL Server 2008 R2.Full message: "The fulltext filter daemon host (FDHost) process has stopped abnormally. This can occur if an incorrectly configured or malfunctioning linguistic component, such as a wordbreaker, stemmer or filter has caused an irrecoverable error during full-text indexing or query processing. The process will be restarted automatically." Actual error code: "Error: 30089, Severity: 17, State: 1."
Any comments / URLs would be appreciated - thank you.
If that's the only error and you can't find any other issues related to fulltext then it's not too easy to figure out the issue. It's poorly documented - other than the issue you probably found with inbound shared memory and SQL Server 2008 which hasn't really been much of a problem since.
Is the daemon currently running or has it had any of the same errors?
Does it restart successfully if you execute: sp_fulltext_service 'restart_all_fdhosts'
That would get logged in the SQL Server error log.
Some of the "known" issues would have some other errors - things such as timeouts, permission issues after changing the service account. Or it doesn't start when you try the restart. If it's related to restricted growth, you should be able to capture that error by executing: select FULLTEXTCATALOGPROPERTY ('catalog_name' ,'IndexSize')
That's one of the few issues documented and it's buried in the remarks section of this documentation:
FULLTEXTCATALOGPROPERTY (Transact-SQL)
Dropping and rebuilding the catalog may be an option depending on the size and resources needed.
Sue
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply