HP 3PAR Recovery Manager 4.5.0 Software for Microsoft Exchange 2007, 2010, and 2013 User Guide

Table 10 HP 3PAR Recovery Manager Software for Microsoft Exchange Event Messages (continued)
Description/ActionError MessageEvent ID
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.
The maximum number of LUNs that can be presented to the host is 255.
Remove unwanted LUNs and tray the operation again.
3PARVSS5090: ERROR:
Maximum of 255 LUN number
has been reached.
5090
A resource allocation error occurred during a VSS Writer operation.RME5102: ERROR: The VSS
Writer ran out of memory or
5102
• Try waiting 10 minutes and then retry the operation.
other system resources. The
• Run vssadmin list writers to verify that the VSS writer is in
a Healthy state.
recommended way to handle
this error is to wait ten minutes
and then repeat the operation.
If the VSS Writer is in a bad
state, restart the writer’s service.
Check the application event log.
The VSS Writer operation has exceeded the 20 second timeout limit for
the freeze and thaw stage allocated by Exchange.
RME5103: ERROR: The VSS
Writer operation failed because
of a timeout between the Freeze
and Thaw events.
5103
• Verify that the Exchange writer is in a Healthy state using vssadmin
list writers.
• This can be sometimes due to an attempt of a snapshot during high
I/O times. If the Exchange writer is in a bad state, restart Exchange
Information Store service. Attempt the snapshot at a less stressful time
to the Exchange server.
The VSS Exchange Writer has failed.RME5104: ERROR: The VSS
Exchange Writer has failed. This
5104
• This can be verified by running the vssadmin list
writerscommand from the command line.
can be verified by running the
command "vssadmin list writers"
from the command line.
• Execute the same command which caused VSS exchange writer
failure error. The next HpRmCli command will bring back VSS
exchange writer into stable state.
The VSS Writer is not responding.
• Run vssadmin list writers to verify that the VSS writer is in
a Healthy state.
RME5106: ERROR: The VSS
Writer is not responding.
5106
The VSS Writer is not operating properly.RME5108: ERROR: The VSS
Writer infrastructure is not
5108
• Check that the Event Service and VSS have been started.
operating properly. Check that
• Run vssadmin list writers to verify that the VSS writer is in
a Healthy state and check the system event log for errors associated
with those services.
the Event Service and VSS have
been started, and check for
errors associated with those
services in the error log.
167