Latest ODBC Driver 18 for SQL (18.7.1.1) breaks SCCM Site Server SQL connectivity

Question

We have an automated update configured for ODBC Driver 18 for SQL which kicked in last night and took our install on the site server from 18.6.2.1 to 18.7.1.1 which seems to have completely broken Site Server -> SQL server connectivity.

Rolling back to 18.6.2.1 and restarting the Site Server is the fix (for now) but I'm sure our Information Security team will be asking to get patched again soon.

For info, the hman.log shows some threads stopping and then just goes dead when the update is applied and the Application event log is filled with "Complus" errors all related to the msodbcsql18.dll...

The system has called a custom component and that component has failed and generated an exception. This indicates a problem with the custom component. Notify the developer of this component that a failure has occurred and provide them with the information below.
Component Prog ID: 0[ODBC][C:\Windows\system32\msodbcsql18.dll]
Method Name: IDispenserDriver::CreateResource
Process Name: sitecomp.exe
Exception: c0000005
Address: 0X00007FFA85FD2C10

How do we raise this with Microsoft? Has anyone else seen the same? Site Server is on Server 2019 (patched monthly). Our SCCM site is version 2603.

Site Server and SQL DB on two different servers. Running E-HTTP mode.

I note that something similar happened not too long ago...

https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/setup-migrate-backup-recovery/update-odbc-18611-causes-issues-configmgr

Thanks

Stuart

sunilbs-msft · Answer

We have reviewed the crash details associated with your Configuration Manager connection failures after updating to Microsoft ODBC Driver 18.7.1.1.
&nbsp;
The crash occurs in the Microsoft Visual C++ runtime library, msvcp140.dll, during connection initialization. Our current assessment points to a compatibility issue between the newer ODBC driver and an older Visual C++ runtime loaded from Configuration Manager’s application-local folder.&nbsp;
&nbsp;
Recommended next steps:
Immediate mitigation: Rolling back to the previously working, supported ODBC driver version.
Long-term resolution: Configuration Manager support to determine the supported approach for updating its application-local Visual C++ runtime dependencies.
Updating the system-wide Visual C++ Redistributable alone may not resolve the issue if Configuration Manager continues to load an older application-local copy. Please avoid manually replacing or removing individual runtime DLLs without support guidance.
We understand the disruption this issue is causing and will use these details to confirm the appropriate resolution.

james1731 · Answer

Any ETA on Config manager support team providing the supported way to refresh the local VC++ Redistributable runtimes?

We just ran into this exact issue also and stumbled on this page to learn it was the ODBC 18 driver.

mattias nylund · Answer

same exact issue here. had to roll back the odbc version. thanks for the report!&nbsp;

cwilliams255 · Answer

Yep same issue here, rolled back ODBC driver, all good

ms_edrusi · Answer

We had the same issue. Thank you for posting this.

Forum Discussion

Latest ODBC Driver 18 for SQL (18.7.1.1) breaks SCCM Site Server > SQL connectivity

10 Replies