Error 0x80070005 occurred during full-text index population for table or indexed view

If you read and follow my previous post about setting up Full-Text Search and then after you execute the Full Population for the Full-Text index (as follow screenshot), but nothing happen after that.

And then, when you try to execute any query with CONTAINS or FREETEXT syntax, you find no record return.

Then, open the Full-Text Indexes properties window, and you find there are some numbers in the Table Full-Text Fail Count.

In oder to see the reason of fail full-text population, go to your database log folder. Normally it is located at your <MSSQL Installed Path>\MSSQL\Log. Then, look for the log file that having prefix "SQLFT" with the latest modified date.

If you find one of the log entry is something like this:

Error '0x80070005' occurred during full-text index population for table or indexed view '[QueryPerfTest].[dbo].[Profiles]' (table or indexed view ID '12345678', database ID '1'), full-text key value '8F8C29D7-EFB0-49E9-827F-FFCBC4FCE85C'. Attempt will be made to reindex it.

Informational: Full-text retry pass of Full population completed for table or indexed view '[QueryPerfTest].[dbo].[Profiles]' (table or indexed view ID '12345678', database ID '1'). Number of retry documents processed: 213. Number of documents failed: 213.


Also, at the same log folder, open up the ERRORLOG file, and you find the log entries are like this:

Error: 7691, Severity: 16, State: 1.

Access is denied to full-text log path. Full-text logging is disabled for database 'QueryPerfTest', catalog 'ftCatalog' (database ID '1', catalog ID '10').

A new instance of the full-text filter daemon host process has been successfully started.

Error: 30089, Severity: 17, State: 1.
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.


Solution:

Ensure the service account that you use to run the SQL Server, SQL Server Agent, and SQL Full-text Filter Daemon Launcher windows service have the proper rights to perform the full-text index population and also the access to write file into the MSSQL log folder. I, myself as a developer normally would use default Local System account for all the services, therefore we would never encounter such issue. Unlike DBAs who want to have all under control including the security measurement. Sometimes the service account privilege was not setup properly. I helped someone in troubleshooting this issue and share the solution that she had found.