VirtualCenter Service To Core Dump With vRangerPro4

[pironet]

Hi Guru's

Just wanted to let you know about what looks like a severe bug in vRangerPro4 version 4.0.0.10476 which prevents VMware VirtualCenter service (version 2.5U3 build 119598) to start an to 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:

backtrace[00|http://communities.vmware.com/community-document-picker.jspa?communityID=&subject=00] eip 0x0128e8b6 ?GenerateCoreDump@System@Vmacore@@YAXXZ

backtrace[01|http://communities.vmware.com/community-document-picker.jspa?communityID=&subject=01] eip 0x011d6d3a ?CreateBacktrace@SystemFactoryImpl@System@Vmacore@@UAEXAAV?$Ref@VBacktrace@System@Vmacore@@@3@@Z

backtrace[02|http://communities.vmware.com/community-document-picker.jspa?communityID=&subject=02] eip 0x011aff6e ??0Throwable@Vmacore@@QAE@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z

backtrace[03|http://communities.vmware.com/community-document-picker.jspa?communityID=&subject=03] eip 0x011b0647 ?PanicExit@Vmacore@@YAXABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z

backtrace[04|http://communities.vmware.com/community-document-picker.jspa?communityID=&subject=04] 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 thru your VI Client you can start RangerPro4' services again.

Does anyone know anything about this problem?

Rgds,

Didier

P.S. This post refers to a similar issue http://communities.vmware.com/message/1327025#1327025

[pironet]

Hi,

Jason Mattox at Vizioncore pointed us out to a this KB:

He posted this message at laez.nl

"We are working very diligently to get this fix in the hands of our users, we have a fix that already out of our development process and is now in the hands of our QA team. You can also reference the following Knowledgebase article here and search for KB 00000296 about this issue. This KB will also be updated shortly for a root cause once the issue is fully cleared by development and QA, for those that are interested in the technical details about the issue. Thanks again for everyone's support! And we hope to get everyone taken care of very soon!"

Cheers,

Didier