vCenter Server 6.0 Update 3 or 6.5 fails with the error: Panic: Win32 exception: Access Violation (0xc0000005)
search cancel

vCenter Server 6.0 Update 3 or 6.5 fails with the error: Panic: Win32 exception: Access Violation (0xc0000005)

book

Article ID: 317562

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
  • vCenter Server 6.0 U3 or 6.5 fails.
  • In the C:\ProgramData\VMware\vCenterServer\logs\vmware-vpx\vpxd.log file, you see HealthCheck::LoadHealthCheckResultFromDB followed by these entries:

    2017-05-07T19:04:20.793+02:00 error vpxd[06628] [Originator@6876 sub=Default opID=SendFdmUpdates-70ff5a04] [VdbStatement] SQLError was thrown: "ODBC error: (HY000)
    [Microsoft][SQL Server Native Client 11.0]Connection is busy with results for another command" is returned when executing SQL statement "select TRUNKED_FLG, VLAN_ID_START, VLAN_ID_END from VPX_DVHOST_HC_VLAN_RESULT where DVS_ID = ? and HOST_ID = ? and UPLINK_PORT_KEY = ?"

    2017-05-07T19:04:20.850+02:00 error vpxd[06628] [Originator@6876 sub=dbQuery opID=SendFdmUpdates-70ff5a04] [HealthCheck::LoadHealthCheckResultFromDB] database error [LoadHealthCheckResultFromDB]: "ODBC error: (HY000) - [Microsoft][SQL Server Native Client 11.0]Connection is busy with results for another command" is returned when executing SQL statement "select TRUNKED_FLG, VLAN_ID_START, VLAN_ID_END from VPX_DVHOST_HC_VLAN_RESULT where DVS_ID = ? and HOST_ID = ? and UPLINK_PORT_KEY = ?"
    ...
    2017-05-07T19:07:46.318+02:00 info vpxd[07408] [Originator@6876 sub=vpxLro opID=task-internal-1-4ffb0fc3-c3] [VpxLRO] -- BEGIN task-internal-1515 -- domain-c83098 -- AskRefreshDrmRecLro --
    2017-05-07T19:13:50.203+02:00 info vpxd[07408] [Originator@6876 sub=Default opID=task-internal-1-4ffb0fc3-c3] CoreDump: Writing minidump
    2017-05-07T19:13:54.589+02:00 panic vpxd[07408] [Originator@6876 sub=Default opID=task-internal-1-4ffb0fc3-c3]
    -->
    --> Panic: Win32 exception: Access Violation (0xc0000005)
    }


    Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.


Cause

This issue occurs due to Microsoft SQL databases not supporting shared connections.

Resolution

Additional Information