May 31, 2017 at 6:58 pm
I am unable to start then SQL agent. getting below error message when i tried start the agent
The SQL Server Agent service (DB_NN) on local machine was started and then stopped. Some services automatically stop if they are not used by any service or program
SQL version: SQL Server 2008R2 Standard Edition(RTM)
Windows:Windows server 2008 R2 enterprise
I verified below things,
currently SQL agent is running through service account. I changed to local and tried to start. But agent didn't started.
How to fix this issue?
June 1, 2017 at 6:14 am
A couple of thoughts...
1. When you changed the Service account that the SQL Agent service uses, did you do this through the SQL Server Configuration Manager, or through the normal Windows Services MMC console? You need to do this using the SQL Server Configuration manager, as that is intelligent enough to make the permissions changes etc that the service accounts require.
2. Are there any more useful error messages in the Windows event log? or even in the SQL Agent Log files? These last are in the same directory as your SQL Server event logs, and the files are named SQLAgent.out, SQLAgent.1... up to SQLAgent.9.
Thomas Rushton
blog: https://thelonedba.wordpress.com
June 1, 2017 at 7:02 pm
1)I tried to start agent service as local through configuration manager and services.msc
AGENT Log Messages:
2)SQL Server Error: 65535, SQL Server Network Interfaces: Failed to find the specified server / instance [xFFFFFFFF]. [SQLSTATE 08001]
ODBC error: 0, Logon timeout has timed out [SQLSTATE HYT00]
SQLServer error: 65535, Network-related or instance-specific error when connecting to SQL Server. The server is not found or is not accessible. Check whether the instance name is correct and whether SQL Server is configured to allow remote connections. For more information, see SQL Server Books Online. [SQLSTATE 08001]
Can not connect to server 'ABC01 \ DB_NN'; Can not Start SQLServerAgent
Note:currently Four named cluster instances are running(Fail over is not yet added). for one instance agent is up and running fine. Other instances agent service is in down.
June 2, 2017 at 11:10 am
Is SQL Browser running on each node?
Also as Thomas indicated, all changes for the accounts should be done through Configuration Manager so the permissions are managed correctly.
Sue
June 2, 2017 at 12:09 pm
Possibly a stupid question, but is the SQL Server Service running AND can you connect to that instance?
And is it configured to allow connections via TCP/IP?
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
June 3, 2017 at 6:13 pm
bmg002 - Friday, June 2, 2017 12:09 PMPossibly a stupid question, but is the SQL Server Service running AND can you connect to that instance?
And is it configured to allow connections via TCP/IP?
Heh - that's not necessarily a stupid question.
vigneshbeece, is this a new instance? Has the SQL Agent ever worked or is this a change in behavior?
June 5, 2017 at 3:22 am
This is new cluster instance installation. I am getting this error in Node A.I am unable to start SQL agent service,fail over is not yet added in Node B. Browser service is running fine.
June 5, 2017 at 3:25 am
Sue_H - Friday, June 2, 2017 11:10 AMIs SQL Browser running on each node?
Also as Thomas indicated, all changes for the accounts should be done through Configuration Manager so the permissions are managed correctly.Sue
This is new cluster installation. Browser service is running fine on Node A. Fail over is not added on Node B.
June 5, 2017 at 3:36 am
According to the error message, you've got a login failure of some description. Change the SQL Server instance so that it captures in the errorlog (at least) all failed logins, if it doesn't already. Then try to start SQL Server Agent again. Does anything appear in the errorlog? If it does, what is the error message? If it doesn't, you've got some sort of connection problem - maybe incorrectly configured protocols, or the wrong one(s).
John
June 5, 2017 at 6:02 am
John Mitchell-245523 - Monday, June 5, 2017 3:36 AMAccording to the error message, you've got a login failure of some description. Change the SQL Server instance so that it captures in the errorlog (at least) all failed logins, if it doesn't already. Then try to start SQL Server Agent again. Does anything appear in the errorlog? If it does, what is the error message? If it doesn't, you've got some sort of connection problem - maybe incorrectly configured protocols, or the wrong one(s).John
I can able to connect DB engine through SSMS. Agent service is not coming up. I already posted Error messages( "SQL Agent log" and "Error when i tried to start agent service") in this post.
June 5, 2017 at 7:12 am
vigneshbeece - Monday, June 5, 2017 6:02 AMJohn Mitchell-245523 - Monday, June 5, 2017 3:36 AMAccording to the error message, you've got a login failure of some description. Change the SQL Server instance so that it captures in the errorlog (at least) all failed logins, if it doesn't already. Then try to start SQL Server Agent again. Does anything appear in the errorlog? If it does, what is the error message? If it doesn't, you've got some sort of connection problem - maybe incorrectly configured protocols, or the wrong one(s).John
I can able to connect DB engine through SSMS. Agent service is not coming up. I already posted Error messages( "SQL Agent log" and "Error when i tried to start agent service") in this post.
You can connect, but the SQL Server Agent service cannot. So something is wrong. Let's try to find out what it is. Make sure you are capturing failed logins in your errorlog. Then see whether an attempt to start SQL Server Agent causes an error message in the errorlog (I'm talking about the errorlog, not the SQL Agent log or any other log). If it does, you've got a login failure (and it'll tell you why it failed: maybe incorrect password, maybe non-existent default database, maybe something else). If it doesn't, you've got a connection failure.
John
June 8, 2017 at 10:17 pm
This was removed by the editor as SPAM
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply