HP 3PAR VSS Provider 2.2.2 for Microsoft Windows User Guide (QL226-97305, December 2013)

Table 3 Application Events (continued)
ActionDescriptionEvent
ID
Check the Window Disk Manager and
the system to verify that the device is
active and functioning properly.
IOCTL inquiry call failed.
Failed on SCSI inquiry to the storage device through an IOCTL call.
5061
Check for the existence of the key name
<value_number> from the register
database.
Could not query the register key value for <value_number>.
The HP 3PAR VSS Provider for Microsoft Windows relies on the
registry to store certain data for internal use, such as snapshot set
ID or the LogLevel, to log the trace.
5062
Check for the existence of the key name
<key_name> from the register database.
Could not query the register key name of <key_name>.
The HP 3PAR VSS Provider for Microsoft Windows relies on the
registry to store certain data for internal use, such as snapshot set
ID or the LogLevel, to log the trace.
5063
The registry key was created by the
installer program during the HP 3PAR
Could not open the register key for HP 3PAR VSS Provider for
Microsoft Windows.
5064
VSS Provider for Microsoft Windows
Failed to open register key
installation. Check to see if the
[HKEY_LOCAL_MACHINE\SOFTWARE\3par\HWPRV].
installation was successful. If necessary,
you may have to re-install the HP 3PAR
VSS Provider for Microsoft Windows.
Move the data out from the non-HP 3PAR
Virtual Volume to an HP 3PAR Virtual
Volume, and perform the task again.
Target LUN <LUN_number> is not an HP 3PAR Virtual Volume.
One of the snapshots from the snapshot set is not targeting a Virtual
Volume.
5065
The HP 3PAR VSS Provider for Microsoft Windows relies on the
registry to store certain data for internal use, such as snapshot set
ID or the LogLevel, to log the trace.
Turn on VSS logging and recreate the
issue to collect VSS trace data for
Microsoft Product Support Service.
The target LUN could not be identified.
HP 3PAR VSS Provider for Microsoft Windows failed to provide
the information of the target LUN during the AreLunsSupport()
interface.
5066
Turn on VSS logging and recreate the
issue to collect VSS trace data for
Microsoft Product Support Service.
The destination LUN could not be identified.
HP 3PAR VSS Provider for Microsoft Windows failed to provide
the information of the destination LUN from the interface.
5067
Check both the Window Disk Manager
and the system to see if the device is
active and functioning properly.
Could not retrieve device descriptor <device_ID>.
Failed to retrieve device <device_ID> information.
5068
Set the LogLevel to ‘4’ and recreate the
issue. Provide the 3parprov.log file
to your local service provider.
DeviceIoControl call failed.
Internal error.
5069
Set the LogLevel to ‘4’ and recreate the
issue. Provide the 3parprov.log file
to your local service provider.
The internal snapshot information is empty.
This is an internal error. It is likely that the HP 3PAR VSS Provider
for Microsoft Windows could not find the mounted snapshot volume.
5070
Set the LogLevel to ‘4’ and recreate the
issue. Provide the 3parprov.logfile to
your local service provider.
Unexpected snapshot set ID.5071
Set the LogLevel to ‘4’ and recreate the
issue. Provide the 3parprov.log file
to your local service provider.
call out of order.5072
Verify that the HP 3PAR CLI is installed.Could not detect HP 3PAR CLI installation.5073
Application Event Log 29