Edit

Share via

SQL Server Agent fails to start while connecting to SQL Server

  • Article

This article helps you resolve a problem in which you can't start the Microsoft SQL Server Agent.

Symptoms

You might receive the following error messages:

SQL Server does not accept the connection (error: 233). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.

A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - An existing connection was forcibly closed by the remote host.) (Microsoft SQL Server, Error: 10054)

Additionally, the event viewer logs event ID 17052.

Cause

The DisabledByDefault and Enabled registry entries in the [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client] subkey might be configured incorrectly. For more information, see TLS 1.2 support for Microsoft SQL Server.

Resolution

To resolve these problems, follow these steps:

  1. Enable the Transport Layer Security (TLS) 1.2 protocol for SQL Server communication by updating the following registry entries:

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2]

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client] "DisabledByDefault"=dword:00000000 "Enabled"=dword:00000001

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server] "DisabledByDefault"=dword:00000000 "Enabled"=dword:00000001

  2. Open Regedit.exe.

  3. Navigate to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client].

  4. Set the DisabledByDefault value to 0 and Enabled to 1 for both the client and server.

See also

An existing connection was forcibly closed by the remote host (OS error 10054)