February 18, 2013 at 4:16 pm
Last week I installed a new SQL 2008 R2 server. Got Agent configured and all was working. Today I ran the upgrade wizard against a database I will be migrating and discovered that it needed Full Text Search which I had not installed. After I installed Full Text Search, the agent stopped working and neither the agent nor the full text search service will start.
I can get the Agent to start if I add my service account into the Local administrators group. (I use the same domain account for the SQL Server Service as well.) So I suspect some file permission that it needs got removed when I added the Full Text Search option.
The full text search service is set to use LocalService account. It won't start regardless of whether the agent starts or not.
Short of Uninstalling SQL and Reinstalling, does someone know how I can resolve this?
February 18, 2013 at 7:35 pm
Need some more details, have you checked windows events, sql server logs? it could well be a coincidence as i feel full text indexing cannot be hampering path of the sql agent's start.
February 18, 2013 at 10:34 pm
Superdoc (2/18/2013)
Need some more details, have you checked windows events, sql server logs? it could well be a coincidence as i feel full text indexing cannot be hampering path of the sql agent's start.
Yes more detail on your environment. What OS? SP levels? Clustered/Non-Clustered? Named or default instance? Multiple instances on same server?
I agree and check the event logs there should be an error on the system/security event log for sql agent if authentication failed or service failed.
---------------------------------------------------------------
Mike Hahn - MCSomething someday:-)
Right way to ask for help!!
http://www.sqlservercentral.com/articles/Best+Practices/61537/
I post so I can see my avatar :hehe:
I want a personal webpage 😎
I want to win the lotto 😀
I want a gf like Tiffa :w00t: Oh wait I'm married!:-D
February 19, 2013 at 8:17 am
Windows Server 2008 R2 Standard, SP1, (64 bit OS)
SQL 2008 R2 (64-bit) (10.50.1600.1)
Default Instance
After I installed Full Text Search, it stopped and restarted the SQL services. I see the following errors:
Log: System
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.
Log: Application
Source: MSSQLSERVER
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.
February 19, 2013 at 4:28 pm
:-)I suspect the resolution was a combination of permissions I added. Prior to my initial posting I did try adding the Local Policy permissions and the SysAdmin Role to my service account.
I then tried a repair on the SQL Install and that did fix the Full Text Search Service but it did not fix the Agent Service. I did discover though that I could get the service going if I added the service account to either the local admins or the SQLServerMSSQLUser$... group. So that got me searching for where I had permissions for that group.
One thing that was missing for certain was permissions to the SQLAgent Logs. Prior to the install where I added Full Text Search the log files have the service account listed with full permissions. After the install this user was missing from the permissions list. Restoring that by itself did not remedy the problem. I also had to apply a registry hack mentioned in this post: http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/cb84d893-2989-48e5-bdae-ade9b1a7fd2d/
There were some other file permissions I gave the account in the Data & Backup folders. (Service account did not have permissions to the tempdb or any of the bak or trn files. I'm not sure if these were needed.
It is possible that the SQL 2008 SP1 may resolve it. I saw that mentioned in one of the posts I found.
My symptoms were very similar to what is in this post: http://connect.microsoft.com/SQLServer/feedback/details/624656/sql-agent-starts-then-stop-after-sql-2008-installation
The errors this user was seeing in the logs and when he tried to start the agent manually were exactly what I was seeing. Hope this post helps someone else.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply