HP Matrix Operating Environment 7.3 Recovery Management User Guide

No configuration operation can be run
Possible causes include:
An Activate, Deactivate, or Import operation is in progress.
Another configuration operation may be in progress
Unable to import Storage Management Servers as part of an import operation
Possible causes include:
The Storage Management Server was not discovered in the HP Matrix Operating
Environment user interface.
The credentials associated with the Storage Management Server do not include the user
name specified in the Matrix recovery management configuration at the Local Site.
The HP Matrix Operating Environment user interface is unable to communicate with the
Storage Management Server specified in the Matrix recovery management configuration
at the Local Site.
Import operation failed
Possible causes include:
The import file is not valid.
The HP Logical Server Automation service is not running.
There were recovery logical servers in an active state at the time of the import.
Configuration error messages
This section lists Matrix recovery management configuration error messages.
Error: Matrix recovery management is being quiesced. Currently running
operations will be allowed to complete. No configuration changes are
allowed at this time.
Error message
The user attempts to change the configuration of Matrix recovery management when the system is
being quiesced.
Cause
Wait for Matrix recovery management to be unquiesced and retry the configuration change.Action
Error: Matrix recovery management is quiesced. No configuration changes
are allowed at this time.
Error message
The user attempts to change the configuration of Matrix recovery management when the system
has been quiesced.
Cause
Wait for Matrix recovery management to be unquieced and retry the configuration change.Action
You are not authorized to access this page.Error message
The user is not authorized to use Matrix recovery management , or the local CMS hostname cannot
be resolved by the DNS.
Cause
Check the HP SIM and Matrix recovery management log files for details, then contact the network
administrator to add the local CMS hostname to the DNS.
Action
54 Troubleshooting