Connect for ODBC SQL Server driver crashes the application on SQLExecute() after connection to DB is lost
Information |
Title | Connect for ODBC SQL Server driver crashes the application on SQLExecute() after connection to DB is lost |
---|
URL Name | Connect-for-ODBC-SQL-Server-driver-crashes-the-application-on-SQLExecute-after-connection-to-DB-is-lost |
---|
Article Number | 000185397 |
---|
Environment | Product: 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 |
|
---|
Steps to Reproduce | 1. 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 Number | Defect 42915, Defect 39417 |
---|
Enhancement Number |
---|
Cause |
|
---|
Resolution |
|
---|
Workaround |
---|
Notes |
---|
Last Modified Date | 11/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. |