System Center Upgrade gets stuck at Upgrade ConfigMgr Database

Question

Hi.

Started an SCCM upgrade to 2409 CB, but got stuck at Upgrade ConfigMgr Database step. Follow is the entry in CMUpdate.log:

[CONFIGURATION_MANAGER_UPDATE] is currently blocked in database by another session [SMS_STATE_SYSTEM][session_id=396][texthash=43DBDC114ED2486FCEC51A2F3DC66395A251E0424A42A9C30085B3A1891202B6]. Please follow documentation https://go.microsoft.com/fwlink/?linkid=2098729 and review the blocking session.

Followed the steps described in https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/setup-migrate-backup-recovery/site-upgrade-blocked-in-database-update and found this on the SQL:

396 396 LCK_M_SCH_M LCK_M_SCH_M OBJECT: 2:-1535237352:3 exec spSummaryTaskEPSecurityHealthDashboard '168', 0x00000000000000 exec spSummaryTaskEPSecurityHealthDashboard '168', 0x0000000000000000

Looking at Activity Monitor, this session is related to SMS_STATE_SYSTEM:

I cannot kill the session, all the SCCM services are stopped on the server. How can I proceed to either upgrade or cancel it?

Regards,

Thiago

Answer 1

Hi Thiago B Andrade,

Thanks very much for your feedback and sharing. Here's a short summary of the problem. It's appreciated that you could click "Accept Answer" to the helpful reply, this will help other users to search for useful information more quickly.

Problem/Symptom:

Tried to upgrade SCCM to version 2409, but got stuck at Upgrade ConfigMgr Database step with below entry in CMUpdate.log.

[CONFIGURATION_MANAGER_UPDATE] is currently blocked in database by another session.

Solution/Workaround:

Ended up stopping the Configuration Manager Update Service manually. Tried to put the database in offline mode, but it failed. Then restarted SQL service to flush the lock.

After that, restarted the Upgrade process and everything went fine and it is concluded.

Thanks again for your time. Have a nice day!

Best regards,

Simon

---

If the response is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

After the way you tag questions on Q&A is updated, for any "Microsoft Configuration Manager" related problem, you can tag it with "Microsoft Intune", and then "Microsoft Configuration Manager" as the child tag.

Answer 2

Hi Simon.

Thanks for your support. I ended up stopping the Configuration Manager Update Service manually. Tried to put the database in offline mode, but it failed. Then I restarted SQL service to flush the lock.

After that, I restarted the Upgrade process and everything went fine and it is concluded.

Obviously, I did all of that with a backup ready, just in case.

Anyway, thanks again.

Thiago

Answer 3

Hi,

Hope everything is going well.

1,We can try to use the CMUpdateReset tool to reset an in-console update with download or replication problem. For more information, please refer to:

<SCCM Install Folder>cd.latest\SMSSETUP\TOOLS\CMUpdateReset>CMUpdateReset.exe -FDELETE -S <your SQL Server> -D CM_1 -P <package GIUD>

2309 Hotfix Stuck on Installing

Update reset tool

2,Please kindly review the ConfigMgrPrereq.log, CMUpdate.log and ConfigMgrAdminUISetup.log to check if there is any further information.

3,What version of the ODBC driver for SQL server on your site servers? Starting with Configuration Manager 2309 release, Configuration Manager requires the installation of the ODBC driver for SQL server 18.1.0 or later as a prerequisite. This prerequisite is required when you create a new site or update an existing one and on all remote roles. Refer to:

Introducing SQL ODBC driver support for Configuration Manager

Hope it helps. Have a nice day!

Best regards,

Simon

---

If the response is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

After the way you tag questions on Q&A is updated, for any "Microsoft Configuration Manager" related problem, you can tag it with "Microsoft Intune", and then "Microsoft Configuration Manager" as the child tag.