VMware Cloud Community
realdreams
Enthusiast
Enthusiast

vSphere Update Manager 5.1 fails to start after fresh install

vSphere 5.1

trying to install VUM on Windows Server 2008 R2 x64 with vCenter 5.1 and SQL 2008 R2 Express. First installation finished but the process crashes instantly.

The VMware vSphere Update Manager Service service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 300000 milliseconds: Restart the service.

Same problem after reintallation.

[2012-09-23 18:09:12:845 '' 2284 ALERT]  [logUtil, 265] Product = VMware Update Manager, Version = 5.1.0, Build = 782803
[2012-09-23 18:09:12:845 'VcIntegrity' 2284 DEBUG]  [vcIntegrity, 1111] Getting managed process information from configuration
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 127] Failed to open handle for process 4. Error: 5. Ignoring the process
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 240. Error: 299. Ignoring the process
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 344. Error: 299. Ignoring the process
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 396. Error: 299. Ignoring the process
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 404. Error: 299. Ignoring the process
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 440. Error: 299. Ignoring the process
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 500. Error: 299. Ignoring the process
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 508. Error: 299. Ignoring the process
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 516. Error: 299. Ignoring the process
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 612. Error: 299. Ignoring the process
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 692. Error: 299. Ignoring the process
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 780. Error: 299. Ignoring the process
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 820. Error: 299. Ignoring the process
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 876. Error: 299. Ignoring the process
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 916. Error: 299. Ignoring the process
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 956. Error: 299. Ignoring the process
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 360. Error: 299. Ignoring the process
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 1080. Error: 299. Ignoring the process
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 1144. Error: 299. Ignoring the process
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 1164. Error: 299. Ignoring the process
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 1348. Error: 299. Ignoring the process
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 1380. Error: 299. Ignoring the process
[2012-09-23 18:09:12:845 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 1532. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 1560. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 1616. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 1648. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 1656. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 1696. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 1716. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 1760. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 1768. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 1832. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 1880. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 1900. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 1940. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 1968. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 1988. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 3076. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 3176. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 3340. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 3460. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 3816. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 3884. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 3924. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 4072. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 3448. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 4028. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 2384. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 2908. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 2476. Error: 6. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 1332. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 4196. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 4220. Error: 6. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 268. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 4324. Error: 6. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 5960. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 INFO]  [processMonitor, 147] Found a running process 6120 with name java.exe
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 INFO]  [processMonitor, 154] Reusing existing process 6120
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 6128. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 6084. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2284 WARN]  [processMonitor, 136] Failed to get the module name for process 6092. Error: 299. Ignoring the process
[2012-09-23 18:09:12:860 'ProcessMonitor' 2796 INFO]  [processMonitor, 245] Process monitoring started
[2012-09-23 18:09:13:063 'SessionMgr' 2284 INFO]  [sessionMgr, 80] GetSessionLocale: Initialized server locale object
[2012-09-23 18:09:13:063 'InternalScheduledTasksMgr' 2284 INFO]  [internalScheduledTasksMgr, 103] Internal Scheduled Task Manager created...
[2012-09-23 18:09:13:063 'EmailAlertMgr' 2284 INFO]  [emailAlertMgr, 278] Email alert manager created...
[2012-09-23 18:09:13:063 'ConfigurationMgr' 2284 INFO]  [configurationMgr, 152] Configuration manager created...
[2012-09-23 18:09:13:063 'EntityLockingMgr' 2284 INFO]  [entityLockingMgr, 62] Entity locking manager created...
[2012-09-23 18:09:13:063 'vaCrypto' 2284 INFO]  [vaCryptoSupport, 262] vaCrypto Initializing....
[2012-09-23 18:09:13:063 'vaCrypto' 2284 INFO]  [vaCryptoSupport, 243] Loaded VALM key E:\Program Files (x86)\VMware\Infrastructure\Update Manager\ssl\valm.key
[2012-09-23 18:09:13:063 'HealthServiceMgr' 2284 INFO]  [healthServiceMgr, 102] Health service manager created...
[2012-09-23 18:09:13:063 'TaskStatsCollector' 2284 INFO]  [taskStatsCollector, 74] Task statistics collector created...
[2012-09-23 18:09:13:063 'Activation.trace' 2284 INFO]  [activationValidator, 1263] Trace objects loaded.
[2012-09-23 18:09:13:079 'VcIntegrityPlugin' 2284 INFO]  [plugin, 252] VcIntegrityPlugin Init
[2012-09-23 18:09:13:079 'VcIntegrityPlugin' 2284 INFO]  [plugin, 282] Add callback to Ufa Shutdown manager.
[2012-09-23 18:09:13:079 'VcIntegrity' 2284 INFO]  [vcIntegrity, 809] Initializing database

client_ip -  -  [23/Sep/2012:20:46:31 +0000] "GET /vci/downloads/VMware-UMClient.exe HTTP/1.1" 200 16340304 "-" "-"

server_ip -  -  [23/Sep/2012:20:56:57 +0000] "GET /vci/downloads/health.xml HTTP/1.1" 404 1292 "-" "Jakarta Commons-HttpClient/3.1"

I have had so many problems on fresh installation of vSphere 5.1 (5.0 can be a hassle at times... but 5.1 is totally pita).Nothing in vCenter 5 didn't throw a fatal error after a fresh installation....
I am thinking about switching to something else since I no longer have a Windows only environment.... VMware KBs are so poorly written...
Reply
0 Kudos
16 Replies
ramkrishna1
Enthusiast
Enthusiast

Hi realdreams,

it seems most probably hardware problem or due to some hotfix & application or antivirus creating problem .

"concentrate the mind on the present moment."
Reply
0 Kudos
ftoppi
Contributor
Contributor

Hi,

I have the exact same problem, fresh install of vCenter & Update manager service won't start. It seems to hang somewhere because there's a java 32bit process which opens the default ports (9084 and 9087) and I can connect to it, download the plugin but that's all.

No antivirus on the server and it's up to date with Windows update. SQL Server 2012 is installed on a separate Windows server and the ODBC 32bit connection is OK (database tables created successfully).

Reply
0 Kudos
ftoppi
Contributor
Contributor

Hi again,

I solved my problem by using SQL Native client version 10 (SQL Server 2008) instead of version 11 (SQL Server 2012).

Cheers.

Reply
0 Kudos
MrBaba
Enthusiast
Enthusiast

Got the same, try to use SQL Native Client 11 or 10, same issue.

Regards,

Reply
0 Kudos
aka_MAC
Contributor
Contributor

Any thoughts? Have the same issue. Native client version 10 hasn't solve the problem.

Reply
0 Kudos
MrBaba
Enthusiast
Enthusiast

Fixed it (for my part)

Need to check DNS and reverse DNS for vCenter and use FQDN instead of the IP adress during VUM installation. After that it works fine with 10.0 or 11.0 client

Reply
0 Kudos
aka_MAC
Contributor
Contributor

Used FQDN from the start. Both A and PTR records exists in DNS. VUM service still doesn't start.

Reply
0 Kudos
hodo
Contributor
Contributor

I've tried all the solutions mentioned so far (SQL client versions, IP vs hostname, verify DNS) and I still have the same issue. UM installs without a problem but the service fails to start every time and there is no indication in any logs on what is causing the problem.

Reply
0 Kudos
Sreejesh_D
Virtuoso
Virtuoso

whats the SQL express version you are connecting ? VUM 5.1 or 5.1 update 1 supports only the following express edition.

Microsoft SQL Server 2008 Express (R2 SP1) - 64-bit

Reply
0 Kudos
aka_MAC
Contributor
Contributor

Ended up with installing 5.1U1 on Server 2012. It works.

Reply
0 Kudos
stephenrbarry
Enthusiast
Enthusiast

I'm having the same issue on 5.1U1, Server 2012, and SQL 2012.  VUM worked fine for the first day or so, but when I logged into the server today I started getting connectivity errors.  Restarting the server didn't help either.  Anyone find a fix for it?

Reply
0 Kudos
realdreams
Enthusiast
Enthusiast

The fix is to ditch vmware products.... I moved to vCSA without VUM. My experience with vmware is that any maintenance will be a nightmare... I would rather spend the time on something productive and leave vmware as broken as it is until i migrate to another solution...

Reply
0 Kudos
realdreams
Enthusiast
Enthusiast

The fix is to ditch vmware products.... I moved to vCSA without VUM. My experience with vmware is that any maintenance will be a nightmare... I would rather spend the time on something productive and leave vmware as broken as it is until i migrate to another solution...

Reply
0 Kudos
realdreams
Enthusiast
Enthusiast

The fix is to ditch vmware products.... I moved to vCSA without VUM. My experience with vmware is that any maintenance will be a nightmare... I would rather spend the time on something productive and leave vmware as broken as it is until i migrate to another solution...

Reply
0 Kudos
OscarDavey
Hot Shot
Hot Shot

Hello,

Try to read and use this article (Installing and Administering VMware vSphere Update Manager).

Hope will help.

VMware vSphere 5.1

Reply
0 Kudos
chay2263
Enthusiast
Enthusiast

Was there ever a resolution to this. I'm using update manager 5.5 and getting the same error even after a fresh reinstall of it. Originally, before the upgrade to 5.5 everything was working fine, but now its not. I even checked and somehow my DSN got removed :smileyplain: so I added it back and got the services to start but when I scan a host the service stops again. I can scan VMs and templates and it works fine.

Chestin Hay vExpert;VCIX6-NV,VCP6-DCV;VCP6-NV,VCP6-CMA https://www.letsv4real.com https://www.twitter.com/letsv4real
Reply
0 Kudos