大网数据广告活动
数据库与应用安全

Troubleshoot SQL Agent Startup Failures with Error 1053

· 52CE 我爱测

Troubleshoot SQL Server Agent Error 1053. Follow step-by-step guidance to fix registry issues and restore service functionality after Windows updates.

This article provides troubleshooting guidance for an issue in which the SQL Server Agent doesn't start, and it returns Error 1053.

Symptoms

When this issue occurs, you see the following symptoms:

  • The SQL Server Agent service doesn't start after a recent Windows update is installed.
  • The Windows Event Log service doesn't start.

If the SQL Server Agent doesn't start, it returns the following error message:

Windows could not start the SQL Server Agent service on Local Computer.
Error 1053: The service did not respond to the start or control request in a timely fashion.

Cause

This issue occurs if one or more registry keys under the HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\EventLog subkey use the DWORD type instead of the correct REG_SZ (string) type.

These invalid registry keys prevent the Windows Event Log service from starting. The SQL Server Agent depends on the Windows Event Log service. Therefore, if the Windows Event Log service is unavailable, the SQL Server Agent also doesn't start, and it returns Error 1053.

Important: If the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\EventLog doesn't exist, no event log policies are configured for your system. In that case, the solution that's provided in this article doesn't apply.

Solution

  1. Verify that the SQL Server Agent didn't start. Try to start it by using any of the following methods:

  2. If the SQL Server Agent starts successfully, the problem is resolved. However, if the SQL Server Agent doesn't start, and it returns Error 1053, go to the next step.

  3. Check the SQL Agent logs, located at %ProgramFiles%\Microsoft SQL Server\<Instance>\MSSQL\Log\SQLAGENT.OUT, after you try to start the SQL Server Agent. If no new entries are added to the logs, this condition confirms that the SQL Server Agent fails before initialization. Go to the next step.

  4. Try to start the Event Log service by running the following command in an elevated Command Prompt window:

    NET START EVENTLOG
    
  5. If the Event Log service starts successfully, the problem is resolved. However, if the Event Log service doesn't start (no logs appear when you open the Event Viewer) go to the next step.

  6. Check the Event Log folder C:\Windows\System32\winevt\Logs for event log files:

    • If the folder contains .evtx log files, go to the next step.
    • If the folder doesn't contain log files, the Windows event log might be corrupted. To troubleshoot a corrupted Windows event log, see How to delete corrupt Event Viewer Log files.
  7. Use the System File Checker (SFC) to repair any corrupted system components by running the following command in an elevated Command Prompt window:

    sfc /scannow
    
  8. Create a backup of the existing registry keys before you make any registry changes. Use one of the following methods:

    • Open Registry Editor, right-click the HKLM\SOFTWARE\Policies\Microsoft\Windows\EventLog key, and then select Export.

    • In an elevated Command Prompt window, run the following command:

      reg export "HKLM\SOFTWARE\Policies\Microsoft\Windows\EventLog" "<Path_To_Store_Backup>/EventLog_Backup.reg"
      
  9. Open the Registry Editor, and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\EventLog.

  10. Under the HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\EventLog subkey and all its sub-entries:

    1. Identify and delete any registry values that are configured as a DWORD type.
    2. Re-create the deleted DWORD values by using the same name and the REG_SZ type.
  11. Delete the problematic HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\EventLog subkey by running the following command:

    reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows\EventLog" /f
    
  12. Restart your device to let Windows re-create the event log configuration by using default settings.

  13. After your device restarts, start the Windows Event Log service by running the following command:

    NET START EVENTLOG
    

    The Event Log service should now start successfully.

  14. Start the SQL Server Agent service by running the following command:

    NET START SQLSERVERAGENT
    

    The SQL Server Agent service should now start successfully.

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
See source applicability · Source date 12/05/2025
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。