ExpressCluster X 2.0 for Windows Reference Guide - Nec

Section I Detailed functions of ExpressCluster
Error messages on the WebManager
Level Message Cause Solution
Error Failed to connect to
the server.
Error Failed to get the list of
mirror disk error.
Error Failed to get the data
for the cluster tree
view from the server.
Error Another user is
performing
auto-search now. Try
it again later.
Failed to communicate with
the WebManager.
Disk Agent failed to get the
information on the mirror
disk.
Internal error of the Disk
Agent occurred.
The access to the Disk
Agent from the
ExpressCluster Web Alert
service failed.
The processing timed out on
the server.
Failed to get the cluster data
of the destination server.
Failed to get all cluster data
in the cluster tree view.
Auto-search has already
been performed from the
other manager.
Error Internal error. An internal error of the
WebManager has occurred.
Warning Failed to obtain a part
of the cookie data.
Warning Could not save the
cluster list because
cookie is not allowed.
Make cookie settings
enabled to display the
list of clusters, and
then restart your
browser.
Error The specified cluster
"{0}" has been
registered.
Info The cluster "{0}" has
been successfully
registered.
Error The cluster cannot be
unregistered now
because it is being
updated to the latest
data. Try again later.
Error Failed to find this
cluster. Check that the
IP address or port
The cookie file that supports
the IP address was
corrupted.
Cookie is not allowed to be
used by the browser.
The cluster with the same
name already exists in the
tree view of the cluster.
The cluster has already
been registered in the tree
view.
The screen is updating by
getting the latest data from
the WebManager server.
The cluster has not been
found by the P address and
port number entered.
ExpressCluster Web
Alert service if the error
still occurs.
Check if the
ExpressCluster Web
Alert service is working
on the server.
Check if connecting to
the server can be
performed successfully.
Check if the Disk Agent
is operating. If the Disk
Agent is not operating,
restart the server.
Check if ExpressCluster
is operating by running a
command on the
destination server
Check if all cluster
management IPs in the
tree view are running
normally.
Retry auto-search later.
Perform the auto-search
again. If an error still
occurs, restart the
ExpressCluster Web
Alert service.
Delete the cookie file
and open the window
again.
Allow cookie by the
browser.
Use the cluster data that
already exists in the tree
view.
-
Try again after updating
the data is completed.
Check if the IP address
and the port number are
correct.
83