SQLServerAgent could not be started (reason: Unable to connect to server ‘(local)’; SQLServerAgent cannot start)

SQLServerAgent could not be started (reason: Unable to connect to server ‘(local)’; SQLServerAgent cannot start)

SQLServerAgent could not be started (reason: Unable to connect to server ‘(local)’; SQLServerAgent cannot start)

If you are trying to start SQL Server Agent and you get the error message SQLServerAgent could not be started (reason: Unable to connect to server ‘(local)’; SQLServerAgent cannot start) then read below, in order to see what you can try for resolving the issue.

 

How to Resolve the Issue

Go to computer management – local users and groups, and add the service account with which you want SQL Server Agent service to start in the below Windows group:
SQLServerSQLAgentUser$[ComputerName]$[InstanceName]

Then, make sure that the service account meets the requirements described on the following MSDN Article.

One of the requirements is that the SQL Server Agent service account is SysAdmin on the SQL Server instance.

So, among the rest of the requirements, make sure that the local Windows Group “SQLServerSQLAgentUser$[ComputerName]$[InstanceName]” has SysAdmin access on the SQL Server instance (important note: never add any irrelevant users to this group – just the service account that start SQL Server agent service).

The last step is to go to SQL Server Configuration Manager, enter SQL Server Agent properties and make sure that the service account that starts the service is the one for which you followed the above steps.

Note: In order to avoid such issues in the future, make sure that during the installation of SQL Server you specify the proper service accounts. This way, SQL Server’s installation process will automatically grant the necessary permissions and arrange the required group memberships for the specified service accounts. 

 

If the Above did not Resolve the Issue

If the above did not resolve the issue, there are some additional steps that might help with your troubleshooting process. To this end, you can try reading the SQL Server error log, in order to find additional information about the error. You can easily find the location of SQL Server’s log file by running the below T-SQL query from SQL Server Management Studio:

USE master
GO
xp_readerrorlog 0, 1, N'Logging SQL Server messages in file', NULL, NULL, N'asc' 
GO

Alternatively, you can check the Application Log in Windows Event Viewer on the database server.

 

Did you find this article useful and interesting? Feel free to leave your comment!

If you enjoy my SQL Server administration tips and articles, I have something special just for you. It is one of my eBooksand it is called “Administering SQL Server“. Check it out!

Subscribe to our newsletterand stay up to date with our latest articles on SQL Server and related technologies!

Check out our latest software releases! All our software tools have Community Editions which are free to download.

 

Rate this article: 1 Star2 Stars3 Stars4 Stars5 Stars (1 votes, average: 5.00 out of 5)

Loading...

Reference: SQLNetHub.com (https://www.sqlnethub.com)

© SQLNetHub

 

Troubleshooting: SQLServerAgent could not be started (reason: Unable to connect to server '(local)'; SQLServerAgent cannot start) Click to Tweet
Artemakis Artemiou
Artemakis Artemiou is a Senior SQL Server and Software Architect, Author, and a 9 Times Microsoft Data Platform MVP (2009-2018). He has over 15 years of experience in the IT industry in various roles. Artemakis is the founder of SQLNetHub and TechHowTos.com. Artemakis is the creator of the well-known software tools Snippets Generator and DBA Security Advisor. Also, he is the author of many eBooks on SQL Server. Artemakis currently serves as the President of the Cyprus .NET User Group (CDNUG) and the International .NET Association Country Leader for Cyprus (INETA). Artemakis's official website can be found at aartemiou.com.