USE SUSDB EXEC spDeleteUpdate @localUpdateID = 0, @bIsLocPublished = 0
If you manage software updates in Microsoft Configuration Manager (Current Branch), you have likely encountered the dreaded error.
Here’s a concise for the error SUP0108: A deployment or update operation is already in progress — useful for documentation, a knowledge base, or a troubleshooting guide.
Log back into the iDRAC Web Interface and verify the job queue is empty under > Job Queue . 3. Execute a System Cold Boot : Use the Dell RACADM tool or the
Q: What does the SUP0108 error mean? A: The SUP0108 error indicates that a deployment or update operation is already in progress, and another operation cannot be started.
: Use the Dell RACADM tool or the iDRAC GUI (Maintenance > Job Queue) to delete any "Pending" or "Failed" tasks.
) or by holding the "i" button on the server's front panel for 20 seconds. Clear the Job Queue : Log in to the iDRAC UI, navigate to the Follow these troubleshooting procedures
The underlying database schema still marks the system status as "Deploying" due to a timeout. Step-by-Step Resolution Guide 1. Verify Active Deployments
: To execute firmware upgrades, the iDRAC installer sometimes places a temporary RAM drive onto the host operating system. Failure to clear this drive automatically leaves the system locked.
Follow these troubleshooting procedures, ordered from the least invasive method to the most comprehensive. Method 1: Clear the iDRAC Job Queue and Reset // or 'stuck'
var gr = new GlideRecord('sys_upgrade_history'); gr.addQuery('state', 'pending'); // or 'stuck', 'error' gr.query(); while (gr.next()) gr.deleteRecord();
ServiceNow stores upgrade histories in the sys_upgrade_history table. Occasionally, an incomplete upgrade leaves records that block new deployments. To clean this table:
When a RAM drive remains stubbornly mounted or hardware registers become unresponsive, a standard warm reboot of the server will not suffice. You must perform a cold boot to drain residual flea power from the motherboard. Safely the host operating system. Unplug all power cables from the back of the server.
In the SUP properties under , increase the timeout value (default is 30 minutes). Large environments may need 120 minutes to avoid false "operation in progress" errors.
