Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED SCCM update to 2503 fails prerequisite checks due to missing ODBC driver 18 for SQL

Status
Not open for further replies.

Greenman

New Member
Messages
2
Reaction score
1
Points
1
The issue is as above, however I can definitely confirm that the driver is installed.
Currently running 5.00.9132.1023 (version 2409 with all hotfixes)

As part of troubleshooting, I've uninstalled, rebooted, and then re-installed the driver, then rebooted again.
Upgraded the SQL server version from 2016 to 2022, then repeated the above step.

This is the only prerequisite that is failing, everything else is okay regarding SQL server connection, firewall exceptions etc
I'm wondering if older versions of the driver could be causing problems, but I don't want to remove anything that is potentially needed...

I've included screenshots showing what I'm seeing in the console and a screenshot of programs and features showing the driver installed.

I've looked through the HMAN.log and CMUpdate.log and posted the relevant section of CMUpdate.log (a full capture of the logs over the time of the prerequisite check from start to finish) at the bottom of this post.

Hoping someone else has had this issue previously and solved it. Thanks in advance!



Detected a change to the "C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box" directory. CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:48:12 2076 (0x081C)
INFO: setup type: 1, top level: 1. CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:48:12 2076 (0x081C)
Content replication succeeded. Start extracting the package to run prereq check... CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:48:12 2076 (0x081C)
Successfully reported ConfigMgr update status (SiteCode=, SubStageID=0xd0005, IsComplete=1, Progress=1, Applicable=1) CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:48:12 2076 (0x081C)
Successfully reported ConfigMgr update status (SiteCode=, SubStageID=0xd0005, IsComplete=1, Progress=25, Applicable=1) CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:48:12 2076 (0x081C)
Checking if the CMU Staging folder already has the content extracted. CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:48:12 2076 (0x081C)
Creating hash for algorithm 32780 CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:48:12 2076 (0x081C)
Staging folder has hash = 9CF4CA50E5ECECA8114398CE02D43C8453F120171FD9C2A570233E0AA8ED7D6E CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
Content is already found at the staging folder CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
Successfully reported ConfigMgr update status (SiteCode=, SubStageID=0xd0005, IsComplete=1, Progress=50, Applicable=1) CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
File '\\?\C:\Program Files\Microsoft Configuration Manager\CMUStaging\AA928926-5C76-4DE0-B51F-0FE4D365DFE2\SMSSetup\update.map.cab' is signed and trusted. CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
File '\\?\C:\Program Files\Microsoft Configuration Manager\CMUStaging\AA928926-5C76-4DE0-B51F-0FE4D365DFE2\SMSSetup\update.map.cab' is signed with MS root cert. CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
Extracting file \\?\C:\Program Files\Microsoft Configuration Manager\CMUStaging\AA928926-5C76-4DE0-B51F-0FE4D365DFE2\SMSSetup\update.map.cab to \\?\C:\Program Files\Microsoft Configuration Manager\CMUStaging\AA928926-5C76-4DE0-B51F-0FE4D365DFE2\SMSSetup\ CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
Extracted \\?\C:\Program Files\Microsoft Configuration Manager\CMUStaging\AA928926-5C76-4DE0-B51F-0FE4D365DFE2\SMSSetup\update.map CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
Successfully reported ConfigMgr update status (SiteCode=, SubStageID=0xd0005, IsComplete=1, Progress=75, Applicable=1) CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
Successfully read file \\?\C:\Program Files\Microsoft Configuration Manager\CMUStaging\AA928926-5C76-4DE0-B51F-0FE4D365DFE2\SMSSetup\update.map CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
Successfully reported ConfigMgr update status (SiteCode=, SubStageID=0xd0005, IsComplete=2, Progress=100, Applicable=1) CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
FQDN for server CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
INFO: Target computer is a 64 bit operating system. CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
INFO: Checking for existing setup information. CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
INFO: Setting setup type to 1. CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
INFO: Checking for existing SQL information. CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
INFO: '' is a valid FQDN. CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
INFO: Verifying the registry entry for Asset Intelligence installation CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
INFO: Found registry key for installation of Asset Intelligence full version CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
INFO: Setup detected an existing Configuration Manager installation. Currently installed version is 9132 CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
INFO: Phase is 1C7 CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
INFO: SDK Provider is on . CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
Set working directory to the staging folder C:\Program Files\Microsoft Configuration Manager\CMUStaging\AA928926-5C76-4DE0-B51F-0FE4D365DFE2\SMSSetup CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
INFO: Setting the default CSV folder path CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
INFO: Language: Mobile Device (INTL), LangPack: 0. CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
INFO: Configuration Manager Build Number = 9135 CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
INFO: Configuration Manager Version = 5.0 CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
INFO: Configuration Manager Minimum Build Number = 800 CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
Preparing prereq check for site server []... CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
prereqcore has hash value SHA256:48899098998C712DDF097638B281D5620D8C511FB9B51E2391119281E0ECA43E CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
Running prereq checking against Server [] ... CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:02 2076 (0x081C)
INFO: SQL Connection succeeded. Connection: SMS ACCESS, Type: Secure CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:19 2076 (0x081C)
Waiting for changes to the "C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 400 seconds... CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:19 2076 (0x081C)
Detected a change to the "C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box" directory. CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:19 2076 (0x081C)
Waiting for changes to the "C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 400 seconds... CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:19 2076 (0x081C)
Detected a change to the "C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box" directory. CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:19 2076 (0x081C)
Waiting for changes to the "C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box" directories, updates will be polled in 400 seconds... CONFIGURATION_MANAGER_UPDATE 29/04/2025 15:49:19 2076 (0x081C)
 

Attachments

  • Screenshot 2025-04-29 151155.png
    Screenshot 2025-04-29 151155.png
    45.3 KB · Views: 23
  • Screenshot 2025-04-29 145753.png
    Screenshot 2025-04-29 145753.png
    74.8 KB · Views: 30
I am running into the same issue. I have ODBC 18 installed, and it still fails at this same step. I suspect this is an issue with the upgrade.
 
Status
Not open for further replies.

Forum statistics

Threads
7,130
Messages
27,846
Members
18,145
Latest member
Rothgar
Back
Top