Forum Discussion
Latest ODBC Driver 18 for SQL (18.7.1.1) breaks SCCM Site Server > SQL connectivity
We have reviewed the crash details associated with your Configuration Manager connection failures after updating to Microsoft ODBC Driver 18.7.1.1.
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.
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.
- BrianI99Oct 22, 2026Brass Contributor
It has been over a month since your last reply. There appears to still be zero Microsoft acknowledgement of this issue other than your post. Is the ConfigMgr team actively working on the dependency issue? It's only a matter of time before a new CVE is discovered for this driver.
- SPearson_Oct 22, 2026Brass Contributor
As far as I understand it, it's resolved in the 2609 update (which I believe is GA but yet to be available in our console).
The info is here...https://learn.microsoft.com/en-us/intune/configmgr/core/servers/manage/checklist-for-installing-update-2609
Important
Microsoft ODBC Driver for SQL Server version 18.7.1.1 has a known issue with Configuration Manager version 2603 and earlier that can block site configuration. If you're updating from one of these versions, don't install ODBC driver version 18.7.1.1 before the update. Complete the Configuration Manager update to version 2609 before you install this ODBC driver version.
- SPearson_Oct 22, 2026Brass Contributor
Just found that 2609 is only available for opt-in to the 2609 Early Update Ring...
https://learn.microsoft.com/en-us/intune/configmgr/core/servers/manage/checklist-for-installing-update-2609#early-update-ring
- NuttybarSep 28, 2026Copper Contributor
we had this issue, and roll back fixed it
we would see EVENT ID 4786, Source COMPLUS in the event log
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: 4[ODBC][C:\Windows\system32\msodbcsql18.dll]
Method Name: IDispenserDriver::CreateResource
Process Name: sitecomp.exe
Exception: c0000005
Address: 0X00007FFAA97C2C10
AND
In the SMSEXEC.LOG on the server i would see
*** Failed to connect to the SQL Server, connection type: SMS ACCESS. SMS_EXECUTIVE 9/27/2026 6:30:01 AM 3848 (0x0F08) CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection SMS_EXECUTIVE 9/27/2026 6:30:01 AM 3848 (0x0F08) CSiteControlEx::GetSCF:Failed to read site information from database, retry in 5 seconds ... SMS_EXECUTIVE 9/27/2026 6:30:01 AM 3848 (0x0F08) *** *** Unknown SQL Error! SMS_EXECUTIVE 9/27/2026 6:30:06 AM 3848 (0x0F08) *** Failed to connect to the SQL Server, connection type: SMS ACCESS. SMS_EXECUTIVE 9/27/2026 6:30:06 AM 3848 (0x0F08) CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection SMS_EXECUTIVE 9/27/2026 6:30:06 AM 3848 (0x0F08) CSiteControlEx::GetSCF:Failed to read site information from database, retry in 5 seconds ... SMS_EXECUTIVE 9/27/2026 6:30:06 AM 3848 (0x0F08) - Hardy_72Sep 17, 2026Copper Contributor
Hi!
Is a resolution possible in the next days?
- James1731Sep 15, 2026Copper Contributor
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.