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

Connection error when adding node to Always On environment

· 52CE 我爱测

This article helps you resolve the problem of intermittent connection errors in SQL Server when a new node is added to the Always On environment.

You experience intermittent connection errors when you add a new node to the existing Always On environment.

Symptoms

When you try to connect to a server that's running Microsoft SQL Server, the following error message appears intermittently:

The 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.)

Cause

This error might occur if a there's a mismatch in security protocols between the database and the application servers.

Resolution

To fix this error, resolve the mismatch between the security protocols. Node1 encrypts information by using AES128/256. Node2 encrypts information by using RC4. To troubleshoot this error, follow these steps:

  1. Download IIS Crypto.

  2. Install the GUI version of the IIS Crypto tool on the server.

  3. Configure Cipher Suites.

  4. Open the IIS Crypto tool on the server.

  5. In the IIS Crypto interface, select Cipher Suites in the left panel.

  6. In the list, clear all checkboxes for ciphers that start with "TLS_DHE*".

    [!NOTE] The list might not be in any particular order.

  7. After you clear the relevant cipher selections, select Apply to save the changes.

    :::image type="content" source="media/intermittent-connection-errors-when-a-new-node-is-added/intermittent-connection-add-new-nodes.png" alt-text="Screenshot that shows clearing all ciphers that aren't required." lightbox="media/intermittent-connection-errors-when-a-new-node-is-added/intermittent-errors-when-adding-a-node-big.png":::

  8. Restart the server.

    After the changes have been applied, restart the server to make sure that the new cipher suite configuration takes effect.

[!NOTE] This troubleshooting process forces the client to communicate by using a different cipher suite that has an improved security implementation.

Always make sure that you have the appropriate backups available. Also, consider testing any changes in a controlled, staged, or test environment before you apply them to the production computers. If the issue persists or if you have any other concerns, contact your network team.

Third-party information disclaimer

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Third-party contact disclaimer

Microsoft provides third-party contact information to help you find additional information about this topic. This contact information may change without notice. Microsoft does not guarantee the accuracy of third-party contact information.

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors (upstream author metadata: prmadhes-msft). 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 04/30/2024
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

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

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