VMware Cloud Community
LB1
Contributor
Contributor

VC 2.5 crashing with Faulting application vcpSysPerf.exe

I cannot keep Virtualcenter running for any long period of time after I tried to add about 100 systems to the capacity planner and analyze them over the course of a couple weeks.

I noticed that when I started, and after I returned to it 2 weeks later, that most systems were still hung at "Collecting System Info", and a few at "Preparing for Anaysis".

I have to constantly restart VirtualCenter Server Service to get connected to it even though its running, after I get the VCP service hanging like so:

Event Type: Error

Event Source: Application Error

Event Category: (100)

Event ID: 1000

Date: 1/3/2008

Time: 7:32:44 AM

User: N/A

Computer: USALPVC01

Description:

Faulting application vcpSysPerf.exe, version 2.6.0.335, faulting module oleaut32.dll, version 5.2.3790.2955, fault address 0x00032a33.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 41 70 70 6c 69 63 61 74 Applicat

0008: 69 6f 6e 20 46 61 69 6c ion Fail

0010: 75 72 65 20 20 76 63 70 ure vcp

0018: 53 79 73 50 65 72 66 2e SysPerf.

0020: 65 78 65 20 32 2e 36 2e exe 2.6.

0028: 30 2e 33 33 35 20 69 6e 0.335 in

0030: 20 6f 6c 65 61 75 74 33 oleaut3

0038: 32 2e 64 6c 6c 20 35 2e 2.dll 5.

0040: 32 2e 33 37 39 30 2e 32 2.3790.2

0048: 39 35 35 20 61 74 20 6f 955 at o

0050: 66 66 73 65 74 20 30 30 ffset 00

0058: 30 33 32 61 33 33 032a33

==================================================

Any thoughts?

0 Kudos
4 Replies
xe
Enthusiast
Enthusiast

Please apply this hotfix:

http://support.microsoft.com/kb/909139/en-us

or upgrade to Service Pack 2.

0 Kudos
willrodbard
VMware Employee
VMware Employee

Hi,

Unfortunately I am also geting these erros but I am running on a W2K3 SP2 server so the hotfix cannot be applied.

Any ideas? Smiley Happy

Cheers

Will.

0 Kudos
xe
Enthusiast
Enthusiast

Can you post your event log data for the crash please?

0 Kudos
TSCinc
Contributor
Contributor

We also have SP2 and are getting this exact error -

Has anyone determined a cause/fix yet?

Thanks, Jim

0 Kudos