I have a problem with a vCenter server that are not able to start up. The problem occured after the power was unplugged without shutting down the server first (it does not run as a virtual machine). I haven't been able to find any solution to this in the Community.
The output from trying to start the service is available here:
C:\Program Files\VMware\Infrastructure\VirtualCenter Server>vpxd -s [2011-10-17 10:08:04.858 03076 info 'App'] Current working directory: C:\Program Files\VMware\Infrastructure\VirtualCenter Server [2011-10-17 10:08:04.858 03076 info 'App'] Log path: C:\ProgramData\VMware\VMware VirtualCenter\Logs [2011-10-17 10:08:04.859 03076 info 'App'] Initializing SSL [2011-10-17 10:08:04.860 03076 info 'Libs'] Using system libcrypto, version 9080CF [2011-10-17 10:08:05.982 03076 info 'App'] Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000 [2011-10-17 10:08:05.984 03076 warning 'Libs'] W32Util_RegisterEventLog: Could not open registry key. Error 0. [2011-10-17 10:08:05.985 03076 warning 'Libs'] Failed to initialize event source for VMware VirtualCenter Server. [2011-10-17 10:08:09.271 03076 info 'App'] CoreDump: Writing minidump [2011-10-17 10:08:09.419 03076 panic 'App'] Panic: Failed to do early initialization. Backtrace: backtrace[00] rip 000000018010a1aa Vmacore::System::Stacktrace::CaptureWork backtrace[01] rip 00000001800e8018 Vmacore::System::SystemFactoryImpl::CreateFileWriter backtrace[02] rip 00000001800e850e Vmacore::System::SystemFactoryImpl::CreateQuickBacktrace backtrace[03] rip 0000000180129205 Vmacore::PanicExit backtrace[04] rip 0000000180129311 Vmacore::PanicExit backtrace[05] rip 00000001800ac0b4 Vmacore::Vpanic backtrace[06] rip 00000001402c5f23 (no symbol) backtrace[07] rip 000000013f8ebc58 (no symbol) backtrace[08] rip 000000013f8ec0c4 (no symbol) backtrace[09] rip 000000013f8eadf2 (no symbol) backtrace[10] rip 00000000771ff56d BaseThreadInitThunk backtrace[11] rip 0000000077433281 RtlUserThreadStart [2011-10-17 10:08:09.469 03076 panic 'App'] Failed to do early initialization. |
The only thing I can think of trying now will be reinstalling vCenter.
Just a note on the version of vCenter I'm running:
C:\Program Files\VMware\Infrastructure\VirtualCenter Server>vpxd -version VMware VirtualCenter 4.1.0 build-258902 |
I ended up reinstalling vCenter but kept the database and everything worked with any additional setup or configuration.