April 4, 2011 at 10:00 am
Hello,
I restarted my machine yesterday and sql agent didn't start eventhough it is set to start automatically. It runs under windows authentication.
Error in Windows Application log says:
Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database.
SQLServerAgent could not be started (reason: Unable to connect to server 'BATCHSERVER'; SQLServerAgent cannot start).
Can anyone please help?
April 4, 2011 at 12:18 pm
Do you have a database called "BatchServer" or is that an Instance name or a server name?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
April 4, 2011 at 12:21 pm
BatchServer is the server instance name...
April 4, 2011 at 12:30 pm
Default database for NT AUTHORITY\SYSTEM login is master database.
April 4, 2011 at 12:34 pm
Were you able to start the service a bit later?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
April 4, 2011 at 12:35 pm
It sounds like someone might have messed with permissions on the server. If you set to LocalSystem as a test, does that work?
April 4, 2011 at 12:38 pm
yes, I started the service manually a day later and was able to do it without any problem... I don't think anyone else has access to the server to do any changes... We do have a third party tool for backup, can that be using this service?
April 4, 2011 at 12:42 pm
apat (4/4/2011)
yes, I started the service manually a day later and was able to do it without any problem... I don't think anyone else has access to the server to do any changes... We do have a third party tool for backup, can that be using this service?
I think you would have been fine starting the service just 10 minutes later. It sounds like the SQL Service was not done starting when the agent service tried starting. Agent service has a pre-requisite of the SQL Service being started. I would add a dependency to your agent startup so that it doesn't start until after the SQL Service starts.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
April 4, 2011 at 12:49 pm
well looks like sql server service was already started. it recovered master database, finished checkdb and also recovered other user databases during this process...
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply