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