We have an application in a WS 2016 connecting to a SQL 2016 Server through ODBC Driver 11 for SQL Server version 2014.120.5543.11. We are experiencing intermittent errors that are disrupting production.
Message example 1:
Database Exception in CHtmlPage_Process::OpenPage() with tag OpenEx
The connection is broken and recovery is not possible. The client driver attempted to recover the connection one or more times and all attempts failed. Increase the value of ConnectRetryCount to increase the number of recovery attempts.
Communication link failure.
Message example 2:
Database Exception in ExecuteSQL for 'SET XACT_ABORT OFF'. Error: The connection is broken and recovery is not possible. The client driver attempted to recover the connection one or more times and all attempts failed. Increase the value of ConnectRetryCount to increase the number of recovery attempts.Communication link failure
We have tried ODBC SQL Server Native Client 11.0 version 2011.110.6518.00 as well. The same error occurs.
Both drivers are set to Pool connections with a Timeout of 60.
The programmers assure me they are using proper transaction control procedures.
In this same environment the JDBC and IIS connections are remaining open in a sleeping status. Sometimes over 150.
We are stumped and need some Microsoft technical guidance on settings to change or whether or not there is a known defect with the Drivers, SQL Server 2016, or WS 2016.
We appreciate your help.