VMware Cloud Community
NZSolly
Contributor
Contributor

vSphere vCenter 4.0 - service wont start

Hi all, I have vsphere vcenter running for a 3 wks now, all appears okay, except it wont start now after some updates over the weekend....I install wsus on the is physical box last week, but didnt have any issues after rebooting etc....it just decided this morning to refuse to start after some windows powershell updates.

any ideas, the host are running okay, and i used client check if they are still licensed etc, appear okay, but would like my vc back!!

Event Type: Error

Event Source: VMware VirtualCenter Server

Event Category: None

Event ID: 1000

Date: 7/09/2009

Time: 9:53:52 a.m.

User: N/A

Computer: NZNPEVCMS01

Description:

The description for Event ID ( 1000 ) in Source ( VMware VirtualCenter Server ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Failed to intialize VMware VirtualCenter. Shutting down....

Reply
0 Kudos
4 Replies
Troy_Clavell
Immortal
Immortal

here are a couple things worth looking into

http://kb.vmware.com/kb/1003926

http://kb.vmware.com/kb/1007669

NZSolly
Contributor
Contributor

Hi, thanks for the links.....i try all of the points raised on the 1st link, my wsus is on 8530, so not interferring and both were working in the 1st few days.

The only point i see a failure on is that I am using sql 2005 express with windows authentication instead of sql....is there a solution to change this?

Update...I stopped IISadmin, and got VC service to start!!...even though I have wsus configured for 8530, their must be some ports that are being used by IIS & VC, any ideas if I can change the VC ports etc?

Reply
0 Kudos
fejf
Expert
Expert

It may be possible that WSUS runs on a non-80 or non-443 port but IIS is still blocking one of them. Use "netstat -anob | more" to see if there's a service listed which uses port 80, 443 or 902-904. If that still doesn't help you need to provide your vpxd.log file (or open a support request and provide them the logfile), because the event viewer doesn't give you much info about what's really happening when dealing with vmware.

--

There are 10 types of people. Those who understand binary and the rest. And those who understand gray-code.

-- There are 10 types of people. Those who understand binary and the rest. And those who understand gray-code.
Reply
0 Kudos
NZSolly
Contributor
Contributor

Hey thats a great command, sh*t load of stuff....though cant find anything else now that uses 80 or 443 other than vpxd.exe......looks like I might have to start wsus\iis\www & http as manual start ups for awhile, I know you can do delayed service start with 2008, might have to look at that!

thanks

Reply
0 Kudos