Feedback
Did this article resolve your question/issue?

   

Article

Connect for ODBC SQL Server driver crashes the application on SQLExecute() after connection to DB is lost

Information

 
TitleConnect for ODBC SQL Server driver crashes the application on SQLExecute() after connection to DB is lost
URL NameConnect-for-ODBC-SQL-Server-driver-crashes-the-application-on-SQLExecute-after-connection-to-DB-is-lost
Article Number000185397
EnvironmentProduct: Connect/Connect64 for ODBC SQL ServerWire Protocol driver
Version: 7.1
OS: All supported platforms
Database: SQL Server
Application: All supported applications
Question/Problem Description

A crash occurs in the application when attempting to call SQLExecDirect on a broken connection.
 

Steps to Reproduce1. Login to SQLServer from example program on AIX
2. Kill the session from server side using management studio
3. Execute any query from example program
4. A crash is observed
Clarifying Information
Error Message
Defect NumberDefect 42915, Defect 39417
Enhancement Number
Cause

When driver writes to closed socket a SIGPIPE signal is generated and the driver was not handling the signal so driver crashes. The default action for unhandled SIGPIPE signal is crash.

Resolution

Fixed in hot fix 07.16.0292 (B0299, U0201)
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/20/2020 7:23 AM
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.