Skip to content
Microsoft ODBC driver 18 for SQL setup Issue with SCCM 2309 Upgrade

Microsoft ODBC driver 18 for SQL setup Issue with SCCM 2309 Upgrade

Written By Anoop C Nair
Last Updated October 12, 2023
Posted In SCCM
SHARE

Let’s try to fix the Microsoft ODBC driver 18 for the SQL setup Issue with the SCCM 2309 Upgrade. This is because the SQL Client prerequisite is missing for Config Manager Setup. It’s important to go through the SCCM 2309 infra upgrade checklist before the upgrade process.

Microsoft released the latest version of SCCM 2309, and it came out with new features and enhancements. Microsoft also announced the deprecation of some of the features, such as configuration profiles etc.

The redistributable installer for Microsoft ODBC Driver 18 for SQL Server installs the client components required during run time to take advantage of newer SQL Server features. Version 18.3.2.1 is the latest general availability (GA) version.

Microsoft added a new feature that allows administrators to schedule script runtimes in UTC. Also added the option to utilize the native Windows Update restart experience when installing monthly patches. More details on SCCM 2309 features are available – SCCM 2309 Upgrade Guide | New Features.

Patch My PC

SCCM 2309 for Beginners: A Step-by-Step Tutorial for Upgrade Process

Video Tutorial – SCCM 2309 for Beginners: A Step-by-Step Tutorial for Upgrade Process. New features of SCCM 2309 are also discussed in this video. Deprecated feature announcement is also discussed.

Video 1 – SCCM 2309 for Beginners: A Step-by-Step Tutorial for Upgrade Process

Microsoft ODBC driver 18 for SQL setup Issue

If the version of the ODBC driver is missing on the site servers (CAS, Primary, etc), the prerequisite check for 2309 will fail.

Microsoft ODBC driver 18 for SQL setup Issue with SCCM 2309 Upgrade Fig. 1
Microsoft ODBC driver 18 for SQL setup Issue with SCCM 2309 Upgrade Fig. 1

You normally get the following error during the prerequisite checks. You can check the SCCM log file called ConfigMgrPrereq.log to get more details on the issue. The following are the two main errors.

  • Microsoft ODBC Driver 18 for SQL Server is not installed
  • SQL client prerequisite missing for Config Manager setup.; Error

INFO: Checking MSODBC version on ServerName CMMEMCM.memcm.com
INFO: Failed to open registry key SOFTWARE\Microsoft\MSODBCSQL18 on CMMEMCM.memcm.com. Error = 2
INFO: Microsoft ODBC Driver 18 for SQL Server is not installed
CMMEMCM.memcm.com; SQL client prerequisite missing for Config Manager setup.; Error; Install the Microsoft ODBC driver 18 for SQL setup from https://go.microsoft.com/fwlink/?linkid=2220989. More information https://go.microsoft.com/fwlink/?linkid=2226618

You need to ensure that the Microsoft ODBC driver 18 for SQL setup as part of the SQL client is installed on Primary, SQL, and CAS servers. In the log file below, you can see the standalone primary server name – CMMEMCM.memcm.com.

SQL setup Issue with SCCM 2309 Upgrade Fig. 2
SQL setup Issue with SCCM 2309 Upgrade Fig. 2

Download Microsoft ODBC driver 18 Offline File

You can download the offline file for Microsoft ODBC driver 18 for SQL setup from the following Microsoft link. The same link is given in SCCM 2309 prerequisite checks.

Download the Link for msodbcsql.msihttps://go.microsoft.com/fwlink/?linkid=2220989

Microsoft ODBC driver 18 for SQL setup Issue with SCCM 2309 Upgrade Fig. 3
Microsoft ODBC driver 18 for SQL setup Issue with SCCM 2309 Upgrade Fig. 3

Install Microsoft ODBC driver 18

Ensure that the msodbcsql.msi is installed on CAS, Primary, and SQL servers to complete the upgrade of the SCCM 2309 version successfully. We have installed it only on the SQL server, but that didn’t help to fix the issue.

Always check the ConfigMgrPrereq.log to get more details about the server where you have to install Microsoft ODBC driver 18 for SQL, as explained in the above section of the post.

The installation itself is straightforward; you just need to launch it with administrative privileges. Also, there is no need for restarting the servers after the Microsoft ODBC driver 18 for SQL installation.

Microsoft ODBC driver 18 for SQL setup Issue with SCCM 2309 Upgrade Fig. 4
SQL setup Issue with SCCM 2309 Upgrade Fig. 4

FIXED SCCM 2309 Prerequisite – SQL Client prerequisite is missing for Config Manager Setup Issue

Now, it’s time to rerun the SCCM 2309 prerequisite checks to confirm whether the issue is fixed or not. The SQL Client prerequisite is missing for Config Manager Setup Issue is fixed after installing the Microsoft ODBC driver 18 for the SQL component on the standalone primary server.

Microsoft ODBC driver 18 for SQL setup Issue with SCCM 2309 Upgrade Fig. 5
Setup Issue with SCCM 2309 Upgrade Fig. 5

Author

Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.

Written by

Anoop C Nair is Workplace Technology solution architect with 25+ years of experience in global enterprise organizations such as JP Morgan, Capgemini, etc. Microsoft Certified Trainer. Microsoft MVP from 2015 onwards for consecutive 11+ years! He also conducts Intune and modern workplace tech training for enterprise organizations. He is Blogger, Speaker, and Founder of HTMD Community and HTMD Conference. His main focus is on Device Management technologies like Intune, Windows, Cloud PC. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security.

Discussion · 6 comments

  1. Hi Anoop,
    I applied the new ODBC driver 18 for SQL, but now I see the following in the ConfigMgrPrereq.log file.

    * [08001][-2146893022][Microsoft][ODBC Driver 18 for SQL Server]SSL Provider: The target principal name is incorrect.
    * [08001][-2146893022][Microsoft][ODBC Driver 18 for SQL Server]Client unable to establish connection
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.

    The log constantly retries the prerequisite checks but fails to access SQL. I see lots of other forums where this driver is causing these errors and it is not just related to ConfigMgr.

    Any ideas?

  2. Saw someone post from X who run into prereq issues like “Failed to connect to the SQL Server, connection type SMS ACCESS. check if you have SSL set to force on the SQL instance. He Had to disable to get this to run with the new ODBC driver.

  3. Hi Anoop, thanks for the post. I can see the docs state that it needs to be on te primary, CAS, Secondary, SUP and MP site systems but couldn’t see anything about the SQL Server (Site Database Role). We just had a Primary with SQL on a seaprate SQl box and also a second DP. I’m assuming that we just need to install it on the Primary SCCM Server. Is that correct?

    https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/configs/site-and-site-system-prerequisites#sql-odbc-driver-for-the-site-server

  4. Hi I trying to upgrade 2503 prerequisite is failed stating [Failed]:Install the Microsoft ODBC driver 18 for SQL setup from https://go.microsoft.com/fwlink/?linkid=2220989.
    I have installed ODBC driver and still i get the same error .
    * [08001][-2146893051][Microsoft][ODBC Driver 18 for SQL Server]A network-related or instance-specific error has occurred while establishing a connection to vmmecmdb.acnktn.com. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. CONFIGURATION_MANAGER_UPDATE 4/19/2025 11:31:28 PM 28528 (0x6F70)
    * Failed to connect to the SQL Server, connection type: SMS ACCESS. CONFIGURATION_MANAGER_UPDATE 4/19/2025 11:31:28 PM 28528 (0x6F70)

    * [08001][-2146893051][Microsoft][ODBC Driver 18 for SQL Server]A network-related or instance-specific error has occurred while establishing a connection to vmmecmdb.acnktn.com. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. CONFIGURATION_MANAGER_UPDATE 4/19/2025 11:31:29 PM 28528 (0x6F70)
    * Failed to connect to the SQL Server, connection type: SMS ACCESS. CONFIGURATION_MANAGER_UPDATE 4/19/2025 11:31:29 PM 28528 (0x6F70)

Join the discussion

Your email address will not be published. Required fields are marked *

Related guides

Intune

Windows 11 KB5101650 KB5099414 July 2026 Patch and 3 Zero Day Vulnerabilities and 570 Flaws

Key Takeaways Windows 11 KB5101650 KB5099414 July 2026 Patch and 3 Zero Day Vulnerabilities and 570 Flaws! In the July 2026 Patch, Microsoft introduced new features designed to improve the overall Windows experience. The update adds enhancements to Windows Update for more flexible update management and introduces Point-in-Time Restore, providing an additional recovery option for […]

AC Anoop C Nair 9 min read
Intune

2026 June KB5094126 KB5093998 Windows 11 Patch | 3 Zero Day Vulnerabilities and 200 Flaws

Key Takeaways 2026 June KB5094126 KB5093998 Windows 11 Patch | 3 Zero Day Vulnerabilities and 200 Flaws! The June 2026 Windows 11 Patch Tuesday update brings several improvements to File Explorer. It adds support for additional archive formats, including UU, CPIO, XAR, and NuGet Packages (NUPKG). The update also preserves View and Sort preferences in […]

AC Anoop C Nair 10 min read
Intune

2026 May KB5089549 KB5087420 Windows 11 Patch | 0 Zero Day Vulnerabilities and 120 Flaws

Key Takeaways The Windows 11 May 2026 Patch KB5089549 KB5087420 Update brings important security fixes, performance improvements, and reliability enhancements across the operating system. The update introduces new features such as Xbox Mode for gaming, File Explorer improvements, enhanced input and sharing experiences, better taskbar and Windows Hello reliability, and additional enterprise management capabilities for […]

AC Anoop C Nair 8 min read
SCCM

ConfigMgr 2603 Introduces New Early Update Enrollment Process

Key Takeaways In this post we are discussing the ConfigMgr 2603 Introduces New Early Update Enrollment Process. Microsoft has officially released Configuration Manager version 2603 to the Early Update Ring, giving organizations an opportunity to test upcoming improvements before the global production rollout. The release is targeted at enterprises running ConfigMgr version 2409 or later […]

AC Anoop C Nair 3 min read