Corrective action 1
In most cases, the management server might not be able to respond to the request from the client, or the response from the server might be extremely slow. Click <OK> and call a management server again.
Corrective action 2
If the corrective action 1 does not work, the Java application (Web-Based Admin View screen) might not be operating normally. Exit the Java application, and then, restart the Web-Based Admin View screen, or reboot the client first.
Reference problem
Corrective action
When the system environment was modified in the environment setup, it is displayed in the client in which the setup was done. Take a proper action in the following:
Click [Yes] to reconnect.
Click [No] to end the connection.
Click [Detailed information] to display error detailed information.
Corrective action
The network failure might have occurred, the client terminal's CPU might have been overloaded, or the system time setting of the management server might have been changed. Take a proper action in the following:
Click [Yes] to reconnect to another management server.
Click [No] to end the current connection.
Reference problem
"Symptom 1" in "Troubleshooting"
Corrective action
The management server may not have been started. Take a proper action in the following:
Click [Yes] to reconnect.
Click [No] to end the connection.
Click [Detailed information] to display error detailed information.
Reference problem
Corrective action 1
The Web-Based Admin View screen might not be operating properly. Exit the screen, and then, restart the Web-Based Admin View screen, or reboot the client first.
Corrective action 2
Refer to take appropriate action while referring to the explanation of "Symptom 14" in troubleshooting to take a Corrective action. Still, the problem is not improved, report the contents of the Java console or the Java execution log to local Customer Support.
Reference problem
"Symptom 14" in "Troubleshooting"
Corrective action
Select one of [Yes], [No], or [Detailed information]:
Click [Yes] to retrieve an active management server for connection.
Click [No] to end the connection.
Click [Detailed information] to display error detailed information.
Note
This message appears if no response is received from the management server. Confirm the state of the management server or the network.
If connection is available by selecting [Yes], a temporary network load is assumed to be the cause of the disconnection.
In this case, raise the "Connection monitoring time between Client and Server" of the system environment.
Reference problem
"Symptom 2", "Symptom 13" in "Troubleshooting"
Corrective action
The management server is terminated. Sign off Web-Based Admin View.
Corrective action
Enter a correct user name and password.
Reference problem
"Symptom 15" in "Troubleshooting"
Corrective action
Enter a correct password.
Corrective action
A network error has occurred. Restart the cluster management server and the monitored node, and then reconnect the network following the procedures described in "6.2 Restart". Still, the problem is not improved, contact local Customer Supports.
Corrective action
Screen startup using the Java Plug-in is not supported.
Access the URL to download and install the application.
Note
This error message is displayed only in an environment where the Java Plug-in is not supported.
Corrective action
Screen startup using the Java Web Start is not supported.
Access the URL to download and install the application.
Note
This error message is displayed only in an environment where the Java Web Start is not supported.
Corrective action
The number of parameters specified in [Target] of the shortcut is not correct.
Check the parameters in [Target] and set two parameters that are the IP address and the port number of the management server. For the details of settings, refer to "3.1.3.2 Setting up Java application."
Corrective action
Correct the IP address set in the parameter of [Target] of the shortcut to an IP address format. For the details of settings, refer to "3.1.3.2 Setting up Java application."
Corrective action
Correct the port number (integers from 1 to 65535) set in the parameter of [Target] of the shortcut to the http port number of the management server. For the details of settings, refer to "3.1.3.2 Setting up Java application."
Corrective action
Create the configuration file directly in an application folder (example: "C:\Users\[User name]\AppData\Local\Programs\ PRIMECLUSTER Web-Based Admin View Startup\"), or after uninstalling the Java application (PRIMECLUSTER Web-Based Admin View Startup), install the Java application again.
When creating the configuration file, it must be empty file or set a settable parameter.
For how to uninstall the Java application, refer to "3.6 Deleting Java application" and for how to install the Java application, refer to "3.1.3.1 Installing Java application."
For the settable parameters, refer to "0075" of "Web-Based Admin View message."
Corrective action
Correct the setting value in the setting parameter according to the message.
For how to set up the setting parameters, refer to the following sections:
redirect
language
"3.5.1 Tentative modification of screen display settings (Language, Look & Feel)"
initialwait
"Symptom 4" in "Troubleshooting"
Corrective action
Refer to "Symptom 1" in "Troubleshooting."
