SQL Agent not automatically restarting on a server with two instances.

Question

SQL Agent not automatically restarting on a server with two instances.

Guras

SSCertifiable

Points: 6518
More actions
April 19, 2018 at 12:20 pm

#410445

I have the SQL Service on Automatic restart on a machine and the agent is restarted only on instance A but not on instance B .

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

sgmunson SSC Guru Points: 110640 More actions · Answer 1

Guras - Thursday, April 19, 2018 12:20 PM
I have the SQL Service on Automatic restart on a machine and the agent is restarted only on instance A but not on instance B .

I suspect that the SQL Agent Service is a component that is shared across instances on the same server, but I haven't been able to find any supporting documentation. The closest I could find was this: https://docs.microsoft.com/en-us/sql/sql-server/install/work-with-multiple-versions-and-instances-of-sql-server?view=sql-server-2017

And that just provides the categories of things that might be shared and what they might be shared across, and surprisingly, SQL Agent Service isn't mentioned in any of the categories...

Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)

SQLPirate SSCrazy Points: 2880 More actions · Answer 2

Guras - Thursday, April 19, 2018 12:20 PM
I have the SQL Service on Automatic restart on a machine and the agent is restarted only on instance A but not on instance B .

This may seem like a dumb question, but did you verify that SQL Server Agent service (not SQL Service) is set to Automatic Restart for both instances? Also, what version of SQL are you running?

Sue_H SSC Guru Points: 90860 More actions · Answer 3

After verifying all the settings, I've seen this happen at times and I think it's been due to SQL Agent trying to start up before SQL Server is ready for connections. One thing to try is to set the service start up to Automatic(Delayed Start). You would need to do that in the Services applet.

Sue

Guras SSCertifiable Points: 6518 More actions · Answer 4

Sue_H - Thursday, April 19, 2018 1:56 PM
After verifying all the settings, I've seen this happen at times and I think it's been due to SQL Agent trying to start up before SQL Server is ready for connections. One thing to try is to set the service start up to Automatic(Delayed Start). You would need to do that in the Services applet.
Sue

That was it.. Thank you !