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