System Update Tasks stuck at 'pending'.

Hi,

Thanks for the post.

Can you verify if the "DSM Essentials Task Manager" service is running? You can also try restarting the service and recreate the task. This service is responsible for running the tasks and if for some reason it is not running the update tasks will not proceed.

Regards

Abhijit

Abhijit -  I came in this morning and verified that the "DSM Essentials Task Manager" service is running.  Just for grins though, I restarted it.  Subsequent to that, I tried pushing out another task, but making it a scheduled task instead of a 'run now' and it seems to be working.  I don't know if it was the restart or the use of the scheduled task.  I'll have to do some more testing to see if I can reproduce the error.  FWIW, yesterday I rebooted the entire OME server and still had the problem.

Update:  'Run Now' seems to be working also.

Further Update:  I tried pushing out a larger number of updates at once and got a failure.  "Results:   Timeout was reached for obtaining the software update status from the target device. Please verify you can still connect to the device and manually run the inventory to determine if the update was successful."

Thanks for the updates.

As you may notice from the message, it doesn't really mean that updates were not applied. For multiple updates, it is possible for the status monitoring thread to reach timeout before all the packages are updated and confirmation is received. In that case, OME shows the above message where the status for the updates cannot be determined. It is possible that the updates were applied successfully but OME did not get the confirmation from the target server.

When the updates are applied, OME runs inventory automatically to refresh the component versions. In this case, since it reached timeout, the inventory will not run automatically. You can try running inventory for that target and OME will show you the updated component versions and the updated compliance report.

Let us know if the all the components are showing up as updated after the inventory is complete.

Thanks for the updates.

You can find all supported Agents/Devices/DBs/OSes information in OME Support Matrix located at the OME documentation link

http://support.dell.com/support/edocs/software/ome/en/index.htm

Just got off the phone with support.  They told me that Windows Server 2008 Storage is not a supported OS for OME, which is disappointing, but at least I know why it isn't working.

Thanks, hmmmm....

Ok, you said you restarted the task manager service which would have been my first suggestion.

Can you try doing a restart of the TM service _and_ try a "Run now"  on the task to see if that gets it running?

Rob

Exact the same problem here: I want to update 5 new Windows Server 2008 R2 Servers (fresh OS install with McAfee VSE 8.5 and Operations Manager 2007 R2 installed). What i have done so far:

-Configured SNMP

-Turned Network Discovery on

-Configured Windows Firewall Exclusion

System Update Task started, the Tasks runs sucessfully on the target server but the task displayed in OME runs in a time out.

News from my testing: You can turn on Network Discovery when the Service SSDP Discovery is not running! It turns itself off as soon as you save the settings.

What i have done:

-Restarting Task Manager Service

-Turning off Windows Firewall on OME Server and Target Server

-Setting SSDP Service to Automatic and started the Service on both Servers

-Finally Turning Network Discovery on on both Servers

Running a System Update Task = AND IT WORKS!

Im not sure what caused the problem. trying to find this one out now....

as soon as i turn on the firewall on both systems, the same problem is appearing again.

can you tell me wich ports i need to open on the Windows Firewall for the OME Server and the Target Servers?

my current fw exclusions:

ICMPv4 All Settings

UDP 137,138,161,162

Remote WMI

Hi,

Thanks for the updates. OME user guide lists all the ports in the user guide under “Managing Security Settings" section.

Here is the link to online version.

http://support.dell.com/support/edocs/software/ome/en/UG/UG_en.pdf

For system updates, you can confirm if you have port 135 open and add the application "omremote.exe" to the Firewall exception list.

Regards

Abhijit

Adding omremote.exe to the firewall exclusions on the OME Server did the trick. Thanks!

Thanks for taking the time to post an update.  Glad it is acting better now.

Best regards,

Rob