I have been unable to start my previously functioning vCenter service for a while. I had not run any updates or anything, it just seemed to stop working one day.
All services start except the VirtualCenter Server service itself. I have narrowed it down to what seems to be a problem with the heartbeat in the vpxd.log (excerpt):
[2011-01-19 16:36:25.204 03160 error 'Heartbeat'] Failed to wait for heartbeat socket: 10038
[2011-01-19 16:36:25.204 03160 warning 'Libs'] ASSERT d:/build/ob/bora-258672/bora/vpx/vpxd/vpxdHeartbeat.cpp:283
[2011-01-19 16:36:25.204 03160 info 'App'] Initiating VMware VirtualCenter shutdown
A netstat -na indicates that port 10038 is not open on the system, meaning it shouldn't be conflicting with any other service that might be trying to use that port.
I have tried:
System is running Windows XP SP3 with all patches applied.
I'm attaching my vpxd.log and netstat output.
Couldn't find anyone on Google with this problem, so hopefully someone has some insight.
Thanks in advance.
Yes, 32 bit.
XP because I had licenses for it and it was on the comaptibility list (on page 18 of your link). I understand that 4.1 is not compatible with XP, but I have not upgraded to it yet.
It worked for about a year before I started having this trouble.
I do run SQL Express 2005, but I know of the issue you speak of and I set up the VMware services to wait for SQL Server to start before starting.
Regardless, I have also tried stopping and starting the services manually in the correct order, and still doesn't work.
It seems as though there is no solution to this problem outside of a full wipe and re-install, probably on a Server based OS now that 4.1 isn't supported on XP.
Does anyone know if it is difficult to un-register ESXi nodes from the old, now non-existant vCenter server and join them to the new vCenter installation? Any gotchas I should watch out for?