Error: "Fault Module: ntdll.dll" when starting vCenter Server
Article ID: 324860
Updated On:
Products
VMware vCenter Server
Issue/Introduction
Increase the value of the ThreadStackSizeKb parameter to 1024 KB in the vpxd.cfg file to resolve this issue.
Symptoms:
- vCenter Server 5.5 or 6.0 fails immediately after starting
- The virtual machine guest operating system may fail with a blue diagnostic screen.
- In the Windows Event Viewer, under application, you see these events:
Windows Event:
Problem signature:
Problem Event Name: APPCRASH
Application Name: vpxd.exe
Application Version: 5.5.0.40799
Application Timestamp: 5307e9e2
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.18247
Fault Module Timestamp: 521eaf24
Exception Code: c0000005
Exception Offset: 0000000000018e5d
Log Name: Application
Source: Application Error
Date: 8/13/2015 8:20:40 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: vCenter_Server
Description:
Faulting application name: vpxd.exe, version: 0.0.0.0, time stamp: 0x55690394
Faulting module name: ntdll.dll, version: 6.3.9600.17936, time stamp: 0x55a68e0c
- In the C:\ProgramData\VMware\VMware VirtualCenter\Logs\vpxd-xx.log file, you see backtraces similar to:
[03364 info 'commonvpxLro' opID=e151ddc] [VpxLRO] -- BEGIN task-1031903 -- group-n23745 -- vim.ManagedEntity.rename -- b1131b40-7387-987a-d231-7a37f6dcc034(527b559e-a31f-c01c-16e0-3d864538a3fd)
<YYYY-MM-DD>T<time> [03364 error 'Default' opID=e151ddc] Alert:VpxTLS::GetTLS()->GetMoLockXCount() == 0@ d:/build/ob/bora-1623101/bora/vpx/common/vpxLro.cpp:3275
--> Backtrace:
--> backtrace[00] rip 000000018018b6aa
--> backtrace[01] rip 0000000180105288
--> backtrace[02] rip 000000018010668e
--> backtrace[03] rip 000000018009c567
--> backtrace[04] rip 0000000140674295
--> backtrace[05] rip 0000000140a73519
--> backtrace[06] rip 0000000000912a27
--> backtrace[07] rip 00000000004d980c
--> backtrace[08] rip 000000014069d366
--> backtrace[09] rip 00000001406757bf
--> backtrace[10] rip 0000000140679174
--> backtrace[11] rip 0000000140687874
--> backtrace[12] rip 00000001406902f5
--> backtrace[13] rip 0000000180153334</time>
- Running the vpxd -s from a command prompt displays an output similar to:
<YYYY-MM-DD>T<time> [02976 warning 'utilvpxdDbLoad'] [ORM] Load: Missi<YYYY-MM-DD>T<time> </time>
ng mapping for property hardware.device.backing.backingObjectId
<YYYY-MM-DD>T<time>[02976 warning 'utilvpxdDbLoad'] [ORM] Non-optiona
l property startConnected set
<YYYY-MM-DD>T<time> [02976 warning 'utilvpxdDbLoad'] [ORM] Non-optiona
l property allowGuestControl set
<YYYY-MM-DD>T<time> [02976 warning 'utilvpxdDbLoad'] [ORM] Non-optiona
l property connected set
<YYYY-MM-DD>T<time> [02976 warning 'utilvpxdDbLoad'] [ORM] Load: Missi
ng mapping for property hardware.device.capacityInBytes
<YYYY-MM-DD>T<time> [02976 warning 'utilvpxdDbLoad'] [ORM] Load: Missi
ng mapping for property hardware.device.storageIOAllocation.reservation
<YYYY-MM-DD>T<time> [02976 warning 'utilvpxdDbLoad'] [ORM] Load: Missi
ng mapping for property hardware.device.diskObjectId
<YYYY-MM-DD>T<time>[02976 warning 'utilvpxdDbLoad'] [ORM] Load: Missi
ng mapping for property hardware.device.vFlashCacheConfigInfo.vFlashModule
<YYYY-MM-DD>T<time> [02976 warning 'utilvpxdDbLoad'] [ORM] Load: Missi
ng mapping for property hardware.device.vFlashCacheConfigInfo.reservationInMB
<YYYY-MM-DD>T<time> [02976 warning 'utilvpxdDbLoad'] [ORM] Load: Missi
ng mapping for property hardware.device.vFlashCacheConfigInfo.cacheConsistencyTy
pe
</time></time></time></time></time></time></time></time></time></time>[07044 verbose 'Proxy Req 00354'] Connected to nam
ed pipe \\.\pipe\vmware-vpxd-qsadapter-pipe
<YYYY-MM-DD>T<time> [02716 verbose 'vpxdvpxdHostCnx' opID=SWI-3a8447f0
] [VpxdHostCnx::SetLastHeartbeat] Could not set last heartbeat due to unset cnxM
apPath: /appdata/VMware/vpxd/hostCnx/cnxMap/#5236ab0f-acff-96d3-0b9d-1fa26b1f1d9
d/
<YYYY-MM-DD>T<time> [05888 verbose 'QsAdapter.HTTPService.HttpConnecti
on'] User agent is 'VMware vim-java 1.0'
<YYYY-MM-DD>T<time> [04112 verbose 'QsAdapter.HTTPService'] HTTP Respo
nse: Complete (processed 0 bytes)
<YYYY-MM-DD>T<time> [05888 verbose 'Proxy Req 00354'] Server named pip
e \\.\pipe\vmware-vpxd-qsadapter-pipe disconnected
<YYYY-MM-DD>T<time>[05888 verbose 'QsAdapter.HTTPService.HttpConnecti
on'] User agent is 'VMware vim-java 1.0'
<YYYY-MM-DD>T<time> [07044 verbose 'QsAdapter.HTTPService'] HTTP Respo
nse: Complete (processed 0 bytes)
<YYYY-MM-DD>T<time> [05888 verbose 'Proxy Req 00342'] The client close
</time></time></time></time></time></time></time>d the stream, not unexpectedly.
Environment
VMware vCenter Server 5.5.x
VMware vCenter Server 6.0.x
VMware vCenter Server 6.0.x
Cause
This issue occurs because the default value of the ThreadStackSizeKb parameter (512 KB) is insufficient.
Resolution
To resolve this issue, increase the value of the ThreadStackSizeKb parameter to 1024 KB within the vpxd.cfg file and then restart the vCenter Server services.
To increase the value of the ThreadStackSizeKb parameter:
- Open the vpxd.cfg file using a text editor.
The vpxd.cfg file is located at:
In vCenter Server 5.5: C:\ProgramData\VMware\VMware VirtualCenter\
In vCenter Server 6.0: C:\ProgramData\VMware\vCenterServer\cfg\vmware-vpx\
- Locate the ThreadStackSizeKb parameter within the file. For example, the parameter appears similar to:
Note: Entries within the vpxd.cfg file are case sensitive.
<Config>
<vmacore>
<threadPool>
<ThreadStackSizeKb>512</ThreadStackSizeKb>
</threadPool>
</vmacore>
</Config>
Note: If the entry does not exist, it will need to be added.
- Set the value of the ThreadStackSizeKb parameter to 1024. For example:
Note: Entries within the vpxd.cfg file are case sensitive.
<Config>
<vmacore>
<threadPool>
<ThreadStackSizeKb>1024</ThreadStackSizeKb>
</threadPool>
</vmacore>
</Config>
Note: If the service still fails increase the value to 2048.
- Save and close the file.
Additional Information
Feedback
Yes
No
Powered by
