When I'm trying to start SQL Server Agent, I got this error:

TITLE: Microsoft SQL Server Management Studio
Unable to start service SQLAGENT$SQL_NAGA on server NAGA. (mscorlib)
The SQLAGENT$SQL_NAGA service on NAGA started and then stopped. (ObjectExplorer)

Can you guys help me to solve this problem? I'm using 2014 Enterprise Edition.

Using @@version I got this:

Microsoft SQL Server 2014 - 12.0.4213.0 (X64) 
Jun  9 2015 12:06:16 
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.3 <X64> (Build 10586: )

I also found this error event related to SQL Server Agent in the Windows Event Log

Log Name:      Application
Source:        SQLAgent$SQL_NAGA
Date:          1/31/2016 6:17:24 PM
Event ID:      103
Task Category: Service Control
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Naga
SQLServerAgent could not be started
(reason: Unable to connect to server 'NAGA\SQL_NAGA'; SQLServerAgent cannot start).


Error log of SQL Server Agent

enter image description here

SQL Server and SQL Server Agent both logged on as Local System Account

enter image description here


5 Answers 5


This error would be where I would start looking:

SQLServer Error: 27, Registry information is corrupt or missing.
Make sure the provider installed and registered correctly. [SQLSTATE 08001]

If you are able to perform a repair of the installation, that should resolve this.


Set the SQL Agent service to Automatic(Delayed). The first thing it will do is try to connect to SQL Server, and if SQL Server hasn't finished starting yet, SQL Agent can fail. Delaying the start for SQL Agent will give SQL Server the chance to finish.

  • I set the SQL Agent Service to Automatic(Delayed) and restarted the SQL server service. But still Agent Service won't start. Getting the error "Service started and then stopped"
    – Naga
    Commented Feb 1, 2016 at 19:20

ODBC driver error can cause problems on systems with multiple versions or upgrade scenarios. Take a look at these articles. This can generate network related errors. https://support.microsoft.com/en-nz/kb/3185365 and https://support.microsoft.com/en-us/kb/955763 The solution is to update to the latest ODBC driver.

  • +1 However in our case (updating OBDC drivers for SQL2019), the latest version did not work. Instead we had to go for a single version increase which worked perfectly.
    – EvilDr
    Commented Mar 1 at 11:01

Check if the service is running. If not you can start the service using one of these alternatives:

  • services.msc
  • net start SQLSERVERAGENT
  • Using SQL Server Configuration Manager
  • Windows service manager start SQL Agent service (automatic)

If the service is running, you can try this:

-- Start SQL Server Agent when ‘Agent XPs disabled’
EXEC sp_configure 'show advanced options', 1
EXEC sp_configure 'Agent XPs', 1

Make sure the SQL Agent service user (the one in services.msc) is a valid login on the SQL Server instance.

If it is, look for 18456 errors in the SQL log to see why that login can't log in.

Specific details in the MSDN Select an Account for the SQL Server Agent Service article


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.