The SQL Server Agent Service does not start and it
generates error 1053:
An error 1053 (The service did not
respond to the start or control request in a timely fashion.) occurred while
performing this service operation on the SQLServerAgent service.
This issue occurs because of one of the following reasons:
- The SQLServerAgent service startup account may not have the
correct permissions on the folder that contains SQLAgent.out files.
- The SQL Server Agent error log may include a path or a file
name that is not correct.
- Some executable .dll files may be corrupted or
damaged.
- The SQLServerAgent service startup account may not have the
correct permissions to use the registry.
To resolve this issue, use one of the following methods, as
appropriate to your circumstances:
- The SQLServerAgent service startup account may not have the
correct permissions on the folder that contains SQLAgent.out files.
In this case, make sure that the specified SQLServerAgent service account has
full control permissions to the folder in which the SQLAgent.out, SQLAgent.1,
SQLAgent.2, and other SQL Server files are located. These files are typically
stored in the LOG folder, which is in the SQL Server installation
path. - The SQL Server Agent error log may include a path or a file
name that is not correct.
In this case, verify that the path and file
name for SQLAgent.out is valid:
- In SQL Server Enterprise Manager, expand the Management
folder.
- Right-click SQL Server Agent, and then click Properties.
- Under Error Log, make sure that the path that is specified next to File Name is valid.
- Make sure that the file name is
SQLAGENT.out.
- Some executable .dll files may be corrupted or
damaged.
In this case, try starting SQL Server Agent from the command
prompt by running the following command:
Default InstanceNamed Instancesqlagent -i[Instance Name] -c -v
If you receive the following error message
execution can't continue as the language resource file sqlagent.rll could not
be loaded
replace the SQLAgent.dll and SQLAgent.rll files with
different copies of these files (SQLAgent.dll and SQLAgent.rll). - The SQLServerAgent service startup account may not have the
correct permissions to use the registry.
In this case, make sure that
the MSSQLSERVER startup account, the SQL Server Agent startup account, and the Microsoft Distributed Transaction
Coordinator (MS DTC) startup account have full control of the following keys
in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDTC
The following keys are for
the default instance:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLSERVER
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlset\Services\SQLSERVERAGENT
The following keys are for
the named instance:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQL$<INSTANCE>
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlset\Services\SQLAgent$<INSTANCE>
Note The placeholder INSTANCE is replaced with
the actual name of an instance of SQL Server.