Share via

Unable to update to ConfigMgr 2309

JP Anderson 0 Reputation points
2023-10-30T19:28:03.95+00:00

Hi all,

I am trying to update Configuration Manager to 2309, but the Checking Prerequisites phase never completes, and is telling me ridiculous things like Server 2019 doesn't meet the minimum requirements. Even though I recently installed the 2303 update along with the Hotfix Rollup with absolutely no problems.

I've run the Update Reset Tool several times, but it hasn't helped.

Here is the log file. It just repeats this section over and over forever.

******************************************************************************* CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) CONFIGURATION_MANAGER_UPDATE service is starting... CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) Microsoft Microsoft Configuration Manager v5.00 (Build 9106) CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) Process ID: 440 CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) Worker thread ID: 20824 CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) Inbox source is local on COSSCCONFIG.redacted.com CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) Set inbox to j:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) This running on active site server COSSCCONFIG.redacted.com. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) Inbox source is local on COSSCCONFIG.redacted.com CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) INFO: Executing SqlCMUpdateInitScripts[0]. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) INFO: Executing SqlCMUpdateInitScripts[1]. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) INFO: Executing SqlCMUpdateInitScripts[2]. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) INFO: Executing SqlCMUpdateInitScripts[3]. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) INFO: Executing SqlCMUpdateInitScripts[4]. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) INFO: Executing SqlCMUpdateInitScripts[5]. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) INFO: Executing SqlCMUpdateInitScripts[6]. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) INFO: Executing SqlCMUpdateInitScripts[7]. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) INFO: Executing SqlCMUpdateInitScripts[8]. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) INFO: Executing SqlCMUpdateInitScripts[9]. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) INFO: Executing SqlCMUpdateInitScripts[10]. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) Getting SYSCENTERID & iLicenseType CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) Initializing the status message reporting system... CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) Inbox source is local on COSSCCONFIG.redacted.com CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) The path to the "Status Manager" inbox is "j:\Program Files\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs". CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) SMS_STATUS_MANAGER is not running as part of this process, the SMS_EXECUTIVE to SMS_STATUS_MANAGER in-memory status message queue will not be used. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:01 PM 20824 (0x5158) Registered this process as a source of "SMS Server" events. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:02 PM 20824 (0x5158) Registered this process as a source of "SMS Client" events. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:02 PM 20824 (0x5158) Registered this process as a source of "SMS Provider" events. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:02 PM 20824 (0x5158) Status message reporting system initialized successfully. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:02 PM 20824 (0x5158) There is no need to start monitoring thread. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:02 PM 20824 (0x5158) INFO: setup type: 1, top level: 1. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:02 PM 20824 (0x5158) Content replication succeeded. Start extracting the package to run prereq check... CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:02 PM 20824 (0x5158) Successfully reported ConfigMgr update status (SiteCode=SPK, SubStageID=0xd0005, IsComplete=1, Progress=1, Applicable=1) CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:02 PM 20824 (0x5158) Successfully reported ConfigMgr update status (SiteCode=SPK, SubStageID=0xd0005, IsComplete=1, Progress=25, Applicable=1) CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:02 PM 20824 (0x5158) Checking if the CMU Staging folder already has the content extracted. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:02 PM 20824 (0x5158) Creating hash for algorithm 32780 CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:02 PM 20824 (0x5158) Staging folder has hash = 2CBE56C104BE948653CDB44CD3A96D498790EF6F062934767206DD0BD7550ADA CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:29 PM 20824 (0x5158) Content is already found at the staging folder CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:29 PM 20824 (0x5158) Successfully reported ConfigMgr update status (SiteCode=SPK, SubStageID=0xd0005, IsComplete=1, Progress=50, Applicable=1) CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:29 PM 20824 (0x5158) File '\?\j:\Program Files\Microsoft Configuration Manager\CMUStaging\3F21A982-F4DD-4CDB-A746-6706AF4F36EC\SMSSetup\update.map.cab' is signed and trusted. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:29 PM 20824 (0x5158) File '\?\j:\Program Files\Microsoft Configuration Manager\CMUStaging\3F21A982-F4DD-4CDB-A746-6706AF4F36EC\SMSSetup\update.map.cab' is signed with MS root cert. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:29 PM 20824 (0x5158) Extracting file \?\j:\Program Files\Microsoft Configuration Manager\CMUStaging\3F21A982-F4DD-4CDB-A746-6706AF4F36EC\SMSSetup\update.map.cab to \?\j:\Program Files\Microsoft Configuration Manager\CMUStaging\3F21A982-F4DD-4CDB-A746-6706AF4F36EC\SMSSetup\ CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:29 PM 20824 (0x5158) Extracted \?\j:\Program Files\Microsoft Configuration Manager\CMUStaging\3F21A982-F4DD-4CDB-A746-6706AF4F36EC\SMSSetup\update.map CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:29 PM 20824 (0x5158) Successfully reported ConfigMgr update status (SiteCode=SPK, SubStageID=0xd0005, IsComplete=1, Progress=75, Applicable=1) CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:29 PM 20824 (0x5158) Successfully read file \?\j:\Program Files\Microsoft Configuration Manager\CMUStaging\3F21A982-F4DD-4CDB-A746-6706AF4F36EC\SMSSetup\update.map CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:29 PM 20824 (0x5158) Successfully reported ConfigMgr update status (SiteCode=SPK, SubStageID=0xd0005, IsComplete=2, Progress=100, Applicable=1) CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:29 PM 20824 (0x5158) FQDN for server COSSCCONFIG is COSSCCONFIG.redacted.com CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:29 PM 20824 (0x5158) INFO: Target computer is a 64 bit operating system. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:30 PM 20824 (0x5158) INFO: Checking for existing setup information. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:30 PM 20824 (0x5158) INFO: Setting setup type to 1. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:30 PM 20824 (0x5158) INFO: Checking for existing SQL information. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:30 PM 20824 (0x5158) INFO: 'COSSCCONFIG.redacted.com' is a valid FQDN. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:30 PM 20824 (0x5158) INFO: Verifying the registry entry for Asset Intelligence installation CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:30 PM 20824 (0x5158) INFO: Found registry key for installation of Asset Intelligence full version CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:30 PM 20824 (0x5158) INFO: Setup detected an existing Configuration Manager installation. Currently installed version is 9106 CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:30 PM 20824 (0x5158) INFO: Phase is 1C7 CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:30 PM 20824 (0x5158) INFO: SDK Provider is on COSSCCONFIG.redacted.com. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:30 PM 20824 (0x5158) Set working directory to the staging folder j:\Program Files\Microsoft Configuration Manager\CMUStaging\3F21A982-F4DD-4CDB-A746-6706AF4F36EC\SMSSetup CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:30 PM 20824 (0x5158) INFO: Setting the default CSV folder path CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:30 PM 20824 (0x5158) INFO: Language: Mobile Device (INTL), LangPack: 0. CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:30 PM 20824 (0x5158) INFO: Configuration Manager Build Number = 9120 CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:30 PM 20824 (0x5158) INFO: Configuration Manager Version = 5.0 CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:30 PM 20824 (0x5158) INFO: Configuration Manager Minimum Build Number = 800 CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:30 PM 20824 (0x5158) Preparing prereq check for site server [COSSCCONFIG.redacted.com]... CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:30 PM 20824 (0x5158) prereqcore has hash value SHA256:3FAB1FD043A7372F660951AA01C783BC5CB63D59B9DE4EC0D3E5A03DABA5465A CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:30 PM 20824 (0x5158) Running prereq checking against Server [COSSCCONFIG.redacted.com] ... CONFIGURATION_MANAGER_UPDATE 10/30/2023 12:08:30 PM 20824 (0x5158)

*********************
Also, i'm getting Crash dumps in the ConfigMgr Logs folder.[crash.log](/api/attachments/3bbfdf4d-9106-45d1-a05d-1b124cfc97a4?platform=QnA)
EXCEPTION INFORMATION
Time = 10/30/2023 12:15:29.370
Service name = 
Thread name = Unknown
Executable = j:\Program Files\Microsoft Configuration Manager\bin\x64\cmupdate.exe
Process ID = 528 (0x210)
Thread ID = 17032 (0x4288)
Instruction address = 00007FFC2E2A5DAE
Exception = c0000005 (EXCEPTION_ACCESS_VIOLATION)
Description = "The thread tried to read from the virtual address 30060 for which it does not have the appropriate access."
Raised inside CService mutex = No
CService mutex description = ""


Help is appreciated!

JP
Microsoft Configuration Manager Updates
Microsoft Configuration Manager Updates
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Updates: Broadly released fixes addressing specific issue(s) or related bug(s). Updates may also include new or modified features (i.e. changing default behavior).
1,040 questions
Microsoft Configuration Manager
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. rogergh 6 Reputation points
    2023-11-06T14:10:34.42+00:00

    We have a similar problem with the same symptoms (Pre-requisite check never finishes, tells us we have multiple warnings and failed checks, which definitely are false). Checking prerequisite logfiles tells us there is something wrong with ODBC\OLEDB connection to the SQL database.

    I made a similar thread if you want to keep updated with our status:

    https://learn.microsoft.com/en-us/answers/questions/1414549/sql-or-odbc-problem-when-trying-to-update-to-confi

    1 person found this answer helpful.
    0 comments
  2. AllenLiu-MSFT 44,191 Reputation points Microsoft Vendor
    2023-10-31T02:53:52.4266667+00:00

    Hi, @JP Anderson

    Thank you for posting in Microsoft Q&A forum.

    Based on the provided context, it is recommended to run the prerequisite checker before installing the Configuration Manager update 2309.

    To run a prerequisite check from the console, go to the Administration workspace, and select Updates and Servicing. Select the Configuration Manager 2309 update package and select Run prerequisite check in the ribbon.

    And check ConfigMgrPrereq.log for more details.

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.