SQL Server failed to communicate with filter daemon launch service.

I am receiving this error on my production "serverSQL Server failed to communicate with filter daemon launch service  (Windows error: The service did not start due to a logon failure.
). Full-Text filter daemon process failed to start. Full-text search functionality will not be available."

I know how to add and or change the password on the login tab of the properties of the service.   But the username for this service is an NT Service account and with the Admin account, I seem not to be able to have access to change the password on this account.  So I have just three questions. (I think)

1) Why would this happen to an NT user account?
2) Can I change the password on an NT user account?
3) If I cannot change the password, would it be possible to just use a domain user account, like the rest of the SQL services are using or do I have to use the NT account for this Service?


Richard ComitoDirector of ITAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.


First thing you need to verify if he SQL Full-text Filter Daemon Launcher service is disabled. In case it is then set it to manual, restart SQL server and use FTS so:

Set the 'SQL Full-text Filter Daemon Launcher' service to Manual.

Next you should restart SQL Server. Once SQL Server is started, you should see that the 'SQL Full-text Filter Daemon Launcher' has been started.

Then try to use  FTS on the database.

Richard ComitoDirector of ITAuthor Commented:
dfke thank you for your reply.  it is set to manual.

What I am trying to figure out is if I have to use the NT account or if I can use my own account be it a domain or a local user account.  just like what I have on all the other SQL services on the same server.  This is the only SQL service on that server that is trying to use the NT user.

Richard ComitoDirector of ITAuthor Commented:
I believe I have found the answer.


So it looks like I can change user to a domain user.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.