June 27, 2012 at 8:28 am
I am getting a lot of "log in" errors in our SQL Server Error log for one of the instances on our Active\Active cluster. It says that there is a problem logging into a database with a Domain service account we are using to start the SQL Server Agent. This database was recently deleted. I do not see it referenced in any of our maintenance plans. I tried to restart the SQL Server Agent from SQL Server Configuration Manager. The service stoppped.... but threw an error message when it tried to restart... it said it could nto start because it was taking too long. If I go into SSMS and right click on the SQL Server Agent... I am able to restart the service. I am able to log onto our system with the Domain Service Account... so I know the password is correct. Any suggestions would be greatly appreciated.
Charlie
June 28, 2012 at 12:23 am
Try this:
1) Looks like the default database of the logins is deleted. Changed the default database to some other database.
2) Use Failover Cluster Manager to bring the SQL Agent resource online. Don't use SQL Server Configuration Manager.
June 28, 2012 at 4:56 am
Thanks for the reply Suresh. We are running SQL Server 2008 R2 Standard Edition. From what I read on the internet, Failover Cluster Manager comes with the Enterprise edition. So we do not have that option on our Cluster.
June 28, 2012 at 5:39 am
Can you start the service from Cluster Administrator? From Services? If you can start it from the latter but not the former, that suggests that the problem is something cluster-related. Does the account that runs the clustering service have access to SQL Server so that it can perform the IsAlive check?
John
June 28, 2012 at 5:51 am
Hi John... By start from Cluster Manager... Do you mean take it offline and bring it back onlline? I do not see a way to restart from the Cluster Administrator other than that.
Thanks,
Charlie
June 28, 2012 at 6:02 am
Charlie
That's right. Either that or fail over the whole group to another node.
John
June 28, 2012 at 6:04 am
I am able to start the agent from Cluster Admin.... but not Services....
June 28, 2012 at 6:10 am
Have you looked at the SQLAgent.OUT file? Is there anything in the event log?
John
June 28, 2012 at 6:22 am
In the SQLAgent.OUT file there are a number of entries:
2012-06-28 08:12:00 - ! [298] SQLServer Error: 18456, Login failed for user 'TOWSNU\SQL2005Service'. [SQLSTATE 28000]
2012-06-28 08:12:00 - ! [298] SQLServer Error: 4060, Cannot open database "SharedServices1_DB" requested by the login. The login failed. [SQLSTATE 42000]
Which is very irritating being as this database does not even exist. It was a Sharepoint DB from the old version. I checked all my maintenance plans and do not see any references that would still be trying to access this database. I told the System Architect that we needed separate Service Accounts for all agents, but he insisted on using one for all. Makes it hard to troubleshoot. Thanks again for your time in replying to this!
Charlie
June 28, 2012 at 6:35 am
As Suresh suggested, check the default database for the service account. If it's anything other than master, change it to master.
John
July 15, 2012 at 5:15 am
Found exactly the same on mine.
It wasn't a maintenance plan but rather a job under the SQL agent set to run every minute.
Again it was related to a Sharepoint installation which had been removed.
Deleted the job - all sorted.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply