The Veritas Enterprise Administrator Service (vxsvc) hangs in a 'Starting' state during startup

book

Article ID: 100033725

calendar_today

Updated On:

Description

Error Message

In Windows Service Control Manager (start > run > services.msc), the Veritas Enterprise Administrator Service will report its status as Starting

The error below is reported in the vdid.log which is found in %vmpath%Logs directory:

vxcadisk.c:get_addrunit_id: Failed to form Disk VDID as no LunSrNo. vdid_err 1007

Cause

With HP 3PAR array firmware version 3.1.3 or earlier, the LUN serial number is available in a standard SCSI Inquiry. However, for the same array with a firmware version greater than 3.1.3, the LUN serial number is now available on SCSI page #83 inquiry only.

The SFW HP 3PAR VDID library (3pardata.dll) is not updated to fetch the serial numbers from SCSI page #83 inquiry and as a result, the HP 3PAR VDID library fails to claim the LUNs. This results in the Veritas Enterprise Administrator service hanging in a 'starting' state.

Due to the VDID naming convention, the SFW VDID libraries (veritas.dll and the vxcadisk.dll) face a conflict to claim the LUNs.

Resolution

A supported hotfix has been made available for this issue. Please contact Veritas Technical Support to obtain this fix. 

 

Issue/Introduction

After installation of Veritas InfoScale for Windows, the Veritas Enterprise Administrator Service (vxsvc) hangs on startup.

Note: This problem is only observed with InfoScale version 7.2, and when storage provisioned to the server is from an HP 3PAR array.

Additional Information

ETrack: 3908367