Windows Server 2008 R2 Standard, SP1, (64 bit OS)
SQL 2008 R2 (64-bit) (10.50.1600.1)
After I installed Full Text Search, it stopped and restarted the SQL services. I see the following errors:
Source: Service Control Manager
Event ID: 7000
Date: 2/18/2013 3:31:05 PM
The SQL Full-text Filter Daemon Launcher (MSSQLSERVER) service failed to start due to the following error:
Access is denied.
Event ID: 17187
Date: 2/18/2013 3:31:06 PM
SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again.
In the SQL Log at 3:31:05 there is an Error 9954, Severity:16, State:1. (source is spid13s) The next line (same time stamp) reads "SQL Server failed to communicate with filter daemon launch service (Windows error: Access is denied.). Full-Text filter daemon process failed to start. Full-text search functionality will not be available.
At 3:31:06 there is a Logon Error 17187, Severity 16, State 1. The next line has "SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the information message that indicates that SQL Server is ready before trying to connect again."
Those 2 lines repeat (same time stamp) then the next line states "The SQL Server Network Interface library could not register the Service Prigincipal Name (SPN) for the SQL Server service. Error: 0x2098, state 15. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an information message. Further action is only required if Kerberos authentication is required by authentication policies.
At this point I go into Configuration Manager and notice that the Agent Service is down and try to start it. I get another Event 7000 "The SQL Server Agent (MSSQLSERVER) service failed to start due to the following error: Access is denied." when I try to start it. The details tab does not provide any useful additional information. The only way I have found to make it start is by adding the service account into the local administrators group on the server.
I have also tried making that account a member of the sysadmin role, and have gone into Local Security Policies and added it to the following policies.
Adjust memory quotas for a process
Bypass traverse checking
Replace a process level token
It already had the Log on as a service policy.
Right now I'm not seeing any alternative but to uninstall and reinstall SQL again. Full Text won't start even though I have gotten the Agent to start if using an Administrator account for the service. And it won't let me uninstall Full Text Search either.
Right now the only DB's on it are the VMWare vCenter and vManager databases. I'll have to reattach the DB's and recreate my jobs but at this point, it won't be that much work to reinstall. I just thought maybe someone else had seen this before and had a resolution.