Your 30-day trial comes with
Full access to Studio Enterprise
Web, Mobile, Desktop, API testing
Easy setup, 1-click integrations
No credit card required
Or Update Operation Is Already In Progress Best: Sup0108 A Deployment
: A previous update failed during file transfer or timed out, leaving a "lockfile" that prevents new jobs. Active LCC
: When a firmware task is initialized, a lockfile is auto-generated to prevent double-flashing. If a network timeout or file transfer failure occurs while the job state reads "Downloading," the file is never deleted, resulting in a persistent lock.
Follow these troubleshooting procedures, ordered from the least invasive method to the most comprehensive. Method 1: Clear the iDRAC Job Queue and Reset
Alternatively, hold the on the front of the server for about 16 seconds until the fans spin up. : A previous update failed during file transfer
By following the solutions above—starting with clearing the RefreshNow flag and escalating to a full SUP reinstall—you can resolve the error in under 15 minutes. More importantly, by respecting the boundary between WSUS (the engine) and ConfigMgr (the manager), you will rarely see this error again.
racadm jobqueue delete -i JID_CLEARALL
The error is a protective measure, not a system failure. By identifying the hung process, waiting for timeouts to clear, or manually releasing the deployment lock, you can get your updates back on track. More importantly, by respecting the boundary between WSUS
A deployment or update operation can remain "in progress" for several reasons. These include a legitimate, long-running firmware installation, a stalled or "hung" process, a previous job that was interrupted by a browser crash, or even a pending task that is stuck in the queue waiting for the server hardware (like the Lifecycle Controller) to become available.
Ensure only one developer or admin is responsible for pushes at any given time.
To resolve this, you generally need to force the iDRAC to reset its state: Via RACADM (CLI) "status": "queued"
By following the systematic troubleshooting steps and best practices outlined in this guide, you can minimize downtime, reduce operational friction, and maintain a healthy firmware update process across your Dell PowerEdge infrastructure.
A soft reset restarts the management controller without impacting the production operating system or the server's running workloads. Via Web GUI Log into the . Navigate to the Dashboard . Locate the Quick Links section on the right side. Click Reset iDRAC . Via RACADM (CLI)
"status": "queued", "message": "A deployment is already in progress. Your request has been queued.", "position": 2, "request_id": "def-456"
# Clear all pending and stuck jobs racadm jobqueue delete -i JID_CLEARALL # Soft-reboot the iDRAC control plane racadm racreset Use code with caution. Method 2: Perform an Auxiliary Power Drain (Cold Boot)
