Just wanted to let you know about what looks like a severe bug in vRangerPro4 version 188.8.131.5276 which prevents VMware VirtualCenter service (version 2.5U3 build 119598) to start and the service does a core dump.
N.B. I have the problem with those versions stated above. I have not tested any other versions of both products here.
The vpxd.exe process just coredump and you can see something similar to this in the vpxd logs:
–2009-08-19 17:52:54.852 ‘App’ 4840 error– Backtrace:
backtrace00 eip 0x0128e8b6 ?GenerateCoreDump@System@Vmacore@@YAXXZ
backtrace01 eip 0x011d6d3a ?CreateBacktrace@SystemFactoryImpl@System@Vmacore@@UAEXAAV?$Ref@VBacktrace@System@Vmacore@@@3@@Z
backtrace02 eip 0x011aff6e ??0Throwable@Vmacore@@QAE@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z
backtrace03 eip 0x011b0647 ?PanicExit@Vmacore@@YAXABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z
backtrace04 eip 0x01292f27 ?GetThisThread@System@Vmacore@@YAPAVThread@12@XZ
–2009-08-19 17:52:54.852 ‘App’ 4840 info– CoreDump: Writing minidump to C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs\vpxd-1004-4840.dmp
Basically you have to stop all vRangerPro4 services prior a restart of VMware VirtualCenter service. Once started and you can connect through your VI Client you can start RangerPro4′ services again.
Does anyone know anything about this problem?
N.B. Thx to Jason Mattox at Vizioncore to point us out to a KB related to this issue.