HP 3PAR VSS Provider Software - Manual (Page 23)

Table 3 Application Events (continued)
Action Description Event ID
Contact your local service provider
with the detailed log file. Could not create file <filename>.
The VSS Provider for Microsoft Windows failed to open the
temporary file <filename> which is generated internally.
5058
Try to correct the system error based
on the message. Generic system error.
This error message is generated by the system.
5059
Check the Window Disk Manager
and the systemto verify that the IOCTL inquiry call failed.
Failed on SCSI inquiry to the storage device through an IOCTL call.
5061
device is active and functioning
properly.
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 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 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 VSS Could not open the register key for VSS Provider for Microsoft
Windows. 5064
Provider for Microsoft Windows
Failed to open register key
installation. Check to see if the
[HKEY_LOCAL_MACHINE\SO FTWARE\3par\HWPRV] installation was successful. If
necessary, you may have to re-install
the VSS Provider for Microsoft
Windows.
Move the data out from the non-HP
3PAR Virtual Volume to an HP 3PAR 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
Virtual Volume, and perform the task
again.
The 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 reproduce
the problem to collect VSS trace data The target LUN could not be identified.
VSS Provider for Microsoft Windows failed to provide the information
of the target LUN during the AreLunsSupport() interface.
5066
for Microsoft Product Support
Service.
Turn on VSS logging and reproduce
the problem to collect VSS trace data The destination LUN could not be identified.
VSS Provider for Microsoft Windows failed to provide the information
of the destination LUN from the interface.
5067
for Microsoft Product Support
Service.
Check both the Window Disk
Manager and the system to see if the Could not retrieve device descriptor <device_ID>.
Failed to retrieve device <device_ID> information.
5068
device is active and functioning
properly.
Set the LogLevel to ‘4’ and reproduce
the problem. Provide the DeviceIoControl call failed.
Internal error.
5069
3parprov.log file to your local
service provider.
Set the LogLevel to ‘4’ and reproduce
the problem. Provide the The internal snapshot information is empty.
This is an internal error. It is likely that the VSS Provider for Microsoft
Windows could not find the mounted snapshot volume.
5070
3parprov.log file to your local
service provider.
Application Event Log 23