SQLDirectConnectA语句执行时，Azure SQL Server崩溃 [英] Azure SQL Server Crashes When SQLDirectConnectA Statement Executes
问题描述
我对ODBC32.dll有疑问.我最近将一个很少使用的旧应用程序的ODBC驱动程序升级为SQL Server的ODBC驱动程序17，并删除了ODBC32.dll.
从我在应用程序中找到的所有地方开始.随后，我运行了"dumpbin/depends cPlusPlus.dll".在我的工作站上查找dll(cPlusPlus.dll)
包含我的C ++代码(包括ODBC代码)，我发现ODBC32.dll仍被列为依赖项.当我将应用程序部署到Azure时，它在SQLDirectConnectA语句上崩溃. Azure错误消息是:一个正在提供服务的进程
应用程序池"xxxx"与Windows Process Activation Service发生致命的通信错误." Azure是否期望ODBC32.dll而找不到它?访问Azure SQL Server数据库时，该应用程序在我的工作站上运行没有错误.
有任何想法吗 ?谢谢.
JS Greene
I have a question about ODBC32.dll. I recently upgraded the ODBC driver of a little-used legacy application to ODBC Driver 17 for SQL Server and I deleted ODBC32.dll
from all of the places I found it in the app. I subsequently ran a "dumpbin /dependents cPlusPlus.dll " on my workstation for the dll (cPlusPlus.dll)
which contains my C++ code including ODBC code and I discovered that ODBC32.dll is still listed as a dependent. When I deploy the application to Azure, it crashes on the SQLDirectConnectA statement. Azure error message is: "A process serving
application pool 'xxxx' suffered a fatal communication error with the windows Process Activation Service." Is Azure expecting ODBC32.dll and not finding it ? The application runs without error on my workstation while accessing Azure SQL Server databases.
Any ideas ? Thanks.
JS Greene
推荐答案
ODBC32.DLL是ODBC驱动程序管理器，是常见ODBC基础结构的一部分.无论您使用的是哪种特定的ODBC驱动程序，使用ODBC都需要这样做，并且不应将其删除.
ODBC32.DLL is the ODBC driver manager, part of common ODBC infrastructure. This is needed to use ODBC regardless of the specific ODBC driver you are using and should not be deleted.
这篇关于SQLDirectConnectA语句执行时，Azure SQL Server崩溃的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
