Microsoft finally provides a solution to bypass Windows applications broken by the SQL Server Bagby driver

[ad_1]

Windows 11 logo as a window with some ladybugs crawling towards it

While Patch Tuesday updates are meant to provide Windows security fixes, they often lead to major problems as well. Tuesday’s November patch for both Windows 11 and Windows 10, as well as Windows Server, caused application problems due to an ODBC SQL Server Driver bug.

Microsoft said affected users will receive an application error or an error from SQL Server, such as “The EMS system encountered a problem” with “Message: [Microsoft][ODBC SQL Server Driver] Protocol Error in TDS Stream” or “Message: [Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server”.

Today, Microsoft finally released a fix for the problem, although the delay is quite understandable since it was the holiday season in the US and many other parts of the world. Author:

Workaround: To alleviate this problem, you can do one of the following:

  • If your app already uses or can use data source name (DSN) To select ODBC connections, install the Microsoft ODBC Driver 17 for SQL Server and select it for use with your application via DSN. Note: We recommend the latest version of Microsoft ODBC Driver 17 for SQL Server because it is more compatible with applications that currently use the older Microsoft ODBC SQL Server driver (sqlsrv32.dll) than Microsoft ODBC Driver 18 for SQL Server.
  • ‚ÄčIf your application is unable to use DSN, the application will need to be modified to enable DSN or use a newer ODBC driver than the Microsoft SQL Server ODBC driver (sqlsrv32.dll).

The Redmond company says it is working on a permanent fix for the problem.



[ad_2]

Leave a Comment