Feedback
Did this article resolve your question/issue?

   

Article

Application crash occurs if QueryTimeout is used when using a SQL Server mirrored database and the network is disabled with the ODBC SQL Server Wire Protocol driver

Information

 
TitleApplication crash occurs if QueryTimeout is used when using a SQL Server mirrored database and the network is disabled with the ODBC SQL Server Wire Protocol driver
URL NameApplication-crash-occurs-if-QueryTimeout-is-used-when-using-a-SQL-Server-mirrored-database-and-the-network-is-disabled-with-the-ODBC-SQL-Server-Wire-Protocol-driver
Article Number000186422
EnvironmentProduct: Connect for ODBC SQL Server Wire Protocol driver
Version: 07.01.0145 (B0147, U0095)
OS: All supported platforms
Database: SQL Server 2008 mirrored database
Application: All applications
Question/Problem Description
Connecting to the primary of a SQL Server mirrored database, when the network is disabled on the primary, there is a hang when using the Connect for ODBC 7.0 SQL Server Wire Protocol driver.  If the "QueryTimeout" connection option is set to cause the query to return sooner, the application crashes. 
Steps to Reproduce
Clarifying Information
A memory access violation occurs with the connection options "FailoverMode=2", "QueryTimeout=5", "EnableCancelTimout=1" and then a query times out.
Error MessageProgram received signal SIGSEGV, Segmentation fault.
Defect NumberDefect PSC00336913
Enhancement Number
Cause
The memory access violation occurred due to the driver not handling the replay of the statements when the failover occurred successfully.
Resolution
Fixed in hot fix 07.01.0147 (B0148, U0095).

Refer to Connect and Connect64 for ODBC hot fix download and install instructions for instructions on how to download and install the hot fix.
Workaround
Notes
Last Modified Date11/6/2015 4:25 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.