|Applies To||RSA Product Set: Archer|
|Issue||Jobs Losing Schedules|
All Jobs that could have a schedule are affected.
Any job that has lost its schedule can have a new scheduled job that is created by saving the job again.
|Resolution||To resolve this issue,|
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.)
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
The exact error text may vary slightly in your environment.
If this behavior is noted, review the following Microsoft article entitled Applications experience "forcibly closed" TLS connection errors when connecting SQL Servers in Windows.
Using Group Policy
TLS_DHE_* ciphers can be disabled by using Group Policy. See Prioritizing Schannel Cipher Suites to configure the SSL Cipher Suite Order group policy.
Policy URL: Computer Configuration > Administrative Templates > Network > SSL Configuration Settings.
Policy Setting: SSL Cipher Suite Order setting.
It is necessary to restart the computer after modifying this setting for the changes to take effect.
Windows versions that contain the leading zero fixes for TLS_DHE: