We recently moved our Laserfiche 11 instance to an Azure VM and are using a SQL PaaS DTU-based instance on the backend. Our users all run the Windows client. Our database is about 2.5 GB.
About a dozen times a day we're getting this error in the Laserfiche->ContentRepository event log - "[Microsoft][ODBC Driver 17 for SQL Server]TCP Provider: An existing connection was forcibly closed by the remote host." Most often (but not always) the error message indicates the function is SysEntryOpenListingEx and the SQL executed is testing for the existence of the #tmplisting table and creating if it doesn't exist.
When this happens the end-user gets a little error message box and closes it out, retries the operation, and everything is fine. So it's not the end of the world but we'd kinda like to figure out why this is happening.
Neither our Server 2019 compute instance nor our SQL instance are indicating any kind of usage limits are even close to being reached.
I also made sure we're running the latest Server 2019 updates and just updated the ODBC Driver 17 to its latest version.
Does anybody have any insight on this, or anything tips on what to try to narrow this error down?