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.)
Same issue. The lack of response from Laserfiche tells me I should submit a support ticket to them. I'll monitor this thread in case we hear back from Laserfiche.
Thanks
Looks like this is an issue affecting other applications as well:
Fix is to:
You can work around this by adding ";Trust Server Certificate=true" to the end of the server name in the connection dialog.
EDIT: we are actually going to try this first, it seems we do not have TLS enabled for some reason:
https://support.laserfiche.com/kb/1013919/configuration-information-for-tls-1-2
*EDIT: Enabling TLS resolved our issue.
Getting the same error periodicaly. WF 10.4.1.
We've been having the same with one of our workflows. It intermittently happens with the remote SQL connection. I'm using ODBC Driver 13 for SQL Server. I'm thinking about trying 13.1 to see if that helps. Has anyone else had any luck troubleshooting this?
i''m also getting this same error in insert into SQL database. has anyone had any luck troubleshooting or work around?
Where are you getting this error exactly? Is it in an activity?
its coming from WF initiated from LF where it Insert or update a SQL Database
@MirunaBabatie
multiple folks having this issue with error on insert into SQL Db. any update?
Not really sure what resolve this issue for us. But system did update our SQL server to have more processing power and more RAM.
I am getting the same error since upgrading from SQL express to SQL std. Has anyone had any luck resolving this?
Getting the same error, hoping for some assistance. The error is not with the Database, it's the way workflow is processing the connections to SQL.
We're getting this error as well. Has anybody found a resolution for this?
Still happening
My Band-Aid was to wrap the sql update activity in a try-catch with a 5 second delay before retrying the sql statement.
We have now started seeing this as well with a large client. The change they made on their side that caused it to start was changing their security configuration on the SQL server to force TLS 1.2 only. The odd part is that workflow successfully connects probably 9 out of every 10 times using TLS 1.2 (verified with wireshark) successfully.
When it fails, it gives the error "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.)"
Has anyone found a fix? We though about changing the security settings and forcing TLS 1.2 only on the servers, however that creates a domino effect for everything that connects to the servers and would require a lot of downtime.
@████████ How did you set a delay only for a few seconds? I only see the option to do 1 minute delay at minimum which is far too long.
I didn’t, in the first case we had to have a scheduled starting rule instead of condition
I have the exact same issue. DocuNav, our Laserfiche contractor, has no solution. Can Laserfiche support assist?