SQL Server Agent would not start (2008 R2)

The fix ended up being to open up SSMS, right-click on SQL Server Agent, go to Properties.  Then on the Connections tab, write in the name of the virtual SQL Server.

It may be that the Cluster Manager is the proper way to start the Agent.  But due to the weird way the customer set up my access, I didn’t have access to Cluster Manager.


Other errors:

Agent named pipes provider could not open a connection to sql server

sqlserveragent could not be started local

This entry was posted in Uncategorized. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s