This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We have an application that communicate with MS SQL Server.
The issue appeared in case of communication failure. We are trying to recover connection but application crashed in MS ODBC driver code:
Stack trace:
> msvcr120.dll!abort() Line 88 C
msvcr120.dll!_purecall() Line 59 C
msodbcsql13.dll!ConnectionRecoveryManager::Recover(void) Unknown
msodbcsql13.dll!ConnectionRecoveryManager::RecoverThreadRoutine(void *) Unknown
ntdll.dll!RtlpTpWorkCallback() Unknown
ntdll.dll!TppWorkerThread() Unknown
kernel32.dll!BaseThreadInitThunk() Unknown
ntdll.dll!RtlUserThreadStart() Unknown
How to resolve this issue?
SQL driver version: 2017.0140.1000.169
Hi @Repkin Dmitry ,
Any update for this thread? Could you share us the information that I mentioned?
Hi @Repkin Dmitry ,
Please share us the error message from the SQL server error log for analysis.
What is the SQL server version? Please using select @@version to check this.
Hello. We are trying to get exact version of SQL Server, but it looks like a client side failure.
Connection was terminated by a networks failure, not a fault of SQL Server itself.
The issue is the SQL Server driver (msodbcsql13) crash the application and we cannot recover the connection in application side.
Excuse me for asking something that might be obvious, but do you have exception handling in your code?
You could try to move to the most recent version of the ODBC driver, which I think is 17.4, https://learn.microsoft.com/en-us/sql/connect/odbc/download-odbc-driver-for-sql-server?view=sql-server-ver15.
Yes, we have an exception handling, but it is not our thread. It is a thread owned by msodbcsql13.
Not sure I get this, but that may be related to that I don't write ODBC applications very often. Or al all.
Are you making an asynchronous call?
Maybe you should ask in a C++ forum to get ideas of how could trap the error without crashing the entire application?
No; we are using synchronous calls to ODBC.
This thread is not ours; it is an MS SQL Server ODBC driver (msodbcsql13.dll) thread.
Microsoft SQL Server 2017 (RTM-CU17) (KB4515579) - 14.0.3238.1 (X64) Sep 13 2019 15:49:57 Copyright (C) 2017 Microsoft Corporation Developer Edition (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: )
No messages in SQL server log at issue time, because the issue is at client.
So you mean that ODBC internally starts new threads? That sounds a little unlikely to me. But, OK, maybe ODBC decides to exit in such a way that it bypasses your exception handling.
As I said, I'm not an ODBC programmer, and nor am I good C++ programmer. Still, I'm kind of curious, and I would be interested to play with a repro, if you are able to distill this to a simple program. I realise that this can be difficult, since we need a communication failure to go with the error.
I think I've found the solution for you. I believe that this problem can be solved with connection resiliency. Take a look here:
https://learn.microsoft.com/en-us/sql/connect/odbc/windows/connection-resiliency-in-the-windows-odbc-driver?view=sql-server-ver15
I have not checked in which version of the ODBC driver this was implemented, so you may have to upgrade.