When the SMS Executive service or WSUS application pool crashes, it may not release the mutex. The lock persists in memory or as a registry key, tricking the SUP into believing an operation is active.
The most effective fix is to manually purge the stuck task using the RACADM interface. You can execute this via SSH or the local OS command line: View current jobs: racadm jobqueue view
Before attempting to force a fix, you must verify that there isn't actually When the SMS Executive service or WSUS application
The error code indicates that the Dell iDRAC or Lifecycle Controller (LC) believes a firmware update or deployment task is already active . This often occurs as a "ghost" session when a previous update failed, timed out, or didn't clear its temporary RAM drive. Immediate Solutions
# Check if SUP is busy function Test-SUPBusy $syncStatus = Get-WmiObject -Namespace "root\SMS\site_$siteCode" -Class SMS_UpdateSyncStatus return $syncStatus.CurrentStatus -eq 3 # 3 = InProgress You can execute this via SSH or the
One such error that frequently appears in the dmpdownloader.log or CMUpdate.log files is:
This is a more aggressive reset:
False. A restart may clear the lock, but if WSUS or ConfigMgr services are misconfigured, the lock will reappear. Always diagnose first.
For official technical documentation on this error, refer to the or the VxRail KB Article . A restart may clear the lock, but if
Rarely, the internal SQL instances hosting the Azure Stack configuration data may have a transaction lock that hasn't been cleared, leading the Update Resource Provider to query an incorrect status.