VMware Update Manager fails to start after a fresh install

Products

• VMware

Issue/Introduction

This document provides steps to troubleshoot the issue where VMware Update Manager does not start after a fresh install.

Symptoms:

• VMware Update Manager does not start after a fresh install
• Update Manager service fails to start
• VMware Update Manager log file vmware-vum-server-log4cpp.log (located at C:\Documents and Settings\All Users\Application Data\VMware\Update Manager or C:\Users\All Users\VMware\VMware Update Manager\Logs\) contain entries similar to:
  
  
  • failed to get module name for process
  • Error while checking for a running VMware Remote Device Server instance

Resolution

If one of the above errors is reported, perform this procedure to resolve this issue:

1. Check if the process rdevserver.exe is running using the Windows Task Manager on the server where Update Manager has been installed.
2. If this process exists, stop the process.
3. Once stopped, restart the VMware Update Manager. For more information, see Stopping, starting, and restarting the VMware Update Manager service (1039328).
4. The service should now start as expected.
   

Note: The rdevserver.exe process should be recreated during the start-up of the VMware Update Manager service.

Additional Information

If this issue persists, file a support request with VMware Support and note this KB article ID in the problem description. For more information, see Filing a Support Request in Customer Connect (2006985) or How to Submit a Support Request.

Installing vCenter Update Manager 4.x best practices
Stopping, starting, or restarting the vSphere Update Manager service
How to file a Support Request in Customer Connect