Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

Search the VMware Knowledge Base (KB)

View by Article ID

The VirtualCenter Server service fails during initialization with the error: Win32 exception (1027666)

Symptoms

The VirtualCenter Server service fails on startup during the initialization of the service
The vpxd.log file contains an access violation similar to:

[<date><time> 'App' 4132 error] Win32 exception: Access Violation (0xc0000005)
[<date><time> 'App' 4132 error] Write (1) at address 0x000094
[<date><time> 'App' 4132 error] eip: 0x17669fb esp: 0x9c7f680 ebp: 0x9c7f680
[<date><time> 'App' 4132 error] eax: 0x9c7f694 ebx: 00000000 ecx: 00000000 edx: 0x9c7f601 edi: 0xaecee9c esi: 0x9c7f730

[<date><time> 'App' 4132 error]

Exception: Win32 exception

[<date><time> 'App' 4132 error] Backtrace:
backtrace[00] eip 0x0128edf6 ?GenerateCoreDump@System@Vmacore@@YAXXZ
backtrace[01] eip 0x011d6d3a ?CreateBacktrace@SystemFactoryImpl@System@Vmacore@@UAEXAAV?$Ref@VBacktrace@System@Vmacore@@@3@@Z
backtrace[02] eip 0x011b185e ??0Throwable@Vmacore@@QAE@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z
backtrace[03] eip 0x011afe77 ?PanicExit@Vmacore@@YAXABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z
backtrace[04] eip 0x01293487 ?GetThisThread@System@Vmacore@@YAPAVThread@12@XZ
backtrace[05] eip 0x7c359c97 __CxxLongjmpUnwind
backtrace[06] eip 0x7c359629 __CxxExceptionFilter
backtrace[07] eip 0x7c3598ad __CxxExceptionFilter
backtrace[08] eip 0x7c35994a __CxxExceptionFilter
backtrace[09] eip 0x7c359b9d __CxxFrameHandler
backtrace[10] eip 0x7c828772 RtlRaiseStatus
backtrace[11] eip 0x7c828743 RtlRaiseStatus
backtrace[12] eip 0x7c82857e KiUserExceptionDispatcher
backtrace[13] eip 0x0092e793 (no symbol)
backtrace[14] eip 0x018c9a39 ??1ByUsername@EventFilterSpec@Event@Vim@@UAE@XZ
backtrace[15] eip 0x013c3d99 ?_GetType@MoRef@Vmomi@@UBEPAVType@2@XZ
backtrace[16] eip 0x013e6be6 ?_RecordPropertyChange@PropertyProviderMixin@Vmomi@@QAE_NABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAVAny@2@1@Z
backtrace[17] eip 0x013e7dae ?_GetChanges@PropertyProviderMixin@Vmomi@@UAE_J_JABVPropertySet@2@_NAAV?$Ref@V?$DataArray@VChange@PropertyCollector@Core@Vmomi@@
@Vmomi@@@Vmacore@@AAV?$Ref@V?$DataArray@VMissingProperty@PropertyCollector@Core@Vmomi@@@Vmomi@@@5@@Z
backtrace[18] eip 0x01407ba8 ?GetPropCollectorLogger@Vmomi@@YAPAVLogger@Service@Vmacore@@XZ
backtrace[19] eip 0x0140ac37 ?GetPropCollectorLogger@Vmomi@@YAPAVLogger@Service@Vmacore@@XZ
backtrace[20] eip 0x0140b6ac ?GetPropCollectorLogger@Vmomi@@YAPAVLogger@Service@Vmacore@@XZ
backtrace[21] eip 0x0140c03c ?GetPropCollectorLogger@Vmomi@@YAPAVLogger@Service@Vmacore@@XZ
backtrace[22] eip 0x0140c69f ?GetPropCollectorLogger@Vmomi@@YAPAVLogger@Service@Vmacore@@XZ
backtrace[23] eip 0x0129699a ?IsEnlisted@System@Vmacore@@YA_NXZ
backtrace[24] eip 0x012972ec ?IsEnlisted@System@Vmacore@@YA_NXZ
backtrace[25] eip 0x01292b0e ?GetThreadId@System@Vmacore@@YA_JXZ
backtrace[26] eip 0x7c349565 _endthreadex
backtrace[27] eip 0x77e6482f GetModuleHandleA

Resolution

This issue can occur when third party agents (such as Xen Desktop) are connected and communicating to vCenter Server when the service is initializing.

This issue is resolved in vCenter Server 2.5 Update 6 and later. You can download vCenter Server 2.5 Update 6 from the Virtual Infrastructure Download Center.

If you cannot upgrade, you can work around this issue by shutting down third party services that are connecting to vCenter Server before starting the service. When the VirtualCenter Server service is started, restart the third party services.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

1 2 3 4 5
2 Ratings

1 2 3 4 5
2 Ratings

Actions

Bookmark Document

KB:

Did this article help you?
This article resolved my issue. This article did not resolve my issue. This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)