Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies to: 
SQL Server
Azure SQL Database
This article describes how to set or change the service account for the SQL Full-text Filter Daemon Launcher service (MSSQLFDLauncher) by using SQL Server Configuration Manager. The default service account used by SQL Server setup is NT Service\MSSQLFDLauncher.
About the SQL Full-text Filter Daemon Launcher service
The SQL Full-text Filter Daemon Launcher service is used by SQL Server Full-Text Search to start the filter daemon host process, which handles full-text search filtering and word breaking. The Launcher service must be running to use full-text search.
The SQL Full-text Filter Daemon Launcher service is an instance-aware service that is associated with a specific instance of SQL Server. The SQL Full-text Filter Daemon Launcher service propagates the service account information to each filter daemon host process that it launches.
Set the service account
On the Start menu, point to All Programs, expand Microsoft SQL Server, and then select SQL Server nnnn Configuration Manager, where nnnn is the version you have installed.
In SQL Server Configuration Manager, select SQL Server Services, right-click SQL Full-text Filter Daemon Launcher (instance name), and then select Properties.
Select the Log On tab of the dialog box, and then select or enter the account under which to run the processes that the SQL Full-text Filter Daemon Launcher service starts.
After you close the dialog box, select Restart to restart the SQL Full-text Filter Daemon Launcher service.
Troubleshoot the SQL Full-text Filter Daemon Launcher service if it doesn't start
If the SQL Full-text Filter Daemon Launcher service doesn't start, review the following possible causes:
Permissions issues
The SQL Server service group doesn't have permission to start SQL Full-text Filter Daemon Launcher service.
Make sure the SQL Server service group has permissions to the SQL Full-text Filter Daemon Launcher service account. During the installation of SQL Server, the SQL Server service group is granted default permission to manage, query, and start the SQL Full-text Filter Daemon Launcher service. If SQL Server service group permissions to the SQL Full-text Filter Daemon Launcher service account have been removed after SQL Server installation, the SQL Full-text Filter Daemon Launcher service doesn't start, and full-text search is disabled.
The account used to connect to the service doesn't have privileges.
You might be using an account that doesn't have login privileges on the computer where the server instance is installed. Verify that you're logging in with an account that has User rights and permissions on the local computer.
Service account and password issues
The user account or password of the service account is incorrect.
In SQL Server Configuration Manager, make sure the service is using the correct service account and password.
The password associated with the SQL Full-text Filter Daemon Launcher service account has expired.
If you use a local user account for the SQL Full-text Filter Daemon Launcher service and the password expires, you have to:
Set a new Windows password for the account.
In SQL Server Configuration Manager, update the SQL Full-text Filter Daemon Launcher service to use the new password.
Named pipes configuration issues
The SQL Full-text Filter Daemon Launcher service isn't configured correctly.
If named pipes functionality has been disabled on the local computer, or if SQL Server has been configured to use a named pipe other than the default named pipe, the SQL Full-text Filter Daemon Launcher service might not start.
Another instance of the same named pipe is already running.
The SQL Server service acts as a named pipe server for the SQL Full-text Filter Daemon Launcher service client. If the named pipe was already created by another process before SQL Server starts, an error is logged in the SQL Server error log and the Windows Event Log, and full-text search isn't available. Determine what process or application is attempting to use the same named pipe and stop the application.