We're running vCenter 4.0.0.10021 with SQL Server 2005 on Windows Server 2003 Enterprise Edition. It was working fine until today, but at some point today, we were no longer able to connect using the vSphere Client. On examining the system, we found that the VMWare VirtualCenter Server service is stopped, and it crashes again whenever we start it. Rebooting the system doesn't help.
The System event log shows a large number of events like the following: "The VMware VirtualCenter Server service terminated unexpectedly. It has done this 36 time(s). The following corrective action will be taken in 300000 milliseconds: Restart the service."
After each restart attempt, the Application event log shows two informational events from the VMware VirtualCenter Server. The first event is "Starting VMware VirtualCenter 4.0.0 build-208111." The second event is "Log directory: E:\Documents and Settings\Default User\Local Settings\Application Data\VMware\vpx." The VMware logs are actually in a slightly different folder than stated in this message. They are in E:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs.
Some errors are scattered through the most recent log file, vpxd-190.log, with the most serious-seeming ones toward the end. I attach the log, but below are a sample of the error messages:
Ignoring unknown entry from DB: VirtualCenter.VMotionEncryption
detected IP conflict between vm (moId:vm-1068) nic:GuestInfo.net[0].ipAddress[0] and entity (moId:vm-906)
Failed to add LDAP entry cn=0N60N-4AJ8L-48833-080UK-2XQKJ,ou=Licenses,ou=Licensing,dc=virtualcenter,dc=vmware,dc=int: 0x44 (The object already exists.)
Update for property timestamp failed
Invalid guest IP address for VM VMware Studio: fe80::250:56ff:fe84:2cc2
Invalid guest IP address for VM RedHatEnterprise_5.2_x86: fe80::250:56ff:fe84:423c
Win32 exception: Access Violation (0xc0000005)
Read (0) at address 0x000018
eip: 0x264cd78 esp: 0x4aae8f8 ebp: 0x4aae904
eax: 0x4aae918 ebx: 0x5ab2f78 ecx: 00000000 edx: 0x5d67a68 edi: 00000000 esi: 0x5ab2f78
Panic: Win32 exception
Backtrace:
backtrace[00] eip 0x01a1c8a0 ?AbortProcess@System@Vmacore@@YAXXZ
backtrace[01] eip 0x01a1d027 ?CreateBacktrace@SystemFactoryImpl@System@Vmacore@@UAEXAAV?$Ref@VBacktrace@System@Vmacore@@@3@@Z
backtrace[02] eip 0x0195fa53 ?PanicExit@Vmacore@@YAXABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z
backtrace[03] eip 0x01a2c7c6 ?GetThisThread@System@Vmacore@@YAPAVThread@12@XZ
backtrace[04] eip 0x78158c0e __CxxLongjmpUnwind
backtrace[05] eip 0x78158576 __CxxExceptionFilter
backtrace[06] eip 0x7815894b __CxxExceptionFilter
backtrace[07] eip 0x78158a57 __CxxExceptionFilter
backtrace[08] eip 0x78158b11 __CxxFrameHandler3
backtrace[09] eip 0x7c828772 RtlRaiseStatus
The log folder also includes a vpxd-54.dmp which I assume is a dump.
Recently, I've been experimenting with vApps, which is something we hadn't used before. Shortly before vCenter stopped working today, I had started a couple of VMs that belonged to a vApp. One of these VMs was running RedHat, so perhaps the error "Invalid guest IP address for VM RedHatEnterprise_5.2_x86" is what started this problem.
Is there some way to work around this problem so we can get vCenter working again? Thanks for any suggestions.
