"Invalid Descriptor Index" for SQL table VPX_HCI_CONFIG_INFO.LOCKDOWN_MODE - vCenter Service 'vpxd' crashes during install/upgrade to vCenter Server 6.7 U1
search cancel

"Invalid Descriptor Index" for SQL table VPX_HCI_CONFIG_INFO.LOCKDOWN_MODE - vCenter Service 'vpxd' crashes during install/upgrade to vCenter Server 6.7 U1

book

Article ID: 301852

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Symptoms:
  • vCenter Server service crashes and fail to start with Invalid Descriptor Index in VPX_HCI_CONFIG_INFO.LOCKDOWN_MODE
  • vCenter Server service crash with "Invalid Descriptor Index" for VPX_HCI_CONFIG_INFO.LOCKDOWN_MODE after upgrading to vSphere 6.7 Update 1
  • In vpxd.log file, you see entries similar to:
2018-11-06T12:59:56.752-05:00 verbose vpxd[08228] [Originator@6876 sub=Default] [VdbStatement]Executing SQL: SELECT CLUSTER_ID, LOCKDOWN_MODE, DATETIME_CONFIG, HCI_WORKFLOW_STATE, CONFIGURED_HOSTS, MIN_ESX_VERSION FROM VPX_HCI_CONFIG_INFO WHERE CLUSTER_ID = ?
2018-11-06T12:59:56.753-05:00 error vpxd[08228] [Originator@6876 sub=Default] [VdbStatement::ResultValue:GetValue] Error to get value at pos: 1, ctype: 4 for SQL "VPX_HCI_CONFIG_INFO.LOCKDOWN_MODE"
2018-11-06T12:59:56.753-05:00 verbose vpxd[08228] [Originator@6876 sub=Default] [VdbODBCError::VdbODBCError] SQLGetDiagRec SQLState='07009' NativeError=0 MessageText='[Microsoft][SQL Server Native Client 11.0]Invalid Descriptor Index'
 rc=0
2018-11-06T12:59:56.753-05:00 error vpxd[08228] [Originator@6876 sub=Main] Init failed. VdbError: Error[VdbODBCError] (-1) ODBC error: (07009) - [Microsoft][SQL Server Native Client 11.0]Invalid Descriptor Index
--> Backtrace:

-->
2018-11-06T12:59:56.753-05:00 trivia vpxd[08228] [Originator@6876 sub=VpxProfiler] Ctr: TotalTime = 1198 ms
2018-11-06T12:59:56.753-05:00 error vpxd[08228] [Originator@6876 sub=Default] Failed to intialize VMware VirtualCenter. Shutting down

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


Resolution

This issue is resolved in VMware vCenter Server 6.7 Update 2, available at VMware Downloads.