Here’s what more than 2,500 business decision-makers around the world say.Download the report
...with the Facility Hero app in hand! Discover how you can optimize your maintenance efforts today.Learn more
Access tailored services, 24/7 self-service and expert help. Anywhere, anytime, any project.Discover now
Everything you need to know about our IoT technology backbone.Learn more
Welcome to the Schneider Electric Global Website×
Unable to start SQL Server Agent. Produces the following error when trying to start it from the services control panel.
"The SQL Server Agent (MSSQLSERVER) service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service."
Struxureware Power Monitoring
Power Monitoring Expert
SQL Server 2005, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014
There was no such directory present on the machine and also the SQLAgent.out log file did not exist.
*Warning: This article contains information about editing the registry. Improper changes to the registry can permanently damage the operating system. Always backup the registry before making any changes.*
Manually try to start SQL Server Agent from a command prompt using the following command:
SQLAGENT90 -C -V>C:\SQLAGENT.OUT
Check the contents of the SQLAgent.out file produced by this command.
Should contain an message as per below:
Unable to rename C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLAGENT.OUT to C:\ProgramFiles\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLAGENT.1
(reason: The system cannot find the path specified)
2014-08-24 10:10:31 - !  Startup error: Unable to initialize error reporting system (reason: The system cannot find the path specified)
2014-08-24 10:10:31 - ?  SQLServerAgent terminated (normally)
Check the value of key ErrorLogFile in the following registry key.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\SQLServerAgent
Change the value in the ErrorLogFile key to reflect the correct location of the SQL log folder.
After making the change and saving, restart the SQL Server Agent from the services control panel.