HP 3PAR Recovery Manager Software for VMware vSphere Licenses - Manual (Page 110)

Table 7 Recovery Manager for Microsoft Exchange Event Messages (continued)
Description/Action Error Message Event ID
Unable to access registry for the specified key
name.
•
Use regedit to check that the registry still has
the corresponding key and that you have
permission to access it.
RM5062: ERROR: Could not query windows
registry key <Registry Key>. 5062
Unable to access the registry for the specified key
name.
• Use regedit to check that the registry still has
the corresponding key and that you have
permission to access it.
3PARVSS5063: ERROR: Could not query
windows registry key name <Registry Key>. 5063
Unable to access the registry for the HP 3PAR VSS
Provider Software installation. RM5064: ERROR: Could not open windows
registry key for 3PAR VSS Provider. 5064
•
Verify the VSS Provider installation using
Add/Remove program or by running vssadmin
list providers
.
• Check that the registry still has the corresponding
key and that you have proper permission to
access it. If this key is missing, you need to
reinstall the VSS Provider package.
The designated target LUN is not an HP 3PAR virtual
volume.
• Verify that all database and log destinations
belong to the HP 3PAR Storage System.
3PARVSS5065: ERROR: Target LUN <Lun
Id> is not a 3PAR Virtual Volume. 5065
The specified target volume does not have adequate
device information and does not allow for proper
identification. 3PARVSS5066: ERROR: Target LUN <Lun
Id> could not be identified. 5066
The specified destination volume does not have
adequate device information and does not allow
for proper identification. 3PARVSS5067: ERROR: Destination LUN
<Lun Id> could not be identified. 5067
An unexpected snapshot set ID was encountered
during the snapshot set preparation.
• Restart both the Volume Shadow Copy Service
and the HP 3PAR VSS Provider Service to reset
the status.
3PARVSS5071: ERROR: Unexpected
snapshot set ID at <Server Name>. 5071
The internal VSS call stack is not in the correct
order.
•
Restart both the Volume Shadow Copy Service
and the HP 3PAR VSS Provider Service to reset
the status.
3PARVSS5072: ERROR: <Error Code> call
out of order. 5072
Unable to get the CLI registration information for
the local system. 3PARVSS5073: ERROR: Could not detect
3PAR InForm CLI installation. 5073
• Verify the CLI package installation using
Add/Remove Programs.
•
Verify the registry keys for the CLI installation.
A resource allocation error occurred during a VSS
Writer operation. RME5102: ERROR: The VSS Writer ran out
of memory or other system resources. The
recommended way to handle this error is to 5102
• Try waiting 10 minutes and then retry the
operation.
wait ten minutes and then repeat the
operation. If the VSS Writer is in a bad
•
Run vssadmin list writers to verify that
the VSS writer is in a Healthy state. state, restart the writer’s service. Check the
application event log.
110 Event Messages