But in the end, there was indeed an issue. Good code should have such mechanisms implemented. Now actually retrying the connection in the code could work around this. (provider: SSL Provider, error: 0 – An existing connection was forcibly closed by the remote host.) -> 32Exception: 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 login process. > : The execution of the InstancePersistenceCommand named CreateWorkflowOwner was interrupted by an error. : The InstanceStore could not be initialized.
Normally everything went fine but one in every 250 to 500 connection of the server-client to a database on SQL Server 2016 they got the error below. They suffered from intermittent TLS issues with Windows Server 2012 R2 connecting to SQL Server 2016 running on Windows Server 2016 or 2019. Someone asked me to help investigate an issue that was hindering client/server applications.
0 kommentar(er)
