10. Error messages

This chapter provides information on error messages you might encounter in operating EXPRESSCLUSTER.

This chapter covers:

• 10.1. Messages

• 10.2. Messages during setup

• 10.3. Messages reported by event log and alert

• 10.4. Driver event log messages

• 10.5. Detailed information in activating and deactivating group resources

• 10.6. Detailed information of monitor resource errors

• 10.7. STOP codes list of disk RW monitor resources

• 10.8. Filter driver STOP code list

• 10.9. JVM monitor resource log output messages

• 10.10. STOP codes list of user space monitor resources

10.1. Messages

10.2. Messages during setup

Module Type	Error Message	Solution
setup	Previous version of EXPRESSCLUSTER is installed. Upgrading from this version is not supported. Install after uninstalling the previous version of EXPRESSCLUSTER.	Uninstall the previous version of EXPRESSCLUSTER, and then try installing again.
setup	The SNMP service is running. You need to stop the SNMP service before you perform uninstallation. Do you want to stop the SNMP service now?	Select Yes to stop the SNMP service automatically and continue the installation. Or, select No to cancel the installation, manually stop the SNMP service and then perform installation again.
setup	Setup has failed. Error code : xxx	- Check the system requirements, setup procedures and notes described in the manual, and make sure they are followed. - If other application is running, terminate it. - Install again after restarting the OS.
setup	Setup has failed(xxx). Error code : xxx Please reboot the system and try again.	- Check the system requirements, setup procedures and notes described in the manual, and make sure these requirements are followed. - If other application is running, terminate it. - Install again after starting the OS again.
setup	Unsupported environment.	Install in the environment where the system requirements are met.
setup	Cannot perform uninstallation because there is one or more EXPRESSCLUSTER services still running. Stop all EXPRESSCLUSTER services before you restart uninstallation.	Stop all EXPRESSCLUSTER services, and then perform uninstallation.
setup	Failed to start the installer. (errcode: xxx)	- Check the system requirements, setup procedures and notes described in the manual, and make sure they are followed. - If other application is running, terminate it. - The installer file may be corrupted or missing. Check it.
setup	Internal error. (xxx)	- Check the system requirements, setup procedures and notes described in the manual, and make sure they are followed. - If other application is running, terminate it.

10.3. Messages reported by event log and alert

These are the messages reported by applications, event logs, and alert logs of the Cluster WebUI. Messages with o in the columns of Alert, Eventlog and Userlog are recorded in each log. The following shows how to refer the logs:

Log Name	How to refer	File Name
Alert	Output to the Alert Logs of the Cluster WebUI. Logs can be collected by using the log collection tool.	alertlog.alt
Event log	Output to the Event Viewer (application log) of the OS. Collect logs by using the log collection tool. The source of the event is "EXPRESSCLUSTER X." Logs can be collected by using the log collection tool. Note because they are collected in the binary format with the file names in the right column, it is necessary to open the files using Event Viewer in the environment where EXPRESSCLUSTER is set up to refer to the information.	AppEvent.Evt SysEvent.Evt
User log	These are the logs with text format, in which detail information is recorded. They are output in the "userlog.{00 - 02}.log" file in the log folder of the logs collected by using the log collection tool.	userlog.{00 - 02}.log

Messages with "o" in the Mail Report column will be sent as e-mail by EXPRESSCLUSTER X Alert Service.

Messages with "o" in the SNMP Trap column will be sent as SNMP trap.

"Report Settings" are settings of when linking to the ESMPRO Agent. In "Alive," the ESMPRO Agent performs the Alert report. In "Manager," alerts are output to the ESMPRO Agent. For details, see the manual of the ESMPRO Agent.

For Mail Alert and SNMP Trap sending, refer to "Alert Service tab" of "Cluster properties" in "2. Parameter details" and "Alert Service" in "7. Information on other settings"

The report settings in "Alert Service tab" of "2. Parameter details" cannot be configured for any message marked with x.

If the "o" mark is shown in the Message Topic column, the message on that row is reported when Amazon SNS linkage function is enabled.

For details of Amazon SNS linkage function, see "2. Parameter details" - "2.2. Cluster properties" - "2.2.20. Cloud tab".

In the table below, each number indicates the following:

[1]Alert, [2]Eventlog, [3]Userlog, [4]Mail Report, [5]SNMP Trap, [6]Alive, [7]Manager, [8]Message Topic

Module Type	Event Type	Event ID	Messages	Description	Solution	1	2	3	4	5	6	7	8
nm	Information	1	The server %1 has been started.	Server up	-	o	o
nm	Information	2	The server %1 has been stopped.	Server down	Server down was detected. Remove the failures of the server and then return the server to the cluster.	o	o		o	o	o	o	o
nm	Information	3	The resource %2 of the server %1 has been started.	Resource up	-			o
nm	Error	4	The resource %2 of the server %1 has an error.	Resource abnormally	An error of the resource was detected. Refer to the event logs of the appropriate resource.			o
nm	Information	5	The resource %2 of the server %1 has been recovered to the normal status.	Resource recover	-			o
nm	Error	6	The resource %2 of the server %1 is unknown.	Resource unknown	Check the cluster configuration data.	o	o					o
nm	Error	7	Network partition was detected. Shut down the server %1 to protect data.	Network partition detected	No heartbeat resources can be used. Make sure there is no error in the network adapter and the network is correctly connected.	o	o	o			o	o
nm	Error	8	An error occurred while confirming the network partition. Shut down the server %1.	It was not possible to check for a network partition.	Refer to the event logs to check whether an error has occurred in a resource.	o	o	o			o	o
nm	Error	9	An error occurred in confirming the network partition. To avoid failover on multiple servers, the server %1 suspended failover.	Failover hold	Refer to the event logs to check whether an error has occurred in a resource.	o	o	o			o	o
nm	Information	10	The server %1 canceled the pending failover.	Failover hold cancel	-	o	o	o
nm	Error	11	Shut down the server %1. (reason:%2)	Server shutdown	No heartbeat resources can be used. Make sure there is no error in the network adapter and the network is correctly connected.	o	o				o	o
nm	Error	12	Cluster service will be stopped. (reason:%1)	Cluster service stopping	Check the cause following the message.	o	o					o
nm	Warning	13	The combination of the network partition resources is invalid. (server name:%1)	NP resource combination error	Check the cluster configuration data.	o	o					o
nm	Error	14	The status of heartbeat %1 is abnormal.	Heartbeat abnormally	Make sure there is no error in the network adapter and the network is correctly connected.	o	o				o	o
nm	Information	15	The heartbeat %1 has been recovered to the normal status.	Heartbeat recovered	-	o	o
nm	Error	16	The network partition %2 of the server %1 has an error.	Network partition abnormally	Refer to the event logs to check whether an error has occurred in a resource.	o	o				o	o
nm	Information	17	The network partition %2 of the server %1 has been recovered to the normal status.	Network partition recovered	-	o	o
nm	Error	18	Failed to start the resource %1. Server name:%2	Resource start failed	Refer to the event logs to check whether an error has occurred in a resource.	o	o				o	o
nm	Information	19	Waiting for servers to start up has been canceled.	Waiting for servers to start up has been canceled.	-	o	o
nm	Error	20	Network partition was detected. Shut down the server %1 for the cluster service to protect data.	Network partition detected	No heartbeat resources can be used. Make sure there is no error in the network adapter and the network is correctly connected.	o	o	o
nm	Error	21	An error occurred when checking for a network partition. Shut down the server %1 for the cluster service to protect data.	It was not possible to check for a network partition.	Refer to the event logs to check whether an error has occurred in a resource.	o	o	o
nm	Error	22	Network partition was detected. Execute action(%1) on the server %2 for the cluster service to protect data.	Network partition	No heartbeat resources can be used. Make sure there is no error in the network adapter and the network is correctly connected.	o	o	o
nm	Error	23	An error occurred when checking for a network partition. Execute action(%1) on the server %2 for the cluster service to protect data.	Can not network partition resolution	Refer to the event logs to check whether an error has occurred in a resource.	o	o	o
nm	Error	24	Execute action(%1) on the server %2. (reason:%3)	Can not network partition resolution	No heartbeat resources can be used. Make sure there is no error in the network adapter and the network is correctly connected.	o	o	o
nm	Warning	25	The NP resolution process at the cluster startup is disabled.	Network partition resolution disabled	The NP resolution process at the cluster startup is disabled.	o	o	o
pm	Information	501	Cluster service has been started properly.	Cluster service started	-	o	o	o
pm	Information	502	Cluster service is shutting down.	Cluster service shutting down	-	o	o	o
pm	Error	510	Cluster service has already been started.	Cluster service already started	Check the status of cluster service.	o	o	o				o
pm	Error	511	Fatal error has occurred in the cluster service.	Critical error in cluster service	The service is not run by a user with required privilege or the system may not be able to operate properly.	o	o	o	o	o		o	o
pm	Error	512	An error is detected in xml library.	problem detected in xml library	The system may not be able to operate properly.	o	o	o				o
pm	Error	513	An error is detected in configuration file.	problem detected in configuration file	Check the cluster configuration data.	o	o	o	o	o		o	o
pm	Error	514	Configuration file does not exist.	Configuration file not exists	Upload the cluster configuration data.	o	o	o				o
pm	Error	515	My host name is not found in configuration file.	my name not found in configuration file	Check the cluster configuration data.	o	o	o				o
pm	Error	520	%1 process terminated abnormally.	process exit abnormally	The system may not be able to operate properly.	o	o	o	o	o		o	o
pm	Error	521	The cluster service process returned an error. (halting system)	Rc process exit with error	Deactivation of group resources may be failed. Take appropriate action by following the group resource message.	o	o	o				o
pm	Error	522	An error has occurred while initializing %1 process. (return code:%2)	process init error	Check the cause of an initialization error and troubleshoot it.	o	o	o	o	o		o	o
pm	Information	523	The system will be shut down.	system halting	-	o	o	o
pm	Information	524	Cluster service will be stopped.	Cluster service stopping	-	o	o	o
pm	Information	525	System will be rebooted.	System rebooting	-	o	o	o
pm	Information	526	%1 process will be restarted.	Process restarting	-	o	o	o
pm	Information	527	Emergency shutdown is in progress.	Emergency shutdown	-	o	o	o
pm	Information	528	Generating STOP error.	Stop Error	-	o	o	o
pm	Information	529	Generating hardware reset.	HW reset	-	o	o	o
pm	Information	530	There was a request to shut down the system from the %1.	request of system halt	-	o	o	o
pm	Information	531	There was a request to stop cluster service from the %1.	request of cluster service stop	-	o	o	o
pm	Information	532	There was a request to reboot system from the %1.	request of system reboot	-	o	o	o
pm	Information	533	There was a request to restart cluster service from the %1.	request of cluster service restart	-	o	o	o
pm	Information	534	There was a request to resume cluster service from the %1.	request of cluster service resume		o	o	o
pm	Information	535	There was a request to suspend cluster service from the %1.	request of cluster service suspend	-	o	o	o
pm	Information	536	There was a request of emergency shutdown from the %1.	request of emergency shutdown	-	o	o	o
pm	Information	537	There was a request to generate STOP error from the %1.	request of STOP error	-	o	o	o
pm	Information	538	There was a request to generate hardware reset from the %1.	request of HW reset	-	o	o	o
pm	Information	540	Requesting shutdown to the automatic running control software.	shutdown request to the automatic running control software start	-	o	o	o
pm	Information	541	Requesting shutdown (reboot) to the automatic running control software.	shutdown (reboot) request to the automatic running control software	-	o	o	o
pm	Information	542	Shutdown request to the automatic running control software is completed.	shutdown request to the automatic running control software complete	-	o	o	o
pm	Error	543	The automatic running control software returned an error to the shutdown request.	shutdown by ESMPRO/AC fail	The automatic operating settings may be incorrect. Check the settings.	o	o	o				o
pm	Error	544	Communications with the automatic running control software failed.	Communications with ESMPRO/AC fail	The system may not be able to operate properly.	o	o	o				o
pmsvc	Error	801	The system will be shutdown because cluster resume was failed.	Failed to resume the cluster daemon	-	o	o	o
pmsvc	Error	802	An attempt to shutdown the system failed.	Failed to shutdown the system	The system may not be able to operate properly.	o	o	o
pmsvc	Information	810	The system shutdown was initiated by other than cluster service. Stopping cluster service. (timeout=%1 min).	Stopping cluster service.	-	o	o	o
pmsvc	Information	811	Stopping cluster service has been completed.	Stopping cluster service has been completed.	-	o	o	o
pmsvc	Error	812	Stopping cluster service has timed out.	Stopping cluster service has timed out.	-	o	o	o
pmsvc	Warning	813	Stopping cluster service has been canceled.	Stopping cluster service has been canceled.	-	o	o	o
rc	Information	1010	The group %1 is starting.	group-start started	-	o	o	o
rc	Information	1011	The group %1 has been started.	group-start ended	-	o	o	o
rc	Error	1012	Failed to start the group %1.	group-start failed	Take appropriate action by following the group resource message.	o	o	o				o
rc	Information	1015	Waiting for group %1 to start has started.	waiting for group to start has started.	-	o	o	o
rc	Information	1016	Waiting for group %1 to start has been completed.	waiting for group to start has been completed.	-	o	o	o
rc	Error	1017	Group start was canceled because waiting for group %1 to start was timed out. (%2)	waiting for group to start has timed out.	Check the status of the group waiting to start. If the group has not yet been started, re-perform the group operation after starting that group.	o	o	o
rc	Warning	1018	Waiting for group %1 to start has timed out. However, group start continues. (%2)	group start continues.	-	o	o	o
rc	Warning	1019	Server %1 is not in a condition to start group %2.	cannot-start-group	Perform server recovery if the target server is suspended (Isolated). If it is suspended (Network Partition Unsolved), recover network partition resources to the normal status.	o
rc	Information	1020	The group %1 is stopping.	group-stop started	-	o	o	o
rc	Information	1021	The group %1 has been stopped.	group-stop ended	-	o	o	o
rc	Error	1022	Failed to stop the group %1.	group-stop failed	Take appropriate action by following the group resource message.	o	o	o				o
rc	Information	1025	Waiting for group %1 to stop has started.	waiting for group to stop has started.	-	o	o	o
rc	Information	1026	Waiting for group %1 to stop has started.	waiting for group to stop has been completed.	-	o	o	o
rc	Error	1027	Group stop has been canceled because waiting for group %1 to stop has timed out. (%2)	waiting for group to stop has timed out.	Check the status of the group waiting to stop. If the group has not yet been stopped, re-perform the group operation after stopping that group.	o	o	o
rc	Warning	1028	Waiting for group %1 to stop has timed out. However, group stop continues. (%2)	group stop continues.	-	o	o	o
rc	Information	1030	The resource %1 is starting.	resource-start started	-		o	o
rc	Information	1031	The resource %1 has been started.	resource-start ended	-		o	o
rc	Error	1032	Failed to start the resource %1. (%2 : %3)	resource-start failed	Check the cause for failing to start the resource. If a stall occurs during start processing, "Failed to start the resource %1. (99 : command is timeout)" is output.	o	o	o	o	o		o	o
rc	Error	1033	Failed to start the recovery script of resource %1. (%2 : %3)	recoverscript-start failed	Check the cause for failing to start the recovery script.	o	o	o				o
rc	Information	1034	A request to activate %1 resource on server %2 has been started.	Resource start request to the standby server	-	o	o	o
rc	Information	1035	A request to activate %1 resource on server %2 has been completed.	Resource start request to the standby server completed.	-	o	o	o
rc	Error	1036	A request to activate %1 resource on server %2 has been failed.	Resource activation request to the standby server failed.	Check if there is an error with the network or with the remote server.	o	o	o
rc	Information	1037	Since the startup attribute is set to manual, the activation of resource %1 was suppressed.	Resource activation suppressed	-	o	o	o
rc	Information	1040	The resource %1 is stopping.	resource-stop started	-		o	o
rc	Information	1041	The resource %1 has been stopped.	resource-stop ended	-		o	o
rc	Error	1042	Failed to stop the resource %1. (%2 : %3)	resource-stop failed	Check the cause for failing to stop the resource. If a stall occurs during stop processing, "Failed to stop the resource %1. (99 : command is timeout)" is output.	o	o	o	o	o		o	o
rc	Information	1044	A request to stop %1 resource on server %2 has been started.	Resource stop request to the standby server	-	o	o	o
rc	Information	1045	A request to stop %1 resource on server %2 has been completed.	Resource stop request to the standby server completed.	-	o	o	o
rc	Error	1046	A request to stop %1 resource on server %2 has been failed.	Resource stop request to the standby server failed.	Check if there is an error with the network or with the remote server.	o	o	o
rc	Information	1050	Moving the group %1.	group-move started	-	o	o	o
rc	Information	1051	The group %1 has been moved.	group-move ended	-	o	o	o
rc	Error	1052	Failed to move the group %1.	group-move failed	Take appropriate action by following the group resource message.	o	o	o				o
rc	Warning	1059	Server %1 is not in a condition to move group %2.	cannot-move-group	Perform server recovery if the target server is suspended (Isolated). If it is suspended (Network Partition Unsolved), recover network partition resources to the normal status.	o
rc	Information	1060	Failing over the group %1.	group-failover started	-	o	o	o
rc	Information	1061	The group %1 has been failed over.	group-failover ended	-	o	o	o
rc	Error	1062	Failed to fail over the group %1.	group-failover failed	Take appropriate action by following the group resource message.	o	o	o				o
rc	Information	1070	Restarting the group %1.	group-restart started	-	o	o	o
rc	Information	1071	The group %1 has been restarted.	group-restart ended	-	o	o	o
rc	Error	1072	Failed to restart the group %1.	group-restart failed	Take appropriate action by following the group resource message.	o	o	o				o
rc	Error	1077	Group failover has failed because there is a server incapable of internal communication.	group-failover failed (internal communication disabled)	Check the LAN heartbeat status in kernel mode. Start the group after recovering internal communication.	o	o	o
rc	Information	1080	Restarting the resource %1.	resource-restart started	-	o	o	o
rc	Information	1081	The resource %1 has been restarted.	resource-restart ended	-	o	o	o
rc	Error	1082	Failed to restart the resource %1.	resource-restart failed	Take appropriate action by following the group resource message.	o	o	o				o
rc	Information	1090	Shutting down the cluster.	cluster shutdown	-	o	o	o
rc	Information	1091	Shutting down the server.	server shutdown	-	o	o	o
rc	Error	1092	Group %1 is started on more than one server.	group double start	Server will automatically be shut down. Check the cause for the group to be started in more than one server.	o	o	o	o	o		o	o
rc	Error	1093	The system shutdown was performed by other than the cluster service.	system shutdown by other than cluster service	It is considered as an error if the system shuts down by other than cluster service. Follow the appropriate steps to shut down the system.	o	o	o				o
rc	Warning	1100	Shutdown count is reached the maximum number (%1). Final action of resource %2 was ignored.	shutdown count reached the limit	-	o	o	o	o	o		o	o
rc	Warning	1101	Since there is no other normally running server, the final action for an activation error of group resource %1 was suppressed.	Suppression of final action for activation error	-	o	o	o
rc	Warning	1102	Since there is no other normally running server, the final action for a deactivation error of group resource %1 was suppressed.	Suppression of final action for deactivation error	-	o	o	o
rc	Warning	1103	Since server %1 is specified as that which suppresses shutdown at both-system activation detection, it ignored the shutdown request.	Suppression of shutdown caused by both-system activation detection	-	o	o	o
rc	Warning	1104	A mismatch in the group %1 status occurs between the servers.	Generation of group status mismatch	Restart the group or reboot the cluster.	o	o	o
rc	Information	1105	Since server %1 is not specified as that which suppresses shutdown at both-system activation detection, it executed the shutdown request.	Shutdown caused by both-system	-	o	o	o
rc	Information	1110	Server %1 is returned to the cluster.	server returned	-	o	o	o
rc	Information	1111	Server %1 is isolated from the cluster.	server isolated	-	o	o	o
rc	Information	1112	Server %1 started to return to the cluster.	server return start	-	o	o	o
rc	Error	1113	Server %1 failed to return to the cluster.	server return fail	The system may not be able to operate properly.	o	o	o				o
rc	Information	1120	Server %1 will notify the automatic running control software of shutdown start.	shutdown notification start	-	o	o	o
rc	Error	1121	The automatic running control software returned an error to the shutdown start notification in server %1.	shutdown notification fail	The automatic operating settings may be incorrect. Check the settings.	o	o	o				o
rc	Information	1122	Server %1 notified the automatic running control software of shutdown start.	shutdown notification finish	-	o	o	o
rc	Information	1123	The automatic running control software is checking the power status of shared disks. A server will be restarted after the power status is checked.	waiting for disk power-on	-	o	o	o
rc	Error	1124	An error was returned from the automatic running control software. Failed to check the power status of shared disks.	disk power-on confirmation failed	The automatic operating settings may be incorrect. Check the settings. An error may have occurred in the automatic power control unit. Check the automatic power control unit.	o	o	o				o
rc	Error	1125	Server %1 failed to communicate with the automatic running control software.	communications with the automatic running control software failed	The system may not be able to operate properly.	o	o	o				o
rc	Information	1130	Starting a single resource %1.	single-resource-start started	-	o	o	o
rc	Information	1131	A single resource %1 has been started.	single-resource-start ended	-	o	o	o
rc	Error	1132	Failed to start a single resource %1.	single-resource-start failed	Take appropriate action by following the group resource message.	o	o	o				o
rc	Warning	1139	Server %1 is not in a condition to start a single resource %2.	cannot-start-single-resource	Perform server recovery if the target server is suspended (Isolated). If it is suspended (Network Partition Unsolved), recover network partition resources to the normal status.	o
rc	Information	1140	Stopping a single resource %1.	single-resource-stop started	-	o	o	o
rc	Information	1141	A single resource %1 has been stopped.	single-resource-stop ended	-	o	o	o
rc	Error	1142	Failed to stop a single resource %1.	single-resource-stop failed	Take appropriate action by following the group resource message.	o	o	o				o
rc	Information	1150	The group %1 is being migrated.	The group is being migrated.	-	o	o	o
rc	Information	1151	The group %1 has been migrated.	The group has been migrated.	-	o	o	o
rc	Error	1152	Failed to migrate the group %1.	Migrating the group has failed.	Take appropriate action by following the group resource message.	o	o	o
rc	Warning	1159	Server %1 is not in a condition to migrate group %2.	The group cannot be migrated.	Perform server recovery if the target server is suspended (isolated). If it is suspended (due to an unresolved network partition), recover network partition resources to the normal status.	o	o	o
rc	Information	1170	Server %1 in the same server group (%2) has been set as the destination for the group %3.	The destination found in the same server group	-	o	o	o
rc	Information	1171	Server %1 not in the same server group (%2) has been set as the destination for the group %3.	The destination found in the other server group	-	o	o	o
rc	Warning	1179	Can not fail over the group %1 because there is no appropriate destination in the same server group %2.	The destination not found in the same server group	Check if other servers in the same server group are stopped or isolated. If so, start the servers or return the servers to the cluster.	o	o	o
rc	Information	1200	The resource %1 will be restarted since starting the resource %2 failed.	resource-restart by resource-acterr	-	o	o	o
rc	Information	1201	The group %1 will be failed over to server %2 since starting the resource %3 failed.	group-failover by resource-acterr	-	o	o	o
rc	Information	1202	The group %1 will be stopped since starting the resource %2 failed.	group-stop by resource-acterr	-	o	o	o
rc	Information	1203	The cluster service will be stopped since starting the resource %1 failed.	service-stop by resource-acterr	-	o	o	o
rc	Information	1204	The system will be shut down since starting the resource %1 failed.	shutdown-system by resource-acterr	-	o	o	o
rc	Information	1205	The system will be rebooted since starting the resource %1 failed.	reboot-system by resource-acterr	-	o	o	o
rc	Information	1220	The resource %1 will be stopped again since stopping the resource %2 failed.	resource-stop retry by resource-deacterr	-	o	o	o
rc	Information	1223	The cluster service will be stopped since stopping the resource %1 failed.	service-stop by resource-deacterr	-	o	o	o
rc	Information	1224	The system will be shut down since stopping the resource %1 failed.	shutdown-system by resource-deacterr	-	o	o	o
rc	Information	1225	The system will be rebooted since stopping the resource %1 failed.	reboot-system by resource-deacterr	-	o	o	o
rc	Information	1241	Hardware reset will be generated since starting the resource %1 failed.	hw-reset by resource-acterr	-	o	o	o
rc	Information	1242	STOP error will be generated since starting the resource %1 failed.	stop-error by resource-acterr	-	o	o	o
rc	Information	1281	Hardware reset will be generated since stopping the resource %1 failed.	hw-reset by resource-deacterr	-	o	o	o
rc	Information	1282	STOP error will be generated since stopping the resource %1 failed.	stop-error by resource-deacterr	-	o	o	o
rc	Information	1300	Script before final action upon activation failure in resource %1 started.	Script before final action upon resource activation failure started.	-	o	o	o
rc	Information	1301	Script before final action upon activation failure in resource %1 completed.	Script before final action upon resource activation failure completed.	-	o	o	o
rc	Information	1302	Script before final action upon deactivation failure in resource %1 started.	Script before final action upon resource deactivation failure started.	-	o	o	o
rc	Information	1303	Script before final action upon deactivation failure in resource %1 completed.	Script before final action upon resource deactivation failure completed.	-	o	o	o
rc	Information	1304	Script before activation in resource %1 started.	Script before resource activation started.	-	o	o	o
rc	Information	1305	Script before activation in resource %1 completed.	Script before resource activation completed.	-	o	o	o
rc	Information	1306	Script after activation in resource %1 started.	Script after resource activation started.	-	o	o	o
rc	Information	1307	Script after activation in resource %1 completed.	Script after resource activation completed.	-	o	o	o
rc	Information	1308	Script before deactivation in resource %1 started.	Script before resource deactivation started.	-	o	o	o
rc	Information	1309	Script before deactivation in resource %1 completed.	Script before resource deactivation completed.	-	o	o	o
rc	Information	1310	Script after deactivation in resource %1 started.	Script after resource deactivation started.	-	o	o	o
rc	Information	1311	Script after deactivation in resource %1 completed.	Script after resource deactivation completed.	-	o	o	o
rc	Error	1340	Script before final action upon activation failure in resource %1 failed.	Script before final action upon resource activation failure failed.	Check the cause of the script failure and take measures.	o	o	o				o
rc	Error	1341	Script before final action upon deactivation failure in resource %1 failed.	Script before final action upon resource deactivation failure failed.	Check the cause of the script failure and take measures.	o	o	o				o
rc	Error	1342	Failed to execute script before activation in resource %1.	Script before resource activation failed.	Check the cause of the script failure and take measures.	o	o	o				o
rc	Error	1343	Failed to execute script after activation in resource %1.	Script after resource activation has failed.	Check the cause of the script failure and take measures.	o	o	o				o
rc	Error	1344	Failed to execute script before deactivation in resource %1.	Script before resource deactivation failed.	Check the cause of the script failure and take measures.	o	o	o				o
rc	Error	1345	Failed to execute script after deactivation in resource %1.	Script after resource deactivation failed.	Check the cause of the script failure and take measures.	o	o	o				o
rc	Error	1346	Failed to log on as a user.	Logon as a user failed	Check if the domain, account and password of the execution user are correctly set.	o	o	o
rc	Information	1400	Forced stop (BMC Power Off) of server %1 has been requested.	forced-stop (bmc-poweroff) requested	-			o
rc	Information	1401	Forced stop (BMC Power Cycle) of server %1 has been requested.	forced-stop (bmc-powercycle) requested	-			o
rc	Information	1402	Forced stop (BMC Reset) of server %1 has been requested.	forced-stop (bmc-reset) requested	-			o
rc	Information	1403	Forced stop (BMC NMI) of server %1 has been requested.	forced-stop (bmc-nmi) requested	-			o
rc	Information	1404	Forced stop has been requested.	forced-stop (VMware vSphere CLI) requested	-			o
rc	Information	1405	Script for forced stop has started.	Script for forced-stop has started.	-			o
rc	Information	1406	Script for forced stop has completed.	Script for forced-stop has completed.	-			o
rc	Error	1420	Forced stop (BMC Power Off) of server %1 failed.	forced-stop (bmc-poweroff) failed	The system may not be able to operate properly.	o	o	o				o
rc	Error	1421	Forced stop (BMC Power Cycle) of server %1 failed.	forced-stop (bmc-powercycle) failed	The system may not be able to operate properly.	o	o	o				o
rc	Error	1422	Forced stop (BMC Reset) of server %1 failed.	forced-stop (bmc-reset) failed	The system may not be able to operate properly.	o	o	o				o
rc	Error	1423	Forced stop (BMC NMI) of server %1 failed.	forced-stop (bmc-nmi) failed	The system may not be able to operate properly.	o	o	o				o
rc	Error	1424	Forced stop failed.	forced-stop (VMware vSphere CLI) failed	The system may not be able to operate properly.	o	o	o				o
rc	Error	1425	Script for forced stop has failed. (%1)	Script for forced-stop has stopped.	Check the cause of the script failure and take measures.	o	o	o				o
rc	Error	1426	Script for forced stop has timed out.	Timeout on the-script for forced stop	Check the cause of the script timeout and take measures.	o	o	o				o
rc	Warning	1427	Group failover has been canceled because forced stop of server %1 failed.	Suppression of failover for forceed stop failed	Check the cause of the forced stop failure and take measures.	o	o	o
rc	Warning	1430	The group %1 which were activated on the server %2 will be activated on the same server because its reboot has been completed within the heartbeat timeout.	Server rebooted before the heartbeat timeout occurs.	Adjust the OS startup time so that the server reboot is not completed before the heartbeat timeout occurs.	o	o	o
rc	Information	1440	The CPU frequency has been set to high.	The CPU frequency has been set to high.	-	o	o	o
rc	Information	1441	The CPU frequency has been set to low.	The CPU frequency has been set to low.	-	o	o	o
rc	Information	1442	The CPU frequency has been set to %1.	The CPU frequency has been set.	-	o	o	o
rc	Information	1443	CPU frequency setting has been switched to automatic control by cluster.	CPU frequency setting has been switched to automatic control by cluster.	-	o	o	o
rc	Warning	1450	Cluster operation is disabled.	Cluster operation is disabled.	-	o	o	o
rc	Warning	1451	Ignored the automatic start of groups because automatic group startup is disabled.	Automatic group startup is not executed.	-	o	o	o
rc	Warning	1452	Ignored the recovery action in resource activation because recovery action caused by group resource activation error is disabled.	Resource recovery action is not executed.	-	o	o	o
rc	Warning	1453	Ignored the recovery action in resource deactivation because recovery action caused by group resource deactivation error is disabled.	Resource recovery action is not executed.	-	o	o	o
rc	Information	1454	Cluster operation is set disabled.	Cluster operation is disabled.	-	o	o	o
rc	Information	1455	Cluster operation is set enabled.	Cluster operation is enabled.	-	o	o	o
rc	Warning	1456	Cluster operation is forcibly disabled since a valid license has not been registered.	Cluster operation is forcibly disabled (License disabled).	Register the license. Canceling the forcible disablement of cluster operation requires up to 1 hour after the license is registered. To cancel it immediately, suspend and resume the cluster after the license registration.	o	o	o
rc	Information	1457	The forcible disablement of cluster operation was canceled since the valid licenses are registered.	Forcible disablement of cluster operation is canceled.	-	o	o	o
rc	Error	1460	CPU frequency control cannot be used.	CPU frequency control cannot be used.	Check BIOS settings and kernel settings.	o	o	o				o
rc	Error	1461	Failed to set the CPU frequency to high.	Setting the CPU frequency to high has failed.	Check BIOS settings and kernel settings. Check if the cluster service is started. Check if the configuration is set so that CPU frequency control is used.	o	o	o				o
rc	Error	1462	Failed to set the CPU frequency to low.	Setting the CPU frequency to low has failed.	Check BIOS settings and kernel settings. Check if the cluster service is started. Check if the configuration is set so that CPU frequency control is used.	o	o	o				o
rc	Error	1463	Failed to set the CPU frequency to %1.	Setting the CPU frequency has failed.	Check BIOS settings and kernel settings. Check if the cluster service is started. Check if the configuration is set so that CPU frequency control is used.	o	o	o				o
rc	Error	1464	Failed to switch the CPU frequency setting to automatic control by cluster.	Switching the CPU frequency setting to automatic control by cluster has failed.	Check if the cluster service is started. Check if the configuration is set so that CPU frequency control is used.	o	o	o				o
rc	Information	1470	Server %1 has been set as the destination for the group %2 (reason: %3).	destination found	-	o	o	o
rc	Warning	1471	There is no appropriate destination for the group %1 (reason: %2).	destination not found	Check if any monitor resources detects an error on the other servers.	o	o	o				o
rc	Warning	1472	Server %1 is not in a condition to start group %2 (reason: %3).	not in a condition to start group	Check if any monitor resources detects an error on the server.	o	o	o
rc	Error	1480	Group start has been canceled because waiting for group %1 to start has failed. (%2)	waiting for group to start failed	-	o	o	o
rc	Warning	1481	Waiting for group %1 to start has failed. However, group start continues. (%2)	waiting for group to start failed	-	o	o	o
rc	Error	1482	Group start has been canceled because waiting for group %1 to start has canceled.	waiting for group to start canceled	-	o	o	o
rc	Warning	1483	Waiting for group %1 to start has canceled. However, group start continues.	waiting for group to start canceled	-	o	o	o
rc	Error	1484	Group stop has been canceled because waiting for group %1 to stop has failed. (%2)	waiting for group to stop failed	-	o	o	o
rc	Warning	1485	Waiting for group %1 to stop has failed. However, group stop continues. (%2)	waiting for group to stop failed	-	o	o	o
rc	Error	1486	Group stop has been canceled because waiting for group %1 to stop has canceled.	waiting for group to stop canceled	-	o	o	o
rc	Warning	1487	Waiting for group %1 to stop has canceled. However, group stop continues.	waiting for group to stop canceled	-	o	o	o
rc	Information	1490	Group %1 started to check the double activation.	check the double activation started	-			o
rc	Information	1491	Group %1 completed to check the double activation.	check the double activation ended	-			o
rc	Error	1492	Group %1 failed to check the double activation.	check the double activation failed	Check the status of the group.	o	o	o				o
rc	Information	1493	Waiting for group %1 to start for check the double activation.	group start continues for check the double activation	Check the status of the group.	o	o	o
rm	Information	1501	Monitor %1 has been started.	Monitor start	-	o	o	o
rm	Information	1502	Monitor %1 has been stopped.	Monitor stop	-	o	o	o
rm	Information	1503	Monitor %1 does not monitor in this server.	Not target server	-	o	o	o
rm	Warning	1504	Monitor %1 is in the warning status. (%2 : %3)	Monitor warn	Check the cause of Warning.	o	o	o				o
rm	Warning	1505	The number of monitor resources reached the maximum number. (registered resource: %1)	invalid number of monitor resource	Check the cluster configuration data.	o	o	o				o
rm	Warning	1506	Configuration of %1 is invalid. (%2 : %3)	invalid monitor resource	Check the cluster configuration data.	o	o	o				o
rm	Error	1507	Failed to start monitor %1.	monitor starting failed	The system may not be able to operate properly.	o	o	o	o	o		o	o
rm	Error	1508	Failed to stop monitor %1.	monitor stopping failed	The system may not be able to operate properly.	o	o	o				o
rm	Error	1509	Monitor %1 detected an error. (%2 : %3)	monitor failed	Check the cause for monitor error.	o	o	o	o	o		o	o
rm	Information	1510	Monitor %1 is not monitored.	not monitored	-	o	o	o
rm	Information	1511	Monitor resource has not been registered.	unregistered monitor resource	-	o	o	o
rm	Information	1512	%1 was stopped for failure in monitor %2.	relation stop	-	o	o	o
rm	Information	1513	%1 was restarted for failure in monitor %2.	relation restart	-	o	o	o
rm	Information	1514	%1 was failed over for failure in monitor %2.	relation group failover	-	o	o	o
rm	Information	1515	There was a request to stop cluster for failure in monitor %1.	cluster stop	-	o	o	o
rm	Information	1516	There was a request to shut down the system for failure in monitor %1.	system shutdown	-	o	o	o
rm	Information	1517	There was a request to restart the system for failure in monitor %1.	system reboot	-	o	o	o
rm	Error	1518	Failed to stop %1 due to error detection of %2.	relation stop failure	Check the status of resources.	o	o	o				o
rm	Error	1519	Failed to restart %1 due to error detection of %2.	relation restart failure	Check the status of resources.	o	o	o				o
rm	Error	1520	Failed to fail over %1 due to error detection of %2.	relation group failover failure	Check the status of resources.	o	o	o				o
rm	Error	1521	Failed to stop the cluster due to error detection of %1.	cluster stop failure	The system may not be able to operate properly.	o	o	o				o
rm	Error	1522	Failed to shut down the system due to error detection of %1.	os shutdown failure	The system may not be able to operate properly.	o	o	o				o
rm	Error	1523	Failed to restart the system due to error detection of %1.	os reboot failure	The system may not be able to operate properly.	o	o	o				o
rm	Error	1524	The group of monitor %1 is unknown.	unknown group	Check the cluster configuration data.	o	o	o				o
rm	Warning	1525	No action is taken because %1 is not online.	not perform failure action	-	o	o	o				o
rm	Information	1526	Status of monitor %1 was returned to normal.	status changed into normal	-	o	o	o
rm	Information	1527	Status of monitor %1 was changed into unknown.	status changed into unknown	The system may not be able to operate properly.	o	o	o
rm	Error	1528	Initialization error has occurred (%1 : %2)	process initialize error	The system may not be able to operate properly.	o	o	o				o
rm	Information	1529	Monitor %1 was suspended.	suspend (single monitor)	-	o	o	o
rm	Information	1530	Monitor %1 was resumed.	resume (single monitor)	-	o	o	o
rm	Information	1531	All monitors were suspended.	suspend (all monitors)	-	o	o	o
rm	Information	1532	All monitors were resumed.	resume (all monitors)	-	o	o	o
rm	Information	1533	The polling interval of monitor %1 was changed into %2*%3.	change polling interval (single monitor)	-	o	o	o
rm	Information	1534	The polling interval ratio of all monitors were changed into %1.	change polling interval (all monitors)	-	o	o	o
rm	Information	1535	Causing intentional stop error was required because an error is detected by %1.	intentional panic	-	o	o	o
rm	Error	1536	Causing intentional stop error has failed because an error is detected by %1.	intentional panic failure	The system may not be able to operate properly.	o	o	o				o
rm	Warning	1537	Recovery will not be executed since server is suspending.	not recovery(server suspending)	Monitor resource is not recovered if the server is suspended (Network Partition Unsolved). Check the cause for being suspended (Network Partition Unsolved) and recover network partition resources to the normal status.	o	o	o				o
rm	Warning	1538	No action is taken because any recovery target is not online.	not recovery (all groups)	-	o	o	o
rm	Warning	1539	No action is taken because the group is set for the recovery target %1 is not online.	not recovery (group)	-	o	o	o
rm	Warning	1571	Monitor %1 was delayed. (timeout=%2, response time=%3, rate=%4)	monitor delayed	Check the load on the server where monitoring delay was detected and reduce the load. Set longer timeout if the monitoring timeout is detected.	o	o	o				o
rm	Warning	1572	Monitor %1 could not perform monitoring.	Delay in internal processing	The system may not be able to operate properly.	o	o	o
rm	Warning	1600	Shutdown count reached the maximum number (%1). Final action of monitor %2 was ignored.	reached OS shutdown limit	-	o	o	o	o	o		o	o
rm	Warning	1601	Since there is no other normally running server, the final action (%1) for the error detection of monitor resource %2 was suppressed.	Suppression of final action for error detection	-	o	o	o
rm	Information	1700	Script before action(%1) upon failure in %2 monitor resource started.	Script before final action upon monitor resource failure started.	-	o	o	o
rm	Information	1701	Script before action(%1) upon failure in %2 monitor resource completed.	Script before final action upon monitor resource failure completed.	-	o	o	o
rm	Information	1720	Script before action(%1) upon failure in %2 monitor resource failed.	Script before final action upon monitor resource failure has failed.	-	o	o	o
rm	Information	1750	The collecting of detailed information triggered by monitoring %1 error has been started (timeout=%2).	The collecting of detailed information has been started.	-	o	o	o
rm	Information	1751	The collection of detailed information triggered by monitoring %1 error has been completed.	The collection of detailed information has been completed.	-	o	o	o
rm	Information	1752	The collection of detailed information triggered by monitoring %1 error has been failed (%2).	The collection of detailed information has been failed.	-	o	o	o
rm	Information	1800	The %1 service will be started by cluster system.	start service	-	o	o	o
rm	Information	1801	The %1 service will be started again because the service has been stopped by cluster system. (retry: %2/%3)	start service (retry)	-	o	o	o
rm	Information	1802	The %1 service will be resumed by cluster system.	resume service	-	o	o	o
rm	Information	1803	The %1 service will be resumed again because the service has been suspended by cluster system. (retry: %2/%3)	resume service (retry)	-	o	o	o
rm	Information	1804	The %1 service will be stopped by cluster system.	stop service	-	o	o	o
rm	Information	1805	The %1 service entered the running state.	service running	-	o	o	o
rm	Information	1806	The %1 service entered the stopped state.	service stopped	-	o	o	o
rm	Warning	1811	Start request of the %1 service failed. Check the service status.	failed to start service	Check the service status.	o	o	o
rm	Warning	1812	Resume request of the %1 service failed. Check the service status.	failed to resume service	Check the service status.	o	o	o
rm	Warning	1813	Stop request of the %1 service failed. Check the service status.	failed to stop the service	Check the service status.	o	o	o
rm	Warning	1816	The %1 service has been stopped by other than cluster system.	service stopped (error)	Check the cause of the service stopped.	o	o	o
rm	Warning	1817	The %1 service has been suspended by other than cluster system.	service suspended (error)	Check the cause of the service suspended.	o	o	o
rm	Warning	1819	Start or resume retry count for the %1 service exceeded the threshold (%2).	start or resume retry count exceeded the threshold	-	o	o	o
rm	Information	1820	The cluster will be stopped because there was a failure in %1 service monitoring.	cluster stop (failure in service monitoring)	-	o	o	o
rm	Information	1821	The system will be shut down because there was a failure in %1 service monitoring.	system shut down (failure in service monitoring)	-	o	o	o
rm	Information	1822	The cluster will be rebooted because there was a failure in %1 service monitoring.	system reboot (failure in service monitoring)	-	o	o	o
rm	Error	1870	Monitor resource %1 can not be controlled because the license is invalid.	cannot control monitor (invalid license)	Check if the license is registered or the license is valid.	o	o	o
rm	Information	1890	Recovery script has executed because an error was detected in monitoring %1.	Recovery script upon monitor resource failure executed		o	o	o
rm	Error	1891	Attempted to execute recovery script due to the error detected in monitoring %1, but failed.	failed to execute recovery script	Check the cause of the recovery script failure and take measures.	o	o	o
rm	Error	1892	Failed to log on as a user.	Logon as a user failed	Check if the domain, account and password of the execution user are correctly set.	o	o	o
rm	Information	1910	Dummy Failure of monitor resource %1 is enabled.	enable dummy failure	-	o	o	o
rm	Information	1911	Dummy Failure of monitor resource %1 is disabled.	disable dummy failure	-	o	o	o
rm	Information	1912	Dummy Failure of all monitors will be enabled.	enable dummy failure (all monitors)	-	o	o	o
rm	Information	1913	Dummy Failure of all monitors will be disabled.	disable dummy failure (all monitors)	-	o	o	o
rm	Warning	1914	An attempt was made to enable Dummy Failure of monitor resource %1, but failed.	failed to enable dummy failure	-	o	o	o
rm	Warning	1915	An attempt was made to disable Dummy Failure of monitor resource %1, but failed.	failed to disable dummy failure	-	o	o	o
rm	Information	1930	Recovery action caused by monitor resource error is disabled.	disable recovery action caused by monitor resource error	-	o	o	o
rm	Information	1931	Recovery action caused by monitor resource error is enabled.	enable recovery action caused by monitor resource error	-	o	o	o
rm	Warning	1932	Ignored the recovery action in monitoring %1 because recovery action caused by monitor resource error is disabled.	not recovery (recovery action caused by monitor resource error has disabled)	-	o	o	o
rm	Warning	1933	Recovery action at timeout occurrence was disabled, so the recovery action of monitor %1 was not executed.	disable recovery action caused by monitor resource timeout	-	o	o	o
diskagent	Information	2001	%1 service was started.	Start service	-		o	o
diskagent	Information	2002	%1 service was stopped.	Stop service	-		o	o
diskagent	Warning	2030	%1 service was not stopped successfully due to stop timeout or other errors of the internal threads.	Fail to stop service	The system may not be able to operate properly.	o	o	o				o
diskagent	Error	2050	%1 service was not started successfully because the specified parameter was invalid. Confirm the cluster configuration data.	Fail to start service	Check the cluster configuration data.	o	o	o				o
diskagent	Error	2051	%1 service was not started because obtaining the policy data failed. Check the data.	Fail to start service	Check the policy file.	o	o	o				o
diskagent	Error	2052	%1 service was not started successfully because dispatching to service manager failed. System may be unable to operate correctly.	Fail to start service	The system may not be able to operate properly.	o	o	o				o
diskagent	Error	2053	%1 service was not started successfully because creating and loading internal resources failed. System may be unable to operate correctly.	Fail to start service	System may be unable to operate correctly.	o	o	o				o
diskagent	Error	2054	%1 service was not started successfully because initialization of shared disk or mirror disk library failed at exit code %2. System may be unable to operate correctly.	Fail to start service	The system may not be able to operate properly.	o	o	o				o
diskagent	Error	2055	%1 service was not started successfully because creating communication socket failed. System may be unable to operate correctly.	Fail to start service	The system may not be able to operate properly.	o	o	o				o
diskagent	Error	2056	%1 service was not started successfully because creating internal threads failed. System may be unable to operate successfully.	Fail to start service	The system may not be able to operate properly.	o	o	o				o
diskagent	Error	2057	%1 service was not started because it may be stopped or forcibly stopped last time when it was started. Reboot the server.	Fail to start service	Reboot the server.	o	o	o				o
diskagent	Error	2090	%1 service failed to reload cluster configuration data. System may be unable to operate correctly. The own server will be shut down.	Server shutdown	The system may not be able to operate properly.	o	o	o				o
diskagent	Error	2099	%1 service was not started successfully because the other internal error occurred. System may be unable to operate correctly.	Fail to start service	The system may not be able to operate properly.	o	o	o				o
event	Information	2101	%1 service has been started.	Start service	-		o
event	Information	2102	%1 service has been stopped.	Stop service	-		o
event	Warning	2130	Timeout or other error has occurred while waiting for internal threads to stop. Detected internal error %1.	Threads were timeout	The system may not be able to operate properly.	o	o					o
event	Error	2150	The specified parameters are invalid. Check the cluster configuration data.	Invalid configuration	Check the cluster configuration data.	o	o					o
event	Error	2151	Failed to obtain the policy data. Check the data.	Invalid configuration	Check the policy file.	o	o					o
event	Error	2152	Failed to obtain the registry data. System may be unable to operate correctly.	Failed to read registry	The system may not be able to operate properly.	o	o					o
event	Error	2153	Failed to dispatch to the service manager. System may be unable to operate correctly.	Dispatch failed	The system may not be able to operate properly.	o	o					o
event	Error	2154	Failed to create an internal resource. System may be unable to operate correctly.	failed to resource creation	The system may not be able to operate properly.	o	o					o
event	Error	2155	Failed to create communication sockets. System may be unable to operate correctly.	failed to socket creation	The system may not be able to operate properly.	o	o					o
event	Error	2156	Failed to control the shared memory. System may be unable to operate correctly.	failed to shared memory control	The system may not be able to operate properly.	o	o					o
event	Error	2157	Failed to generate internal threads. System may be unable to operate correctly.	failed to thread creation	The system may not be able to operate properly.	o	o					o
event	Error	2199	Other internal error has occurred. System may be unable to operate correctly.	Internal Error	The system may not be able to operate properly.	o	o					o
trnsv	Error	2301	There was a notification from external (IP=%1), but it was denied.	Connection limit by client IP address	Check the client IP address from which the connection is permitted.	o	o	o
trnsv	Information	2310	There was a notification (%1) from external (IP=%2).	Received an abnormity occurrence notification from outside	-	o	o	o
trnsv	Information	2320	Recovery action (%1) of monitoring %2 has been executed because a notification arrived from external.	Executed the recovery action at abnormity occurrence	-	o	o	o
trnsv	Information	2321	Recovery action (%1) of monitoring %2 has been completed.	Completed the recovery action at abnormity occurrence	-	o	o	o
trnsv	Error	2322	Attempted to recovery action (%1) of monitoring %2 due to the notification from external, but failed.	Failed to execute the recovery action at abnormity occurrence	Make sure that the recovery action on the environment is executable.	o	o	o
trnsv	Information	2330	Action (%1) has been completed.	The requested action completed	-	o	o	o
trnsv	Error	2331	Attempted to execute action (%1), but it failed.	The requested action Failed	Make sure that the recovery action is an executable environment.	o	o	o
trnsv	Information	2340	Script before action of monitoring %1 has been executed.	Script execution started	-	o	o	o
trnsv	Information	2341	Script before action of monitoring %1 has been completed.	Script execution completed	-	o	o	o
trnsv	Error	2342	Attempted to execute script before action of monitoring %1, but it failed.	Script execution failed	Handle the problem after making sure the cause of script failure.	o	o	o
trnsv	Error	2350	The system will be shutdown because cluster resume was failed.	Failed to resume the cluster daemon	-	o	o	o
trnsv	Error	2351	An attempt to shutdown the system failed.	Failed to shutdown the system	The system may not be able to operate properly.	o	o	o
mdadmn	Information	2401	Full Recovery of mirror disk %1 started.	Full Recovery of mirror disk started	-	o	o	o
mdadmn	Information	2402	Full Recovery of mirror disk %1 finished successfully.	Full Recovery of mirror disk succeeded	-	o	o	o
mdadmn	Information	2403	Full Recovery of mirror disk %1 was canceled.	Full Recovery of mirror disk was canceled.	-	o	o	o
mdadmn	Error	2404	Full Recovery of mirror disk %1 failed.	Full Recovery of mirror disk failed.	Make sure there is no error in the disk and network adapter and the network is correctly connected.	o	o	o			o	o
mdadmn	Information	2405	Fast Recovery of mirror disk %1 started.	Fast Recovery of mirror disk started	-	o	o	o
mdadmn	Information	2406	Fast Recovery of mirror disk %1 finished successfully.	Fast Recovery of mirror disk succeeded	-	o	o	o
mdadmn	Information	2407	Fast Recovery of mirror disk %1 was canceled.	Fast Recovery of mirror disk was canceled	-	o	o	o
mdadmn	Error	2408	Fast Recovery of mirror disk %1 failed.	Fast Recovery of mirror disk failed	Make sure there is no error in the disk and network adapter and the network is correctly connected.	o	o	o			o	o
mdadmn	Warning	2411	Trying again to disconnect mirror disk %1. Check if the mirror disk is being used.	Disconnection of mirror disk is being retried.	Check if the mirror disk is being used.	o	o	o				o
mdadmn	Information	2412	Mirror disk %1 was forcibly disconnected.	mirror disk was forcibly disconnected.	-	o	o	o
mdadmn	Error	2422	A data partition error occurred in the mirror disk %1.	mirror disk abnormal	Replace the server disk.	o	o	o			o	o
mdadmn	Error	2423	A cluster partition error occurred in the mirror disk %1.	Disk error	Replace the server disk.	o	o	o			o	o
mdadmn	Error	2431	Failed to initialize the mirror disk connect.	Mirror disk connection initialization failed	Make sure there is no error in the network adapter and the network is correctly connected.	o	o	o			o	o
mdadmn	Error	2432	Failed to initialize the mirror disk %1.	Mirror disk initialization failed.	Check the partition exists and the disk is recognized by the operating system.	o	o	o			o	o
mdadmn	Error	2433	Failed to initialize the mirror disk %1. The cluster partition and the data partition must be different partitions.	Mirror disk initialization failed.	Check the cluster configuration data.	o	o	o				o
mdadmn	Error	2434	Failed to initialize the mirror disk %1. The area in the cluster partition has been used by another mirror disk.	Mirror disk initialization failed.	Check the cluster configuration data.	o	o	o				o
mdadmn	Error	2435	Failed to initialize the mirror disk %1. The partition specified for the cluster partition has been used as the data partition of another mirror disk.	Mirror disk initialization failed.	Check the cluster configuration data.	o	o	o				o
mdadmn	Error	2436	Failed to initialize the mirror disk %1. The partition specified for the data partition has been used by another mirror disk.	Mirror disk initialization failed.	Check the cluster configuration data.	o	o	o				o
mdadmn	Error	2440	Connecting mirror disk %1 has failed.	Connecting mirror disk failed.	Check the partition exists and the disk is recognized by the operating system.		o				o	o
mdadmn	Error	2441	Disconnecting mirror disk %1 has failed.	Disconnecting mirror disk failed.	Check if the mirror disk is being used.		o					o
mdadmn	Warning	2442	The mirror disk connect of mirror disk %1 has been changed.(Priority%2->%3)	The mirror disk connect has been switched due to disconnection of the active mirror disk connect.	Make sure there is no error in the network adapter and the network is correctly connected.	o	o	o
mdadmn	Error	2443	Disconnecting mirror disk %1 has failed while it is being copied. The server is shut down to protect data.	Failed sending server closing due to process access Execution of emergency shutdown by process access	The mirror disk may be in use. Check the mirror disk.	o	o	o			o	o
mdadmn	Information	2450	Extending the mirror disk(%1) finished successfully. (size:%2 Bytes)	Extending the data partition of mirror disk resource succeeded.	-	o	o	o
mdadmn	Error	2451	Extending the mirror disk(%1) has failed.	Extending the data partition of mirror disk resource failed	Check if the status of mirror disk is normal or if there is free space necessary for extension.	o	o	o
mdadmn	Information	2455	Updated the encryption key of mirror disk %1 successfully.	Updating the encryption key succeeded. %1: Mirror disk name	-	o	o	o
mdadmn	Error	2456	Failed to update the encryption key of mirror disk %1.	Updating the encryption key failed. %1: Mirror disk name	Check if the key file exists in the configured key file full path on each server.	o	o	o
mdadmn	Error	2457	Update the encryption key of mirror disk %1.	Prompt to update the encryption key. %1: Mirror disk name	Update the encryption key.	o	o	o
mdadmn	Warning	2458	The mirror disk connection of mirror disk %1 is disconnected.	Mirror disk connection error. %1: Mirror disk name	Check if there is an error with the network adopter or the network is properly connected.	o	o	o
lankhb	Error	2851	Keep-alive timeout was detected on the server %1.	Keep-alive timeout	There is a server where keep-alive timeout is detected. Check the server error.	o	o	o				o
lankhb	Error	2852	STOP error was detected on the server %1. (source:%2, exit code:%3)	STOP error	There is a server where STOP error is detected. Remove the failure of the server.	o	o	o				o
lankhb	Error	2853	Hardware reset was detected on the server %1. (source:%2, exit code:%3)	Hardware reset	There is a server where hardware reset is detected. Remove the failure of the server.	o	o	o				o
fip	Error	2901	IP address already exists. (IP=%1)	address duplication	-	o	o	o
fip	Information	2902	IP address will be activated forcibly. (IP=%1)	address force activation	-	o	o	o
vip	Error	3051	IP address already exists. (IP=%1)	address duplication	-	o	o	o
vip	Information	3052	IP address will be activated forcibly. (IP=%1)	address force activation	-	o	o	o
sdfunc	Warning	3201	Trying again to disconnect disk %1. Check if the disk is being used.	Retry disk disconnection	Check if the disk is being used.	o	o	o				o
sdfunc	Information	3202	Disk %1 was forcibly disconnected.	Disconnect disk forcibly	-	o	o	o
sdfunc	Warning	3203	Updated configuration data was not reflected properly. Update the configuration data again after modifying the configuration settings.	Fail to update configuration	Check whether the cluster configuration information, specifically the HBA setting and the letter of the drive and GUID data for the disk NP resolution resource and disk resources for each server, matches the current disk configuration of each server.	o	o	o				o
sdfunc	Warning	3204	The server %1 is not found in the configuration data. Check the server name of the configuration data.	Fail to detect server name	Check the cluster configuration data.	o	o	o				o
sdfunc	Information	3205	Detected disk resources that have not been identified. Disk reidentification will be executed.	Execute disk reconfirmation	-	o	o	o
sdfunc	Information	3206	Reidentification of the disk has finished.	Finish disk reconfirmation	-	o	o	o
sdfunc	Error	3207	Connecting disk %1 has failed.	Fail to connect disk	Check if the partition is allocated and the disk is being recognized by operating system.		o				o	o
sdfunc	Error	3208	Disconnecting disk %1 has failed.	Fail to disconnect disk	Check if the disk is being used.		o					o
disknp	Warning	3251	Timeout has occurred in read/write to the partition for disk heartbeat. Check the connection status of partition for disk heartbeat.	Disk heart beat timeout	Make sure there is no error in the disk and it is correctly connected .	o	o	o			o	o
disknp	Information	3252	Recovered from the timeout occurred in read/write to the partition for disk heartbeat.	Recover from disk heartbeat timeout	-	o	o	o
disknp	Error	3257	Disconnection monitoring(%1) among the shared disk and the servers could not be started. The system may not be able to operate properly.	Fail to start monitoring	The system may not be able to operate properly.	o	o	o				o
ptun	Warning	3301	The parameter (%1) exceeded the threshold (%2 p.c.). Timeout value=%3(sec) Data=%4(sec)	Delay warning	The parameter exceeded the threshold. Set an appropriate value to the parameter.	o	o	o				o
ptun	Warning	3302	The parameter (%1) exceeded the threshold (%2 p.c.). Timeout value=%3 Data=%4 Server=%5 Resource=%6	Delay warning	The parameter exceeded the threshold. Set an appropriate value to the parameter.	o	o	o				o
armcmd	Error	3501	ARMLOAD detected that the application (watchID=%2) of the group %1 has stopped. The number of failovers has reached the maximum count. Check what has caused the application to stop.	Application stopped	Check the cause for application to be stopped.	o	o					o
armcmd	Error	3502	ARMLOAD detected that the application (watchID=%2) of the group %1 has stopped. Script will be restarted. Check what has caused the application to stop.	Application stopped	Check the cause for application to be stopped.	o	o					o
armcmd	Error	3503	ARMLOAD detected that the application (watchID=%2) of the group %1 has stopped. The application will be restarted. Check what has caused the application to stop.	Application stopped	Check the cause for application to be stopped.	o	o					o
armcmd	Error	3504	ARMLOAD detected that the application (watchID=%2) of the group %1 has stopped. Group will be failed over. Check what has caused the application to stop.	Application stopped	Check the cause for application to be stopped.	o	o					o
armcmd	Error	3505	ARMLOAD detected that the application (watchID=%2) of the group %1has stopped. The server will shut down. Check what has caused the application to stop.	Application stopped	Check the cause for application to be stopped.	o	o					o
armcmd	Error	3506	ARMLOAD detected that the service (watchID=%2) of the group %1 has stopped. The number of failovers has reached the maximum count. Check what has caused the application to stop.	Service stopped	Check the cause for service to be stopped.	o	o					o
armcmd	Error	3507	ARMLOAD detected that the service (watchID=%2) of the group %1 has stopped. Script will be restarted. Check what has caused the application to stop.	Service stopped	Check the cause for service to be stopped.	o	o					o
armcmd	Error	3508	ARMLOAD detected that the service (watchID=%2) of the group %1 has stopped. The service will be restarted. Check what has caused the application to stop.	Service stopped	Check the cause for service to be stopped.	o	o					o
armcmd	Error	3509	ARMLOAD detected that the service (watchID=%2) of the group %1 has stopped. The group will be failed over. Check what has caused the application to stop.	Service stopped	Check the cause for service to be stopped.	o	o					o
armcmd	Error	3510	ARMLOAD detected that the service (watchID=%2) of the group %1 has stopped. The server will shut down. Check what has caused the application to stop.	Service stopped	Check the cause for service to be stopped.	o	o					o
armcmd	Error	3513	An error occurred in command %1. Shut down the server.	Command error	The system may not be able to operate properly.	o	o					o
armcmd	Warning	3514	An abnormal connection to the shared name (%1) has been detected.	Share-name abnormally	The shared name cannot be used. Recover the devices that correspond to the shared name. (1) OS is unstable. Check the OS status. (2) Check if the power is supplied to the appropriate devices. (3) Check if the appropriate devices and the servers are connected properly.	o	o					o
armcmd	Information	3515	Connection to the shared name (%1) has been recovered.	Share-name recovered	-	o	o
armcmd	Warning	3516	Failed to start the application (WID=%2) of the group %1.	Application failed	Check the cause for failing to start the application.	o	o					o
armcmd	Information	3517	The application (WID=%2) of the group %1 has restarted.	Application restarted	-	o	o
armcmd	Warning	3518	Failed to start the service (WID=%2) of the group %1.	Service failed	Check the cause for failing to start the service.	o	o					o
armcmd	Information	3519	The service (WID=%2) of the group %1 has restarted.	Service restarted	-	o	o
armcmd	Error	3520	Failed to fail over the group %1. Check whether the server where the group can fail over exists.	Fail over failed	There may not be a server where the group can fail over.	o	o					o
lcns	Information	3551	The trial license is valid until %1. (Product name:%2)	Trial version license (normal)	-	o	o
lcns	Error	3552	The trial license has expired in %1. (Product name:%2)	Trial version license (expired)	Register the license.	o	o	o				o
lcns	Warning	3553	The number of licenses is insufficient. The number of insufficient licenses is %1. (Product name:%2)	Insufficient	Register the license.	o	o					o
lcns	Error	3554	The license is not registered. (Product name:%1)	Not registered	Register the license.	o	o	o				o
lcns	Error	3555	The same license is registered with other servers. (Product name:%1)	Repetition registered	Delete the overlapping license.	o	o	o				o
lcns	Error	3556	Manufacturer or model of this server is invalid.	Invalid manufacturer or model	Confirm the manufacturer or model.	o	o	o				o
lcns	Error	3558	The registered license is invalid. (Product name:%1, Serial No:%2)	The license is invalid.	Register the valid lincense.	o	o	o				o
lcns	Information	3559	The fixed term license is effective until %1. (Product name:%2)	Fixed term license (normal)	-	o	o
lcns	Error	3560	The fixed term license has expired in %1. (Product name:%2)	Fixed term license (expired)	Register the license.	o	o	o				o
logcmd	Information	3601		log command	-	o	x	x	x	x	x	x	x
sdw / hdtw	Warning	3651	Monitor %1 was delayed. (timeout=%2 response time=%3 rate=%4)	Monitoring is delayed		o	o	o				o
sdw / hdtw	Error	3652	Cannot access the disk (%1).	Disconnection is detected.	Make sure there is no error in the disk and the shared disk is correctly connected.		o				o	o
sdw / hdtw	Information	3653	Recovered the status where access to the disk (%1) is possible.	Recovery from disconnection has been done.	-		o
diskw	Warning	3701	Monitor %1 was delayed. (timeout=%2 response time=%3 rate=%4)	monitor delayed	-	o	o	o				o
userw	Warning	3711	Monitor %1 was delayed. (timeout=%2 response time=%3 rate=%4)	monitor delayed	-	o	o	o				o
vcom	Error	3751	Failed to register the virtual computer name (%1) to the DNS server.	Failed to register the virtual computer name	Make sure there is no error on the DNS server, or a trouble occurred in communicating with the DNS server.	o	o
vcom	Error	3752	Failed to delete the virtual computer name (%1) from the DNS server.	Failed to delete the virtual computer name	Make sure there is no error on the DNS server, or a trouble occurred in communicating with the DNS server.	o	o
hdadmn	Information	3851	Full Recovery of hybrid disk %1 started.	Full Recovery of hybrid disk started	-	o	o	o
hdadmn	Information	3852	Full Recovery of hybrid disk %1 finished successfully.	Full Recovery of hybrid disk succeeded	-	o	o	o
hdadmn	Information	3853	Full Recovery of hybrid disk %1 was canceled.	Full Recovery of hybrid disk was canceled	-	o	o	o
hdadmn	Error	3854	Full Recovery of hybrid disk %1 failed.	Full Recovery of hybrid disk failed	Make sure there is no error in the disk and network adapter and the network is correctly connected.	o	o	o			o	o
hdadmn	Information	3855	Fast Recovery of hybrid disk %1 started.	Fast Recovery of hybrid disk started	-	o	o	o
hdadmn	Information	3856	Fast Recovery of hybrid disk %1 finished successfully.	Fast Recovery of hybrid disk succeeded	-	o	o	o
hdadmn	Information	3857	Fast Recovery of hybrid disk %1 was canceled.	Fast Recovery of hybrid disk was canceled	-	o	o	o
hdadmn	Error	3858	Fast Recovery of hybrid disk %1 failed.	Fast Recovery of hybrid disk failed	Make sure there is no error in the disk and network adapter and the network is correctly connected.	o	o	o			o	o
hdadmn	Warning	3859	Trying again to disconnect hybrid disk %1. Check if the hybrid disk is being used.	Disconnection of hybrid disk is being retried	Check if the hybrid disk is being used.	o	o	o				o
hdadmn	Information	3860	Hybrid disk %1 was forcibly disconnected.	Hybrid disk was forcibly disconnected.	-	o	o	o
hdadmn	Error	3862	A data partition error occurred in the hybrid disk %1.	disk error	Replace the server disk.	o	o	o			o	o
hdadmn	Error	3863	A cluster partition error occurred in the hybrid disk %1.	disk error	Replace the server disk.	o	o	o			o	o
hdadmn	Error	3864	Failed to initialize the mirror disk connect.	Mirror disk connection initialization failed	Make sure there is no error in the network adapter and the network is correctly connected.	o	o	o			o	o
hdadmn	Error	3865	Failed to initialize the hybrid disk %1.	Hybrid disk initialization failed	Check the partition exists and the disk is recognized by the operating system.	o	o	o			o	o
hdadmn	Error	3866	Failed to initialize the hybrid disk %1. The cluster partition and the data partition must be different partitions.	Hybrid disk initialization failed	Check the cluster configuration data.	o	o	o				o
hdadmn	Error	3867	Failed to initialize the hybrid disk %1. The area in the cluster partition has been used by another hybrid disk.	Hybrid disk initialization failed	Check the cluster configuration data.	o	o	o				o
hdadmn	Error	3868	Failed to initialize the hybrid disk %1. The partition specified for the cluster partition has been used as the data partition of another hybrid disk.	Hybrid disk initialization failed	Check the cluster configuration data.	o	o	o				o
hdadmn	Error	3869	Failed to initialize the hybrid disk %1. The partition specified for the data partition has been used by another hybrid disk.	Hybrid disk initialization failed	Check the cluster configuration data.	o	o	o				o
hdadmn	Error	3870	Connecting hybrid disk %1 has failed.	Connecting hybrid disk failed	Check the partition exists and the disk is recognized by the operating system.		o				o	o
hdadmn	Error	3871	Disconnecting hybrid disk %1 has failed.	Disconnecting hybrid disk failed	Check if the hybrid disk is being used.		o					o
hdadmn	Information	3872	Detected a disk resource that has not been identified. Disk reidentification will be executed.	Disk reidentification starts	-	o	o	o
hdadmn	Information	3873	Reidentification of the disk has finished.	Disk reidentifcaiton finished.	-	o	o	o
hdadmn	Error	3874	A fatal error has occurred during control hybrid disk %1. Shutdown the server.	Fatal error has occurred	Make sure there is no error in the disk and network adapter and the network is correctly connected.	o	o	o			o	o
hdadmn	Warning	3875	The mirror disk connect of hybrid disk %1 has been changed. (Priority %2 -> %3)	The mirror disk connect has been switched due to disconnection of the active mirror disk connect.	Make sure there is no error in the network adapter and the network is correctly connected.	o	o	o
hdadmn	Error	3876	Disconnecting hybrid disk %1 has failed while it is being copied. The server is shut down to protect data.	Failed sending server closing due to process access Execution of emergency shutdown by process access	The hybrid disk may be in use. Check the mirror disk.	o	o	o			o	o
hdadmn	Warning	3880	The mirror disk connect of hybrid disk %1 has been disconnected.	An error occurred in the mirror disk connect.	Make sure there is no error in the network adapter and the network is correctly connected.	o	o	o
hdadmn	Warning	3881	The Auto mirror recovery check box is not selected. It is necessary to recover the mirror manually, in order to resume mirring (%1).	It is necessary to recover the mirror manually, in order to resume mirroring.	Recover a mirror from the command or Mirror disks.	o	o	o	o				o
hdadmn	Information	3885	Updated the encryption key of hybrid disk %1 successfully.	Updating the encryption key succeeded. %1: Hybrid disk Name	-	o	o	o
hdadmn	Error	3886	Failed to update the encryption key of hybrid disk %1.	Updating the encryption key failed. %1: Hybrid disk name	Check if the key file exists in the configured key file full path on each server.	o	o	o
hdadmn	Error	3887	Update the encryption key of hybrid disk %1.	Notification of necessary update of the encryption key. %1: Hybrid disk name	Update the encryption key.	o	o	o
hdfunc	Warning	3859	Trying again to disconnect hybrid disk %1. Check if the hybrid disk is being used.	Disconnection of hybrid disk is being retried	Check if the hybrid disk is being used.	o	o	o				o
hdfunc	Information	3860	Hybrid disk %1 was forcibly disconnected.	Hybrid disk was forcibly disconnected.	-	o	o	o
hdtw	Warning	4001	Monitor %1 was delayed. (timeout=%2 response time=%3 rate=%4)	Monitoring is delayed	-	o	o	o				o
hdtw	Error	4002	Cannot access the disk (%1).	Disconnection is detected.	Make sure there is no error in the disk and the shared disk is correctly connected.		o				o	o
hdtw	Information	4003	Recovered the status where access to the disk (%1) is possible.	Recovery from disconnection has been done.	-		o
mail	Error	4101	mail failed(%1).(SMTP server: %2)	Mail failed	Make sure there is no error in the SMTP server and no problem communicating with the SMTP server.	o	o	o				o
mail	Information	4102	mail succeed.(SMTP server: %1)	Mail succeeded	-		o	o
lamp	Information	4151	Notice by the network warming light succeeded.	Network warning light succeeded	-	o	o	o
lamp	Error	4152	Error in network warning light notice command.(%1)	Network warning light failed	Take appropriate action by following the error code.	o	o	o				o
lamp	Error	4153	Failed to execute warning light command.(%1)	Network warning light failed	The system may not be able to operate properly.	o	o	o				o
cifs	Information	4201	Created new shared configuration file.	Created new shared configuration file.	-	o	o	o
cifs	Warning	4202	Failed to read in shared configuration file. File may be corrupted.	Reading shared configuration file failed.	Check if the shared configuration file is corrupted.	o	o	o
cifs	Information	4203	Recovered shared configuration file from backup file.	Shared configuration file is restored.	-	o	o	o
cifs	Warning	4204	Recreated shared configuration file since it cannot be found.	Shared configuration file is created again.	This is a normal action at first activation. In other cases, check if the shared configuration file is not deleted.	o	o	o
cifs	Warning	4205	There are differences between share settings stored in shared configuration file and the current configuration settings.	Sharing target folder is lost.	Check if the shared folder is not deleted while CIFS resource is deactivated.	o	o	o
cifs	Information	4206	Failed to get shared folder account information	Failed to get shared folder account information	Check if a deleted group or user is set in Permissions for the shared folder.	o	o	o
apisv	Information	4301	There was a request to stop cluster from the %1(IP=%2).	Cluster stop	-	o		o
apisv	Information	4302	There was a request to shutdown cluster from the %1(IP=%2).	Cluster shutdown	-	o		o
apisv	Information	4303	There was a request to reboot cluster from the %1(IP=%2).	Cluster restart	-	o		o
apisv	Information	4304	There was a request to suspend cluster from the %1(IP=%2).	Cluster suspend	-	o		o
apisv	Information	4310	There was a request to stop server from the %1(IP=%2).	Cluster service stop	-	o		o
apisv	Information	4311	There was a request to shutdown server from the %1(IP=%2).	Shutdown	-	o		o
apisv	Information	4312	There was a request to reboot server from the %1(IP=%2).	Restart	-	o		o
apisv	Information	4330	There was a request to start group(%1) from the %2(IP=%3).	Group start	-	o		o
apisv	Information	4331	There was a request to start all groups from the %1(IP=%2).	All group start	-	o		o
apisv	Information	4332	There was a request to stop group(%1) from the %2(IP=%3).	Group stop		o		o
apisv	Information	4333	There was a request to stop all groups from the %1(IP=%2).	All group stop	-	o		o
apisv	Information	4334	There was a request to restart group(%1) from the %2(IP=%3).	Group restart	-	o		o
apisv	Information	4335	There was a request to restart all groups from the %1(IP=%2).	All group restart	-	o		o
apisv	Information	4336	There was a request to move group(%1) from the %2(IP=%3).	Group move	-	o		o
apisv	Information	4337	There was a request to move all groups from the %1(IP=%2).	All group move	-	o		o
apisv	Information	4338	There was a request to failover group(%1) from the %2(IP=%3).	Group failover	-	o		o
apisv	Information	4339	There was a request to failover all groups from the %1(IP=%2).	All group failover	-	o		o
apisv	Information	4340	There was a request to migrate group(%1) from the %2(IP=%3).	Group migration	-	o		o
apisv	Information	4341	There was a request to migrate all groups from the %1(IP=%2).	All group migration	-	o		o
apisv	Information	4342	There was a request to failover all groups from the %1(IP=%2).	All group failover	-	o		o
apisv	Information	4343	There was a request to cancel waiting for the dependence destination group of group %1 was issued from the %2.	Cancel waiting	-	o		o
apisv	Information	4350	There was a request to start resource(%1) from the %2(IP=%3).	Resource start	-	o		o
apisv	Information	4351	There was a request to start all resources from the %1(IP=%2).	All resource start	-	o		o
apisv	Information	4352	There was a request to stop resource(%1) from the %2(IP=%3).	Resource stop	-	o		o
apisv	Information	4353	There was a request to stop all resources from the %1(IP=%2).	All resource stop	-	o		o
apisv	Information	4354	There was a request to restart resource(%1) from the %2(IP=%3).	Resource restart	-	o		o
apisv	Information	4355	There was a request to restart all resources from the %1(IP=%2).	All resource restart	-	o		o
apisv	Information	4360	There was a request to suspend monitor resources from the %1(IP=%2).	Monitor temporary stop	-	o		o
apisv	Information	4361	There was a request to resume monitor resources from the %1(IP=%2).	Monitor restart	-	o		o
apisv	Information	4362	There was a request to enable Dummy Failure of monitor resource(%1) from the %2(IP=%3).	Dummy Failure enabled	-	o		o
apisv	Information	4363	There was a request to disable Dummy Failure of monitor resource(%1) from the %2(IP=%3).	Dummy Failure disabled	-	o		o
apisv	Information	4364	There was a request to disable Dummy Failure of all monitor resources from the %1(IP=%2).	All Dummy Failure disabled	-	o		o
apisv	Information	4370	There was a request to set CPU frequency from the %1(IP=%2).	CPU clock control	-	o		o
apisv	Error	4401	A request to stop cluster was failed(%1).	Cluster stop failure	Check the cluster status.	o		o
apisv	Error	4402	A request to shutdown cluster was failed(%1).	Cluster shutdown failure	Check the cluster status.	o		o
apisv	Error	4403	A request to reboot cluster was failed(%1).	Cluster restart failure	Check the cluster status.	o		o
apisv	Error	4404	A request to suspend cluster was failed(%1).	Cluster suspend failure	Check the cluster status.	o		o
apisv	Error	4410	A request to stop server was failed(%1).	Cluster service stop failure	Check the cluster status.	o		o
apisv	Error	4411	A request to shutdown server was failed(%1).	Server shutdown failure	Check the server status.	o		o
apisv	Error	4412	A request to reboot server was failed(%1).	Server restart failure	Check the server status.	o		o
apisv	Error	4430	A request to start group(%1) was failed(%2).	Group start failure	Check the group status.	o		o
apisv	Error	4431	A request to start all groups was failed(%1).	All group start failure	Check the group status.	o		o
apisv	Error	4432	A request to stop group(%1) was failed(%2).	Group stop failure	Check the group status.	o		o
apisv	Error	4433	A request to stop all groups was failed(%1).	All group stop failure	Check the group status.	o		o
apisv	Error	4434	A request to restart group(%1) was failed(%2).	Group restart failure	Check the group status.	o		o
apisv	Error	4435	A request to restart all groups was failed(%1).	All group restart failure	Check the group status.	o		o
apisv	Error	4436	A request to move group(%1) was failed(%2).	Group move failure	Check the group status.	o		o
apisv	Error	4437	A request to move all groups was failed(%1).	All group move failure	Check the group status.	o		o
apisv	Error	4438	A request to failover group(%1) was failed(%2).	Group failover failure	Check the group status.	o		o
apisv	Error	4439	A request to failover all groups was failed(%1).	All group failover failure	Check the group status.	o		o
apisv	Error	4440	A request to migrate group(%1) was failed(%2).	Group migration failure	Check the group status.	o		o
apisv	Error	4441	A request to migrate all groups was failed(%1).	All group migration failure	Check the group status.	o		o
apisv	Error	4442	A request to failover all groups was failed(%1).	All group failover failure	Check the group status.	o		o
apisv	Error	4443	A request to cancel waiting for the dependency destination group of group %s has failed(%1).	Cancel waiting failure	Check the group status.	o		o
apisv	Error	4450	A request to start resource(%1) was failed(%2).	Resource start failure	Check the resource status.	o		o
apisv	Error	4451	A request to start all resources was failed(%1).	All resource start failure	Check the resource status.	o		o
apisv	Error	4452	A request to stop resource(%1) was failed(%2).	Resource stop failure	Check the resource status.	o		o
apisv	Error	4453	A request to stop all resources was failed(%1).	All resource stop failure	Check the resource status.	o		o
apisv	Error	4454	A request to restart resource(%1) was failed(%2).	Resource restart failure	Check the resource status.	o		o
apisv	Error	4455	A request to restart all resources was failed(%1).	All resource restart failure	Check the resource status.	o		o
apisv	Error	4460	A request to suspend monitor resource was failed(%1).	Monitor temporary stop failure	Check the monitor resource status.	o		o
apisv	Error	4461	A request to resume monitor resource was failed(%1).	Monitor restart failure	Check the monitor resource status.	o		o
apisv	Error	4462	A request to enable Dummy Failure of monitor resource(%1) was failed(%2).	Dummy Failure enabled	Check the monitor resource status.	o		o
apisv	Error	4463	A request to disable Dummy Failure of monitor resource(%1) was failed(%2).	Dummy Failure disabled	Check the monitor resource status.	o		o
apisv	Error	4464	A request to disable Dummy Failure of all monitor resource was failed(%1).	All Dummy Failure disabled	Check the monitor resource status.	o		o
apisv	Error	4470	A request to set CPU frequency was failed(%1).	CPU clock control failure	Check if the server handles CPU clock control.	o		o
apisv	Error	4480	Initializing internal communication (%1) failed (port=%2).	Initializing internal communication failed.	Check if an application other than EXPRESSCLUSTER uses the port.	o		o
diskperf	Warning	4801	An internal error occurred in clpdiskperf.dll There is a possibility that certain Cluster Disk Resource Performance Data can't be collected	An internal error occurred in clpdiskperf.dll.	There may be insufficient memory or OS resources. Check whether there are sufficient resources available.	o	o	o
diskperf	Information	4802	clpdiskperf.dll internal problem has gone.	The internal error in clpdiskperf.dll has been resolved.	-	o	o	o
diskperf	Warning	4803	An error occurred by writing in Cluster Disk Resource Performance Data log. Please confirm the state of the disk.	An error occurred when writing the Cluster Disk Resource Performance Data log.	Check whether there is sufficient free disk space.	o	o	o
diskperf	Information	4804	Write error of Cluster Disk Resource Performance Data log was recovered.	The write error in the Cluster Disk Resource Performance Data log has been resolved.	-	o	o	o
diskperf	Error	4805	An internal error occurred in clpdiskperf.dll Cluster Disk Resource Performance Data can't be collected until a server restart.	An internal error occurred in clpdiskperf.dll	Reboot the server.		o	o
diskperf	Error	4806	Cluster Disk Resource Performance Data can't be collected because a performance monitor is too numerous.	The number of processes that load clpdiskperf.dll exceeded 32.	Refer to the following topic in the "Getting Started Guide": "Notes and Restrictions" -> " After starting operating EXPRESSCLUSTER" -> " Event log output relating to linkage between mirror statistical information collection function and OS standard function"
bmchb	Error	4951	Failed to initialize BMC.
bmchb	Warning	4952	Heartbeat from HB resource %1 of server %2 was delayed.
userw	Warning	5001	Monitor %1 was delayed. (timeout=%2 response time=%3 rate=%4)	Monitor delayed	-	o	o	o				o
genw	Warning	5151	Since loss of the target script (%1) has been detected, it was rebooted.	Since loss of the target script (%1) has been detected, it was rebooted	-	o	o
db2 ftp http imap4 odbc oracle otx pop3 psql smtp sqlserver tux was wls	Warning	10001	%1	Error message for each monitored application.	Take appropriate action for the application failure by following the error message.	o	x	x	x	x	x	x	x
db2w ftpw httpw imap4w odbcw oraclew otxw pop3w psqlw smtpw sqlserverw tuxw wasw wlsw db2 ftp http imap4 odbc oracle otx pop3 psql smtp sqlserver tux was wls	Warning	10002	The API Error of Windows occurred.%1	API error of Windows has occurred. %1 is API error code.	Take appropriate action for the OS failure by following the error code.	o	x	x	x	x	x	x	x
mrw	Warning	4901	Monitor %1 is in the warning status. (%2 : %3)	Monitor warn	Check the cause of Warning.	o	o	o				o
mrw	Warning	4902	Configuration of %1 is invalid. (%2 : %3)	invalid monitor resource	Check the cluster configuration data.	o	o	o				o
mrw	Error	4903	Failed to start monitor %1.	monitor starting failed	The system may not be able to operate properly.	o	o	o	o	o		o	o
mrw	Error	4904	Failed to stop monitor %1.	monitor stopping failed	The system may not be able to operate properly.	o	o	o				o
mrw	Error	4905	Monitor %1 detected an error. (%2 : %3)	monitor failed	Check the cause for monitor error.	o	o	o	o	o		o	o
mrw	Information	4906	Monitor resource has not been registered.	unregistered monitor resource	-	o	o	o
mrw	Information	4907	%1 was stopped for failure in monitor %2.	relation stop	-	o	o	o
mrw	Information	4908	%1 was restarted for failure in monitor %2.	relation restart	-	o	o	o
mrw	Information	4909	%1 was failed over for failure in monitor %2.	relation group failover	-	o	o	o
mrw	Information	4910	There was a request to stop cluster for failure in monitor %1.	cluster stop	-	o	o	o
mrw	Information	4911	There was a request to shut down the system for failure in monitor %1.	system shutdown	-	o	o	o
mrw	Information	4912	There was a request to restart the system for failure in monitor %1.	system reboot	-	o	o	o
mrw	Information	4913	Failed to stop %1 due to error detection of %2.	relation stop failure	Check the status of resources.	o	o	o				o
mrw	Error	4914	Failed to restart %1 due to error detection of %2.	relation restart failure	Check the status of resources.	o	o	o				o
mrw	Error	4915	Failed to fail over %1 due to error detection of %2.	relation group failover failure	Check the status of resources.	o	o	o				o
mrw	Error	4916	Failed to stop the cluster due to error detection of %1.	cluster stop failure	The system may not be able to operate properly.	o	o	o				o
mrw	Error	4917	Failed to shut down the system due to error detection of %1.	os shutdown failure	The system may not be able to operate properly.	o	o	o				o
mrw	Error	4918	Failed to restart the system due to error detection of %1.	os reboot failure	The system may not be able to operate properly.	o	o	o				o
mrw	Error	4919	The group of monitor %1 is unknown.	unknown group	Check the cluster configuration data.	o	o	o				o
mrw	Warning	4920	No action is taken because %1 is not online.	not perform failure action	-	o	o	o				o
mrw	Information	4921	Status of monitor %1 was returned to normal.	status changed into normal	-	o	o	o
mrw	Information	4922	Status of monitor %1 was changed into unknown.	status changed into unknown	The system may not be able to operate properly.	o	o	o
mrw	Error	4923	Initialization error has occurred (%1 : %2)	process initialize error	The system may not be able to operate properly.	o	o	o				o
mrw	Information	4924	Causing intentional stop error was required because an error is detected by %1.	intentional panic	-	o	o	o
mrw	Error	4925	Causing intentional stop error has failed because an error is detected by %1.	intentional panic failure	The system may not be able to operate properly.	o	o	o				o
mrw	Warning	4926	Recovery will not be executed since server is suspending.	not recovery(server suspending)	Monitor resource is not recovered if the server is suspended (Network Partition Unsolved). Check the cause for being suspended (Network Partition Unsolved) and recover network partition resources to the normal status.	o	o	o				o
mrw	Warning	4927	Shutdown count reached the maximum number (%1). Final action of monitor %2 was ignored.	reached OS shutdown limit	-	o	o	o	o	o		o	o
mrw	Information	4928	Script before action(%1) upon failure in %2 monitor resource started.	Script before final action upon monitor resource failure started.	-	o	o	o
mrw	Information	4929	Script before action(%1) upon failure in %2 monitor resource completed.	Script before final action upon monitor resource failure completed.	-	o	o	o
mrw	Information	4930	Script before action(%1) upon failure in %2 monitor resource failed.	Script before final action upon monitor resource failure has failed.	-	o	o	o
mrw	Information	4931	Recovery script has executed because an error was detected in monitoring %1.	Recovery script upon monitor resource failure executed		o	o	o
mrw	Error	4932	Attempted to execute recovery script due to the error detected in monitoring %1, but failed.	failed to execute recovery script	Check the cause of the recovery script failure and take measures.	o	o	o
mrw	Warning	4933	Ignored the recovery action in monitoring %1 because recovery action caused by monitor resource error is disabled.	not recovery (recovery action caused by monitor resource error has disabled)	-	o	o	o
mrw	Information	4934	There was a notification (%1) from external. (detail: %2)	An error notification from external was received.	-	o	o	o
tuxw	Warning	10004	The API Error of Application occurred.%1	API error of application has occurred. %1 is API error code.	Take appropriate action for the application failure by following the error code.	o
jra	Error	20251	Internal processing has failed. (%1)	An internal error occurred. %1: Internal error code	Check if JVM monitor resource is running. If not, restart the server.		o
jra	Error	20252	Startup has failed due to an error of the setting value. (%1)	Specified setting valueis invalid. %1: Internal error code	Check if the Java installation path is correct.		o
sra	Error	20301	Service was terminated because reading an SG file failed.	An error occurred in reading the setting file.	Check the message separately issued.		o
sra	Error	20302	The installation folder name could not be acquired.	The installation folder name could not be acquired.	Restart the cluster, or execute the suspend and resume.		o
sra	Error	20305	No IModules could be loaded.	Some files required to execute this product do not exist. So, this product failed to start.	Install this product again.		o
sra	Error	20306	An unexpected error occurred.	An attempt was made to start this product, but failed for some reason or another.	Restart the cluster, or execute the suspend and resume.		o
sra	Error	20307	Internal error occurred.	This product has terminated abnormally.	See the system log message issued last.		o
sra	Error	20308	An error has occurred in issuing WMI. %1(ErrorID:0x%2 class:%3) %1: Message %2: Error code %3: Information that could not be acquired	Statistics information could not be acquired. %1: Message %2: Error code %3: Information that could not be acquired	Restart the cluster, or execute the suspend and resume.		o
sra	Warning	20336	Script is timeout. (%1 %2) %1: Script file name %2: Argument	An internal error has occurred.	Check the load status of the server and remove the load.		o
sra	Information	20346	%1 event succeeded. %1: Event type (Boot, Shutdown, Stop, Start, or Flush)	The operation management command has been executed. The executed event type %1 (boot, shutdown, stop, start, or flush) is output.	-		o
sra	Warning	20347	%1 was smaller than %2, it changed to minimum value(%3).	The configuration value of the monitoring is not correct. %1:Variable name %2:Variable name %3:configured value	Check the configured value on the Cluster WebUI.		o
sra	Warning	20348	%1 was too long compared with %2, it changed to %1(%3).	The configuration value of the monitoring is not correct. %1:Variable name %2:Variable name %3:configured value	Check the configured value on the Cluster WebUI.		o
sra	Warning	20349	%1 was smaller than %2, it changed to %2 value(%3).	The configuration value of the monitoring is not correct. %1:Variable name %2:Variable name %3:configured value	Check the configured value on the Cluster WebUI.		o
sra	Warning	20350	%1 was larger than %2, it changed to %2 value(%3).	The configuration value of the monitoring is not correct. %1:Variable name %2:Variable name %3:configured value	Check the configured value on the Cluster WebUI.		o
sra	Warning	20351	%1 was over than Total disk size, %2.	The configuration value of the monitoring is not correct. %1:Variable name %2:configured value	Check the configured value on the Cluster WebUI.		o
sra	Warning	20352	%1 was over than Total disk size, %2.	The configuration value of the monitoring is not correct. %1:Variable name %2:configured value	Check the configured value on the Cluster WebUI.		o
sra	Warning	20353	Delete MOUNT[%1] in DiskCapacity list.	The configuration value of the monitoring is not correct. %1:configured value	Check the configured value on the Cluster WebUI.		o
sra	Warning	20354	%1 was illegal value (%2).	The configuration value of the monitoring is not correct. %1:Variable name %2:configured value	Check the configured value on the Cluster WebUI.		o
sra	Warning	20355	The DriveLetter of %1 is not ready, or Drive type was not fixed.(DriveLetter = %2)	The configuration value of the monitoring is not correct. %1:Variable name %2:configured value	Check the configured value on the Cluster WebUI.		o
sra	Error	20358	A process resource error was detected. (type = cpu, pid = %1, %2)	An error was detected in monitoring the CPU usage rate of the specific process. %1:Process ID %2:Process name	Check the possible causes of the monitoring failure.	o	o
sra	Error	20358	A process resource error was detected. (type = memory leak, pid = %1, %2)	An error was detected in monitoring the memory usage of the specific process. %1:Process ID %2:Process name	Check the possible causes of the monitoring failure.	o	o
sra	Error	20358	A process resource error was detected. (type = file leak, pid = %1, %2)	An error was detected in monitoring the number of the open files of the specific process. %1:Process ID %2:Process name	Check the possible causes of the monitoring failure.	o	o
sra	Error	20358	A process resource error was detected. (type = thread leak, pid = %1, %2)	An error was detected in monitoring the number of the threads of the specific process. %1:Process ID %2:Process name	Check the possible causes of the monitoring failure.	o	o
sra	Error	20358	A process resource error was detected. (type = same name process, pid = %1, %2)	An error was detected in monitoring a process with the same name. %1:Process ID %2:Process name	Check the possible causes of the monitoring failure.	o	o
sra	Error	20359	A system resource error was detected. (type = cpu)	An error was detected in monitoring the CPU usage rate of the system.	Check the possible causes of the monitoring failure.	o	o
sra	Error	20359	A system resource error was detected. (type = memory)	An error was detected in monitoring the usage amount of the total memories of the system.	Check the possible causes of the monitoring failure.	o	o
sra	Error	20359	A system resource error was detected. (type = swap)	An error was detected in monitoring the usage amount of the total virtual memories of the system.	Check the possible causes of the monitoring failure.	o	o
sra	Error	20360	A disk resource error was detected. (type = used rate, level = NOTICE, %1)	A notice-level error was detected in monitoring the disk usage rate. %1:Logical drive	Check the possible causes of the monitoring failure.	o	o
sra	Error	20360	A disk resource error was detected. (type = used rate, level = WARNING, %1)	A warning-level error was detected in monitoring the disk usage rate. %1:Logical drive	Check the possible causes of the monitoring failure.	o	o
sra	Error	20360	A disk resource error was detected. (type = free space, level = NOTICE, %1)	A notice-level error was detected in monitoring the free space of disks. %1:Logical drive	Check the possible causes of the monitoring failure.	o	o
sra	Error	20360	A disk resource error was detected. (type = free space, level = WARNING, %1)	A warning-level error was detected in monitoring the free space of disks. %1:Logical drive	Check the possible causes of the monitoring failure.	o	o
ddns	Error	5051	Failed to register the virtual host name (%1) to the DNS server.	DNS registration failure %1: Virtual host name	Check whether an error occurred in the DNS server, or whether an error occurred in communication with the DNS server.	o	o
ddns	Error	5052	Failed to delete the virtual host name (%1) from the DNS server.	Failure of deletion of DNS registration %1: Virtual host name	Check whether an error occurred in the DNS server, or whether an error occurred in communication with the DNS server.	o	o
ddns	Error	5053	Failed to disable the Kerberos Authentication (irtual host name: %1).	Failure of disabling Kerberos Authentication %1: Virtual host name	Check if there is an error in Kerberos Authentication server (KDC) or a problem of communications with Kerberos Authentication server (KDC).	o	o
webmgr	Warning	5121	HTTPS configuration isn't correct, HTTPS mode doesn't work. Please access WebManager by HTTP mode.	Invalid HTTPS setting	-	o	o	o
logcmd	Error	3601	[1] gcdns: Failed to obtain the setting value in the activation process.	The setting value failed to be obtained in activation of Google Cloud DNS resource.	Check the settings of Google Cloud DNS resource.	o	o	o
			[2] gcdns: Failed to obtain the record set in the activation process.	The Cloud DNS record set failed to be obtained in Google Cloud DNS resource activation.	Check the setting value of Google Cloud DNS resource and the privilege of the account which permitted Cloud SDK.	o	o	o
			[3] gcdns: Failed to start the transaction in the activation process.	The Google Cloud DNS resource activation failed to start the transaction.	Check the privilege of the account which permitted Cloud SDK.	o	o	o
			[4] gcdns: Failed to delete the record set in the activation process.	The Google Cloud DNS resource activation failed to add the record set deletion processing to the transaction.	Check the privilege of the account which permitted Cloud SDK.	o	o	o
			[5] gcdns: Failed to add the record set in the activation process.	The Google Cloud DNS resource activation failed to add the record set addition processing to the transaction.	Check the privilege of the account which permitted Cloud SDK.	o	o	o
			[6] gcdns: Failed to execute the transaction in the activation process.	The Google Cloud DNS resource activation failed to execute the transaction.	Check the privilege of the account which permitted Cloud SDK.	o	o	o
			[1] gcdns: Failed to obtain the setting value in the deactivation process.	The Google Cloud DNS resource deactivation failed to obtain the setting value.	Check the settings of Google Cloud DNS resource.	o	o	o
			[2] gcdns: Failed to obtain the record set in the deactivation process.	The Google Cloud DNS resource deactivation failed to obtain the record set of Cloud DNS.	Check the setting value of Google Cloud DNS resource and the privilege of the account which permitted Cloud SDK.	o	o	o
			[3] gcdns: Detected an invalid parameter in the deactivation process.	An internal error occurred in the Google Cloud DNS resource deactivation.	-	o	o	o
			[4] gcdns: Failed to start the transaction in the deactivation process.	The Google Cloud DNS resource activation failed to start the transaction.	Check the privilege of the account which permitted Cloud SDK.	o	o	o
			[5] gcdns: Failed to delete the record set in the deactivation process.	The Google Cloud DNS resource activation failed to add the record set deletion processing to the transaction.	Check the privilege of the account which permitted Cloud SDK.	o	o	o
			[6] gcdns: Failed to execute the transaction in the deactivation process.	The Google Cloud DNS resource activation processing failed to execute the transaction.	Check the privilege of the account which permitted Cloud SDK.	o	o	o
			[1] gcdnsw: Failed to obtain the setting value.	The monitoring of Google Cloud DNS monitor resource failed to obtain the setting value.	Check the settings of Google Cloud DNS monitor resource.	o	o	o
			[2] gcdnsw: Failed to obtain the zone name.	The monitoring of Google Cloud DNS monitor resource failed to obtain the setting value of the resource to be monitored at activation.	Check the settings of Google Cloud DNS monitor resource and Google Cloud DNS resource.	o	o	o
			[3] gcdnsw: Failed to obtain the DNS name.	The monitoring of Google Cloud DNS monitor resource failed to obtain the setting value of the resource to be monitored at activation.	Check the settings of Google Cloud DNS monitor resource and Google Cloud DNS resource.	o	o	o
			[4] gcdnsw: Failed to obtain the record type.	The monitoring of Google Cloud DNS monitor resource failed to obtain the setting value of the resource to be monitored at activation.	Check the settings of Google Cloud DNS monitor resource and Google Cloud DNS resource.	o	o	o
			[5] gcdnsw: Failed to obtain the TTL.	The monitoring of Google Cloud DNS monitor resource failed to obtain the record set of Cloud DNS.	Check the setting value of Google Cloud DNS monitor resource and the privilege of the account which permitted Cloud SDK.	o	o	o
			[6] gcdnsw: Failed to obtain the IP address.	The monitoring of Google Cloud DNS monitor resource failed to obtain the record set of Cloud DNS.	Check the setting value of Google Cloud DNS monitor resource and the privilege of the account which permitted Cloud SDK.	o	o	o
			[7] gcdnsw: Failed to obtain the record set.	The monitoring of Google Cloud DNS monitor resource failed to obtain the record set of Cloud DNS.	Check the setting value of Google Cloud DNS monitor resource and the privilege of the account which permitted Cloud SDK.	o	o	o
			[8] gcdnsw: No record set to be monitored. (%1)	A monitoring failure was detected in Google Cloud DNS monitor resource. %1:Cause of error	-	o	o	o

10.4. Driver event log messages

10.4.1. Disk filter driver

The following events are recorded in system event log as the source "clpdiskfltr".

Module Type	Event Type	Event ID	Message	Description	Solution
diskfltr	Info	1001	Mirror disk resource activated without mirroring achieved.(%1)	Mirror disk resource has been activated without connecting to the mirror connect. %1: mirror disk number	Mirror disk resource has been activated while the other server is not in normal state such as in failover or access restriction release. Make sure there is no error in the other server.
diskfltr	Info	1002	The mirror disk connect of mirror disk %1 is available. (Priority %2)	The standby mirror disk connect has been recovered. The degenerated state has changed to the redundant state. %1: Mirror disk number %2: Priority number	-
diskfltr	Info	1003	The mirror disk connect used for mirror data communication of mirror disk %1 has been changed due to a user request. (Priority %2 -> %3)	The active mirror disk connect has been changed due to a manual change request. %1: Mirror disk number %2: Priority number before switching %3: Priority number after switching	-
diskfltr	Info	1004	The mirror disk connect used for mirror data communication of mirror disk %1 has been changed due to a request from the sending server. (Priority %2 -> %3)	The active mirror disk connect has been changed due to a request from the sending server. %1: Mirror disk number %2: Priority number before switching %3: Priority number after switching	Make sure there is no error in the network.
diskfltr	Info	1005	The operation of compressing mirror communication data of mirror disk %1 has been changed (%2).	The mirror communication data compression method has been changed to one different from the specified method.	-
diskfltr	Info	1006	The mirror disk has been activated in compatible mode. The version of the driver is different from that of the mirror destination server (%1).	The version of the EXPRESSCLUSTER on the destination server is old. %1: Mirror disk number	Make sure the version of the installed EXPRESSCLUSTER is the same.
diskfltr	Info	1007	An error occurred when the mirror disk connect was initialized. (%1)	Because an error occurred during initialization of the mirror disk connect, the target mirror disk connect is not available. %1: IP address of the mirror disk connect	Make sure there is no error in the network.
diskfltr	Error	2001	Mirror disk connect error.(%1)	Disconnected: Disconnection has been detected in the mirror connect.	Make sure there is no error in the network.
				Timeout - HealthCheck: There was no response from the other server.	Same as above.
				Timeout - 1stAck: There was no response from the other server.	Make sure there is no error in the network or the other server.
				Timeout - 2ndAck: There was no response from the other server.	Same as above.
				refused by other: The other server is in an invalid status (like being activated).	The same as above
				Mirror DP Not Found: The data partition of the other server cannot be found.	Make sure there is no error in the data partition of the other server.
diskfltr	Error	2002	Asynchronized transfer error.(%1)	Timeout - Get KernelQueue: Timeout occurred in asynchronized transfer.	An error occurred in the user process of asynchronized transfer. Check that the clpdiskagent process is running normally, and that there is no error in I/O to the local disk.
				History Overflow: The number of the items to be recorded as history (default 6553500 I/O) was exceeded, so mirroring was interrupted.	Consider to decrease the process to write asynchronized transfer or improve the speed of circuit.
diskfltr	Error	2003	Mirror disk access error(DP).(%1)	Accessing the mirror disk failed. %1: mirror disk number	Make sure there is no error in the data partition of the mirror disk. In case of an error, exchange the disk for the one without an error.
diskfltr	Error	2004	Mirror disk access error(CP).(%1)	Failed to record the difference information on the cluster partition. %1: mirror disk number	Make sure there is no error in the cluster partition of the mirror disk. In case of an error, exchange the disk for the one without an error.
diskfltr	Error	2005	Cluster partition access error.	Accessing the cluster portion failed.	Make sure there is no error in the cluster partition of the mirror disk. In case of an error, exchange the disk for the one without an error.
diskfltr	Error	2006	Mirror disk activation error.(%1)	Standby: Mirror disk is already being operated as the standby system.	An error in operation is considered to have caused this error. Check the cause of this error.
				Already opened: Mirror disk is already being operated as the active system.	Same as above.
				Refused by other: The status of the other server is wrong. (It is being activated now.)	Same as above.
diskfltr	Error	2007	Failed to initialize the encryption. (%1)	The initialization of the encryption failed. %1: nmp_index=Mirror disk number	Kernel memory or OS resource may not be sufficient. Check with performance monitor.
diskfltr	Error	2008	The encryption key is invalid. (%1)	Invalid encryption key. %2: nmp_index=Mirror disk number	Check if the correct encryption key is used.
diskfltr	Error	2009	Failed to encrypt the mirror data. (%1)	The encryption of the mirror data failed. %1: nmp_index=Mirror disk number	Kernel memory or OS resource may not be sufficient. Check with performance monitor.
			Failed to encrypt the mirror data. (%1, Encryption serial no overflow.)	Overflow of encryption serial number. %1: nmp_index=Mirror disk number	Update the encryption key.
diskfltr	Error	2010	Failed to decrypt the mirror data. (%1)	The decryption of mirror data failed. %1: nmp_index=Mirror disk number	Kernel memory or OS resource may not be sufficient. Check with performance monitor.
			Failed to decrypt the mirror data. (%1, Encryption serial no overflow.)	Overflow of encryption serial number. %1: nmp_index=Mirror disk number	Update the encryption key.
diskfltr	Error	2099	Internal error.	An internal error occurred.	Insufficient kernel memory or OS resource is considered to have caused this error. Check this error with the performance monitor.
diskfltr	Warning	3001	The mirror disk connect used for mirror data communication of mirror disk %1 has been changed due to a communication error. (Priority %2 -> %3)	Disconnection of the active mirror disk connect has been detected. The mirror disk connect will be switched and mirror disk connect %3 will be used. %1: Mirror disk number %2: Priority number before switching %3: Priority number after switching	Make sure there is no error in the network.
diskfltr	Warning	3002	The mirror disk connect of mirror disk %1 is unavailable. (Priority %2)	Disconnection of the standby mirror disk connect has been detected. %1: Mirror disk number %2: Priority number	Make sure there is no error in the network.
diskfltr	Error	5001	Connection error on mirror disk connect.(%1)	Connecting to the mirror connect failed.	Make sure there is no error in the network or the mirror connect settings.
diskfltr	Error	5002	Communication error on mirror disk connect.(%1)	Because the network has an error or is highly loaded, the mirror connect is disconnected.	Make sure there is no error in the network.
diskfltr	Error	5003	History file access error.(%1)	Failed to write or read the history file.	Make sure there is no error in the hard disk. In case of an error, exchange the disk for the one without an error.
diskfltr	Error	5004	Mirror disk virtual device access error.(%1)	Failed to obtain the data from the mirror disk virtual driver.	The mirror disk virtual driver is not running normally or has an error. Check that EXPRESSCLUSTER has been set up correctly.
diskfltr	Error	5005	Mirror disk connect timeout.(%1)	The network has an error or is highly loaded, the mirror connect is disconnected.	Make sure there is no error in the network or the other server.
diskfltr	Error	5006	History file disk overflow.(%1)	Failed to output the history file because of insufficient disk capacity.	The folder to store the history file does not have enough. Set the folder with enough capacity.
diskfltr	Error	5007	Queue buffer allocation error.(%1)	Failed to allocate the buffer for ansynchronized transfer.	Insufficient memory or OS resource is considered to have caused this error. Check the cause.
diskfltr	Error	5099	Internal error.(%1)	An internal error occurred.	Insufficient memory or OS resource is considered to have caused this error. Check the cause.

10.4.2. Kernel mode LAN heartbeat driver

The following events are recorded in system event log as the source "clphb".

Module Type	Event Type	Event ID	Message	Description	Solution
clphb	Error	3001	Fatal error occurred in the driver.	Fatal error occurred in the driver.	Kernel memory or OS resource may not be sufficient. Check with performance monitor.
clphb	Info	1001	Signal has been set to the shutdown event due to the keep alive timeout.	User mode is stalled.	Kernel memory or OS resource may not be sufficient. Check with performance monitor.
clphb	Info	1002	Signal has been set to the shutdown event due to the FILTER closing action.	Received FILTER closing action.	Kernel memory or OS resource may not be sufficient. Check with performance monitor.

10.5. Detailed information in activating and deactivating group resources

The following information is displayed in the messages recorded in event logs or alert logs as detail information when the resource activation / deactivation fails.

10.5.1. Application resource

Module Type	Type	Return Value	Message	Description	Solution
appli	Error	5	The application path is invalid.	The application path is invalid.	Check if the application path is correct.
appli	Error	7	Failed to start application.	Failed to start application.	Memory or OS resources may not be sufficient. Check them.
appli	Error	8	Failed to stop application.	Failed to stop application.	Memory or OS resources may not be sufficient. Check them.
appli	Error	10	Timeout occurred.	Timeout occurred.	Check if the application terminates within the timeout period.
appli	Error	11	Failed to log on as a user.	Failed to log on as a user.	Check if a domain, an account and a password of the logon user are set properly.
appli	Error	12	Returned exit code %1.	The non-resident type application returned abnormal error code.	Check the cause for the abnormal error code.
appli	Error	Others	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.5.2. CIFS Resource

Module Type	Type	Return Value	Message	Description	Solution
cifs	Error	2	The specified path is invalid.	The specified path is invalid.	Correct the setting of target folder.
cifs	Error	3	Access denied.	Access denied.	Check if local system account has the appropriate access right to the target folder.
cifs	Error	4	The share name is already in use on this server.	The specified name of the shared folder is already in use on this server.	Correct the setting of shared name.
cifs	Error	5	The specified path does not exist.	The specified path does not exist.	Correct the setting of target folder.
cifs	Error	6	Insufficient memory is available.	Insufficient memory is available.	Memory or OS resources may not be sufficient. Check them.
cifs	Error	7	The specified folder can not be found.	The specified folder can not be found.	Correct the setting of target folder.
cifs	Error	8	The specified shared name cannot be found.	The shared folder to be monitored does not exist.	Check if the shared configuration has not been released.
cifs	Error	10	Failed to set the caching.	Failed to set the caching.	Check if local system account has the appropriate access right to the target folder.
cifs	Error	11	Failed to set security information.	Failed to set security information.	Check if local system account has the appropriate access right to the target folder.
cifs	Error	15	The shared configuration file path is wrong.	Specified path does not exist, or invalid character strings are used in the absolute path.	Correct the configuration value.
cifs	Error	17	Failed to write the shared configuration file.	Failed to save the shared configuration in the file.	Check if the writing to the shared configuration file is available with the local system account.
cifs	Error	18	Failed to read the shared configuration file.	Failed to read the shared configuration form the file.	Check if the reading from the shared configuration file is available with the local system account.
cifs	Error	20	Failed to start up CIFS control process.	Failed to start up the process (clpcifsp.exe) that monitors the change of shared configuration	There may be corruption of the execution file, lack of memory capacity or lack of OS resource. Check these issues.
cifs	Error	25	Failed to set comments for the shared folder.	Failed to set comments for the shared folder.	Check the access right for the local system account and the shared name of the shared folder.
cifs	Error	Others	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.5.3. Floating IP resource

Module Type	Type	Return Value	Message	Description	Solution
fip	Error	5	IP address already exists.	IP address already exists.	Check if the IP address is already used on the network. Set the IP address that is not used.
fip	Error	8	Available adapter does not exist.	Available adapter does not exist.	Check if the FIP address network is the same as the server's real IP address.
fip	Error	9	Failed to add IP address.	Failed to add IP address.	Check the result of the ipconfig command. If 0.0.0.0 address exists, restart NIC.
fip	Error	10	Failed to delete IP address.	Failed to delete IP address.	Memory or OS resources may not be sufficient. Check them.
fip	Error	99	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.5.4. Mirror disk resource / hybrid disk resource

Module Type	Type	Return Value	Message	Description	Solution
md/hd	Error	2	An internal error occurred.	An internal error occurred.	Memory or OS resources may not be sufficient. Check them.
md/hd	Error	2	The resource is busy.	The resource is busy.	The partition may be in use. Wait for a while, and retry the operation.
md/hd	Error	2	A network error occurred.	A network error occurred.	Check the status of the interconnect connection.
md/hd	Error	2	Cannot establish the mirror disk connection.	Cannot establish the mirror disk connection.	Check if the cluster configuration data is correct.
md/hd	Error	2	The resource name is invalid.	The resource name is invalid.	Check if the cluster configuration data is correct.
md/hd	Error	2	The status is invalid.	The status is invalid.	You need to perform the mirror recovery.
md/hd	Error	2	The resource is not initialized.	The resource is not initialized.	Check if the partition is allocated and OS recognizes the disk. Check if the cluster configuration data is correct.
md/hd	Error	2	The resource is not performed first mirror construction.	The resource is not performed first mirror construction.	You need to perform the initial mirror construction.
md/hd	Error	2	Cannot lock the mirror disk.	Cannot lock the mirror disk.	Memory or OS resources may not be sufficient. Check them.
md/hd	Error	2	The license is not registered.	The license is not registered.	Register the license.
md/hd	Error	2	The trial version has expired.	The trial version has expired.	Register the license.
md/hd	Error	2	The license authentication failed.	The license authentication failed.	Register the license.
md/hd	Error	2	Cannot find the history folder.	Cannot find the history folder.	Check if the cluster configuration data is correct.
md/hd	Error	2	The mirror connect is not initialized.	The mirror connect is not initialized.	Check the status of the mirror connect. Check if the cluster configuration data is correct.
md/hd	Error	2	Cannot find the partition specified for the cluster partition.	Cannot find the partition specified for the cluster partition.	Check if the partition is allocated and the OS recognizes the disk.
md/hd	Error	2	Cannot find the partition specified for the data partition.	Cannot find the partition specified for the data partition.	Check if the partition is allocated and the OS recognizes the disk.
md/hd	Error	2	Cannot change the drive letter for the cluster partition.	Cannot change the drive letter for the cluster partition.	Check if the drive letter for the cluster configuration data is specified. Check if the drive letter is not used for another partition.
md/hd	Error	2	Cannot change the drive letter for the data partition.	Cannot change the drive letter for the data partition.	Check if the drive letter for the cluster configuration data is specified. Check if the drive letter is not used for another partition.
md/hd	Error	2	The server name is invalid.	The server name is invalid.	Check if the cluster configuration data is correct.

10.5.5. NAS Resource

Module Type	Type	Return Value	Message	Description	Solution
nas	Error	1	The drive has already been used.	The specified drive letter has already been used for another network drive.	Change the drive letter.
nas	Error	3	Invalid nas drive.	The specified drive letter has already been used for another drive.	Change the drive letter.
nas	Error	4	Failed to redirect the network resource .	Failed to mount the network drive.	Check if the specified network resource is accessible with the specified account and password.
nas	Error	Others	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.5.6. Registry synchronization resource

Module Type	Type	Return Value	Message	Description	Solution
regsync	Error	2	Timeout has occurred while waiting for completion of synchronization processing at startup.	The resource cannot be activated because synchronization of registry files between servers has not been completed.	Activate the resource again after a while. If the error persists, OS may have errors. Check the status of the system.
regsync	Error	2	Timeout occurred when waiting for completing initialization of resource thread.	Activating the resource failed because initialization process of the thread has not been completed.	OS may have errors. Check the status of the system.
regsync	Error	2	Timeout occurred when waiting for completing termination of resource thread.	Deactivating the resource failed because termination process of the thread has not been completed.	OS may have errors. Check the status of the system.
regsync	Error	4	Specified resource does not exist in cluster configuration data.	Activating or deactivating the resource failed because it does not exist on the cluster configuration data.	Check if the resource name is consistent with the information in the cluster configuration data.
regsync	Error	5	Failed to allocate memory.	Activating the resource failed because the memory cannot be allocated.	Memory or OS resources may not be sufficient. Check the status of the system.
regsync	Error	6	Failed to get OS resource.	Activating the resource failed because OS resource cannot be obtained.	Memory or OS resources may not be sufficient. Check the status of the system.
regsync	Error	6	Failed to create thread.	Activating the resource failed because the thread cannot be created.	Memory or OS resources may not be sufficient. Check the status of the system.
regsync	Error	7	Failed to open registry.	Opening the registry failed because invalid registry key is registered to the resource.	Check the value set on the Cluster WebUI (Details on Resource Properties), and change to a correct registry key.
regsync	Error	7	Failed to restore registry.	Restoring the registry failed because invalid registry key is registered to the resource.	Check the value set on the Cluster WebUI (Details on Resource Properties), and change to a correct registry key.
regsync	Error	8	Failed to open registry.	Opening the registry failed because the registry key registered to the resource does not exist on the registry, or Win32 API error occurred.	Check if the registry key exists on the registry. If it does not exist, create it. If it exists, OS may have errors. Check the status of the system.
regsync	Error	8	Failed to restore registry.	Opening the registry failed because the registry key registered to the resource does not exist on the registry, other process opens the registry key, or the system call for registry operation returned an error.	Check if the registry key exists on the registry. If it does not exist, create it. If it exists, check if a process other than EXPRESSCLUSTER opens the registry key. If the registry key exists and no other process opens it, OS may have errors. Check the status of the system.
regsync	Error	9	Failed to lock file.	Locking a file failed when operating the registry storage file.	Check if the process other than EXPRESSCLUSTER opens the registry storage file.
regsync	Error	9	Failed to input/output the file.	The input/output process of the file failed when operating the registry storage file.	Check if the process other than EXPRESSCLUSTER opens the registry storage file. OS may have errors. Check the status of the system.
regsync	Error	12	Synchronization processing at startup has failed.	The resource cannot be activated because synchronization process of the registry storage file between servers failed.	OS may have errors. Check the status of the system.

10.5.7. Script resource

Module Type	Type	Return Value	Message	Description	Solution
script	Error	6	Failed to execute start script.	Failed to execute start script.	Memory or OS resources may not be sufficient. Check them.
script	Error	7	Failed to execute stop script.	Failed to execute stop script.	Memory or OS resources may not be sufficient. Check them.
script	Error	8	Returned exit code %1.	The synchronous type script returned abnormal error code.	Check the cause for the abnormal error code.
script	Error	9	Timeout occurred.	Timeout occurred.	Check if the script terminates within the timeout period.
script	Error	10	Failed to log on as a user.	Logon as a user failed	Check if the domain, account and password of the execution user are correctly set.
script	Error	Others	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.5.8. Disk resource

Module Type	Type	Return Value	Message	Description	Solution
sd	Error	-1	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.
sd	Error	-1	Failed to load cluster configuration data.	Failed to load cluster configuration data.	Check if the cluster configuration data is stored on a proper location.
sd	Error	-1	Failed to unload cluster configuration data.	Failed to unload cluster configuration data.	Check if the cluster configuration data is stored on a proper location.
sd	Error	-1	Failed to get cluster configuration data.	Failed to get cluster configuration data.	Check if the cluster configuration data is correct.
sd	Error	-1	Failed to allocate memory.	Failed to allocate memory.	Memory or OS resources may not be sufficient. Check them.
sd	Error	-1	Failed to activate resource.	Failed to activate resource.	Check if the HBA settings are correct. The partition may be in use. Check it.
sd	Error	-1	Failed to create thread.	Failed to create thread.	Memory or OS resources may not be sufficient. Check them.
sd	Error	-1	Timeout occurred on thread.	Timeout occurred on thread.	Memory or OS resources may not be sufficient. Check them.
sd	Error	-1	Failed to dismount the partition specified by the resource.	Failed to dismount the partition specified by the resource.	The partition may be in use. Check it.
sd	Error	-1	Failed to lock the partition specified by the resource.	Failed to lock the partition specified by the resource.	The partition may be in use. Check it.
sd	Error	-1	Failed to deactivate resource.	Failed to deactivate resource.	Check if the HBA settings are correct.
sd	Error	-1	Server does not exist in cluster configuration data.	Server does not exist in cluster configuration data.	Check if the server exists in the cluster configuration data.
sd	Error	-1	Resource does not exist in cluster configuration data.	Resource does not exist in cluster configuration data.	Check if the resource exists in the cluster configuration data.
sd	Error	-1	Cannot find the specified partition.	Cannot find the specified partition.	Check if OS recognizes the specified partition.
sd	Error	-1	Cannot change the drive letter.	Cannot change the drive letter.	Check if the specified drive letter is used for another partition.

10.5.9. Service resource

Module Type	Type	Return Value	Message	Description	Solution
service	Error	5	Failed to get service control right.	Failed to get service control right.	Check if the service name is correct.
service	Error	6	Failed to start service.	Failed to start service.	Check the status of the service.
service	Error	7	Failed to stop service.	Failed to stop service.	Check the status of the service.
service	Error	8	Service has already been running.	Service has already been running.	Check the status of the service. It is possible to configure settings not to make it an error when the service is already running.
service	Error	10	Timeout occurred.	Timeout occurred.	Check if the service starts or stops within the timeout period.
service	Error	13	Computer name related to service that is running is different from virtual computer name of target VCOM resource.	Computer name related to service that is running is different from virtual computer name of target VCOM resource.	When you set the same service to more than one service, do not set the target VCOM resource name.
service	Error	Others	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.5.10. Print spooler resource

Module Type	Type	Return Value	Message	Description	Solution
spool	Error	5	Failed to stop service.	Failed to stop service.	Stopping the spooler service failed. Check if the printer setting is correct.
spool	Error	4	Failed to start service.	Failed to start service.	Starting the spooler service failed. Check if the printer setting is correct.
spool	Error	Other	Internal error occurred.(status:%1)	Internal error occurred.(status:%1)	The disk capacity or the memory of the server where EXPRESSCLUSTER is installed may not be sufficient. Check them.
spool	Error	1	Failed to create a specified spool directory.	Failed to create a specified spool directory.	Check if activating the disk resource or the mirror disk resource fails. Check if characters that cannot be used in a directory name are included.
spool	Error	1	Failed to change a spool directory.	Failed to change a spool directory.	Check if activating the disk resource or the mirror disk resource fails. Check if characters that cannot be used in a directory name are included.
spool	Error	2	Config value(printer name) is invalid. resource:%1 value:%2	Config value(printer name) is invalid. resource:%1value:%2	Check if the printer name exists on the server.
spool	Error	2	Config value(partition) is invalid. resource:%1 value:%2	Config value(partition) is invalid. resource:%1 value:%2	Check if the drive letter is the one on the disk resource or the mirror disk resource.
spool	Error	2	Config value(directory) is invalid. resource:%1 value:%2	Config value(directory) is invalid. resource:%1 value:%2	Check if characters that cannot be used in a directory name are included.

10.5.11. Virtual computer name resource

Module Type	Type	Return Value	Message	Description	Solution
vcom	Error	5	VCOM control process has already been started.	VCOM control process has already been started.	Memory or OS resources may not be sufficient. Check them. Restart the OS.
vcom	Error	6	VCOM control process has not been started.	VCOM control process has not been started.	Memory or OS resources may not be sufficient. Check them. Restart the OS.
vcom	Error	8	VCOM control process does not exist.	VCOM control process does not exist.	Memory or OS resources may not be sufficient. Check them. Restart the OS.
vcom	Error	9	Failed to get IP address table.	Failed to get IP address table.	Memory or OS resources may not be sufficient. Check them.
vcom	Error	10	Target FIP address does not exist.	Target FIP address does not exist.	Check if the IP address of the target FIP resource exists.
vcom	Error	11	Virtual computer name is the same as local hostname.	Virtual computer name is the same as local hostname.	Do not set existing host names for a virtual computer name.
vcom	Error	12	Failed to start VCOM control process.	Failed to start VCOM control process.	Check if all conditions for using a virtual computer are met.
vcom	Error	13	Failed to stop VCOM control process.	Failed to stop VCOM control process.	An error occurred when stopping the virtual computer. Restart the OS.
vcom	Error	Others	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.5.12. Virtual IP resource

Module Type	Type	Return Value	Message	Description	Solution
vip	Error	5	IP address already exists.	IP address already exists.	Check if the IP address is already used on the network. Set the IP address that is not used.
vip	Error	8	Available adapter does not exist.	Available adapter does not exist.	Check if the IP address set on the interconnect exists on the server. Set a proper IP address.
vip	Error	9	Failed to add IP address.	Failed to add IP address.	Check the result of the ipconfig command. If 0.0.0.0 address exists, restart NIC.
vip	Error	10	Failed to delete IP address.	Failed to delete IP address.	Memory or OS resources may not be sufficient. Check them.
vip	Error	Others	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.5.13. Virtual machine resource

Module Type	Type	Return Value	Message	Description	Solution
vm	Error	5	Virtual Machine configuration data is invalid.	The configuration file of the virtual machine may be invalid.	Check if VM configuration file path is correct.
vm	Error	6	Virtual machine has been already started.	The virtual machine failed to start because the virtual machine has been already started.	Check the status of the virtual machine.
vm	Error	7	Hyper-V Virtual Machine Management service has not started yet.	Hyper-V Virtual Machine Management has not started yet.	Check the status of Hyper-V Virtual Machine Management service.
vm	Error	8	Failed to start virtual machine.	Failed to start virtual machine.	Check the status of the virtual machine and if the configuration file is valid.
vm	Error	9	Failed to stop virtual machine.	Failed to stop virtual machine.	Check the status of the virtual machine.
vm	Error	10	Failed to save virtual machine.	Failed to temporarily stop and export the virtual machine.	Check if the status of the virtual machine is Running on Hyper-V manager.
vm	Error	11	Failed to resume virtual machine.	Failed to import and restart the virtual machine.	Check if VM configuration file path is correct.
vm	Error	13	Timeout occurred.	It took much time to import, export, start or stop the virtual machine.	Check if the timeout value is proper.
vm	Error	Others	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.5.14. Dynamic DNS resource

Module Type	Type	Return Value	Message	Description	Solution
ddns	Error	1	Parameter is invalid.	The dynamic DNS resource or dynamic DNS monitoring resource parameter is invalid.	Check the cluster configuration data.
ddns	Error	2	Group does not exist in cluster configuration data.	Group does not exist in cluster configuration data.	Check the cluster configuration data.
ddns	Error	3	Resource does not exist in cluster configuration data.	Resource does not exist in cluster configuration data.	Check the cluster configuration data.
ddns	Error	4	Failed to get the value from cluster configuration data.	Failed to get the value from cluster configuration data.	Check the cluster configuration data.
ddns	Error	5	Query to DNS has failed.	Query to DNS has failed.	Check the DNS server setting. Make sure that communication with the DNS server is enabled.
ddns	Error	6	Failed to delete DNS.	Failed to delete DNS.	Check the DNS server setting. Make sure that communication with the DNS server is enabled.
ddns	Error	7	Failed to update DNS.	Failed to update DNS.	Check the DNS server setting. Make sure that communication with the DNS server is enabled.
ddns	Error	8	A reception timeout occurred.	A reception timeout occurred.	Memory or OS resources may not be sufficient. Check them.
ddns	Error	9	Failed to send to the DNS server.	Failed to send to the DNS server.	Check the DNS server setting. Make sure that communication with the DNS server is enabled.
ddns	Error	10	Failed to receive from the DNS server.	Failed to receive from the DNS server.	Check the DNS server setting. Make sure that communication with the DNS server is enabled.
ddns	Error	13	DDNS control process has already started.	DDNS control process has already started.	Memory or OS resources may not be sufficient. Check them. Or, the previous activation might fail. In this case, stop the cluster and kill the DDNS control process (clpddnsp.exe) manually.
ddns	Error	14	DDNS control process is not running.	DDNS control process is not running.	Check the DNS server setting. Make sure that communication with the DNS server is enabled. Or, memory or OS resources are shortage. Check them.
ddns	Error	16	Failed to start DDNS control process.	Failed to start DDNS control process.	Check the DNS server setting. Make sure that communication with the DNS server is enabled. Or, memory or OS resources are shortage. Check them.
ddns	Error	17	Failed to stop DDNS control process.	Failed to stop DDNS control process.	Check the DNS server setting. Make sure that communication with the DNS server is enabled. Or, memory or OS resources may not be sufficient. Check them.
ddns	Error	18	DDNS control process path is invalid.	DDNS control process path is invalid.	The executable file is damaged, or memory or OS resources are shortage. Check them.
ddns	Error	99	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.5.15. AWS elastic ip resources

Module type	Type	Return value	Message	Description	Solution
awseip	Error	5	AWS CLI command failed.	Failed in the AWS CLI command.	Check if the settings in the AWS CLI file are correct.
awseip	Error	5	The allocation ID '%1' does not exist	The specified EIP ALLOCATION ID %1 does not exist.	Check if the value of EIP ALLOCATION ID is correct.
awseip	Error	5	The networkInterface ID '%1' does not exist)	The specified ENI ID %1 does not exist.	Check if the value of ENI ID is correct.
awseip	Error	6	Timeout occurred.	Timeout occurred.	Memory or OS resources may not be sufficient. Check them.
awseip	Error	7	ENI ID is invalid.	The ENI ID is invalid.	Check if the value of ENI ID is correct. Check if ENI ID of other instance is specified mistakenly.
awseip	Error	99	Internal error occurred.	An internal error occurred.	Check if Python is installed correctly. Check if AWS CLI is installed correctly. Memory or OS resources may not be sufficient. Check them.

10.5.16. AWS virtual ip resources

Module type	Type	Return value	Message	Description	Solution
awsvip	Error	5	AWS CLI command failed.	Failed in the AWS CLI command.	Check if the settings in the AWS CLI file are correct.
awsvip	Error	5	The vpc ID '%1' does not exist	The specified VPC ID %1 does not exist.	Check if the value of VPC ID is correct.
awsvip	Error	5	The networkInterface ID '%1' does not exist)	The specified ENI ID %1 does not exist.	Check if the value of ENI ID is correct.
awsvip	Error	6	Timeout occurred.	Timeout occurred.	Memory or OS resources may not be sufficient. Check them.
awsvip	Error	7	The VIP address belongs to a VPC subnet.	The VIP address belongs to a VPC CIDR.	For the VIP address, an IP address not belonging to a VPC CIDR must be specified. Check the VIP address.
awsvip	Error	8	Failed to add the VIP address.	Failed to add the VIP address.	Check the VIP settings. Memory or OS resources may not be sufficient. Check them.
awsvip	Error	9	Failed to delete the VIP address.	Failed to delete the VIP address.	Memory or OS resources may not be sufficient. Check them.
awsvip	Error	10	The VIP address is already used.	The VIP address is already used.	Check if the VIP address is already used.
awsvip	Error	11	ENI ID is invalid.	The ENI ID is invalid.	Check if the value of ENI ID is correct. Check if ENI ID of other instance is specified mistakenly.
awsvip	Error	99	Internal error occurred.	An internal error occurred.	Check if Python is installed correctly. Check if AWS CLI is installed correctly. Memory or OS resources may not be sufficient. Check them.

10.5.17. AWS DNS resource

Module type	Type	Retrun value	Message	Description	Solution
awsdns	Error	5	AWS CLI command failed.	Failed in the AWS CLI command.	Check if the settings in the AWS CLI file are correct.
awsdns	Error	6	Timeout occurred.	Timeout occurred.	Check the load status of the server and remove the load.
awsdns	Error	99	Internal error occurred.	An internal error occurred.	Check if Python is installed correctly. Check if AWS CLI is installed correctly. Memory or OS resources may not be sufficient. Check them.

10.5.18. Azure probe port resources

Module type	Type	Return value	Message	Description	Solution
azurepp	Error	5	Probe port is already used.	The Probe port is already used.	Check if the probe port is already opend on the local server.
azurepp	Error	6	Failed to open the probe port.	Failed to open the probe port.	Memory or OS resources may not be sufficient. Check them.
azurepp	Error	7	Failed to close the probe port.	Failed to close the probe port.	Memory or OS resources may not be sufficient. Check them.
azurepp	Error	8	Failed to stop the probe port control process.	Failed to stop the probe port control process.	Memory or OS resources may not be sufficient. Check them. Reboot the OS.
azurepp	Error	9	The probe port control process has already started.	The probe port control process has already started.	Memory or OS resources may not be sufficient. Check them. Or, the immediately preceding deactivation may have failed. In that case, stop the cluster and forcibly terminate the probe port control process (clpazureppp.exe) manually.
azurepp	Error	10	Failed to start the robe port control process.	Failed to start the probe port control process.	Memory or OS resources may not be sufficient. Check them.
azurepp	Error	99	Internal error has occurred.	An internal error has occurred.	Memory or OS resources may not be sufficient. Check them.

10.5.19. Azure DNS resource

Module type	Type	Return value	Message	Description	Solution
azuredns	Error	41	Timeout has occurred when executing the Azure CLI command.	The Azure CLI command did not end within Azure CLI Timeout.	Make sure that the Azure CLI command can be executed properly in EXPRESSCLUSTER server. Check the load status of the server and remove the load. Check the value of Azure CLI Timeout.
azuredns	Error	42	An error occurred in the Azure CLI command.	The Azure CLI command was executed. However, an error was returned.	Make sure that the settings of resources are correct.
azuredns	Error	43	The Azure CLI command could not be executed.	The Azure CLI command could not be executed.	Make sure that the settings of Azure CLI File Path are correct and that Azure CLI is installed properly.
azuredns	Error	99	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.5.20. Google Cloud virtual IP resource

Module type	Type	Return value	Message	Description	Solution
gcvip	Error	5	Port is already used.	Port is already used.	Check if the port specified for Port Number on the local server has already been used.
gcvip	Error	6	Failed to open the port.	Opening the port failed.	Check if memory or OS resources are sufficient.
gcvip	Error	7	Failed to close the port.	Closing the port failed.	Check if memory or OS resources are sufficient.
gcvip	Error	8	Failed to stop the port control process.	Stopping the port control process failed.	Check if memory or OS resources are sufficient. Restart the OS.
gcvip	Error	9	The port control process has already started.	The port control process has already started.	Check if memory or OS resources are sufficient. Or, the immediately preceding deactivation may have failed. In that case, stop the cluster and forcibly terminate the port control process (clpgcvipp.exe) manually.
gcvip	Error	10	Failed to start the port control process.	Starting the port control process failed.	Check if memory or OS resources are sufficient.
gcvip	Error	99	Internal error.	Internal error occurred.	Check if memory or OS resources are sufficient.

10.5.21. Google Cloud DNS resources

Module Type	Type	Return Value	Message	Description	Solution
gcdns	Error	6	Failed to execute start script.	Failed to execute start script.	Memory or OS resources may not be sufficient. Check them.
gcdns	Error	7	Failed to execute stop script.	Failed to execute stop script.	Memory or OS resources may not be sufficient. Check them.
gcdns	Error	8	Returned exit code %1.	The synchronous type script returned abnormal error code.	Check the cause for the abnormal error code.
gcdns	Error	9	Timeout occurred.	Timeout occurred.	Check if the script terminates within the timeout period.
gcdns	Error	10	Failed to log on as a user.	Logon as a user failed	Check if the domain, account and password of the execution user are correctly set.
gcdns	Error	Others	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.5.22. Oracle Cloud virtual IP resource

Module type	Type	Return value	Message	Description	Solution
ocvip	Error	5	Port is already used.	Port is already used.	Check if the port specified for Port Number on the local server has already been used.
ocvip	Error	6	Failed to open the port.	Opening the port failed.	Check if memory or OS resources are sufficient.
ocvip	Error	7	Failed to close the port.	Closing the port failed.	Check if memory or OS resources are sufficient.
ocvip	Error	8	Failed to stop the port control process.	Stopping the port control process failed.	Check if memory or OS resources are sufficient. Restart the OS.
ocvip	Error	9	The port control process has already started.	The port control process has already started.	Check if memory or OS resources are sufficient. Or, the immediately preceding deactivation may have failed. In that case, stop the cluster and forcibly terminate the port control process (clpocvipp.exe) manually.
ocvip	Error	10	Failed to start the port control process.	Starting the port control process failed.	Check if memory or OS resources are sufficient.
ocvip	Error	99	Internal error.	Internal error occurred.	Check if memory or OS resources are sufficient.

10.6. Detailed information of monitor resource errors

The following information is displayed in the message recorded in event logs or alert logs as detail information when monitor resource detects an error.

10.6.1. Application monitor resource

Module Type	Type	Return Value	Message	Description	Solution
appliw	Error	9	Process did not exist. (Stop code : %1)	Process did not exist. (The stop code is displayed only if it can be acquired.)	Process of the monitoring target application resource was cleared due to some error. Check it.
appliw	Error	11	Failed to log on as a user.	Failed to log on as a user.	Check if a domain, an account and a password of the logon user are set properly.
appliw	Warning	Others	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.6.2. CIFS monitor resource

Module Type	Type	Return Value	Message	Description	Solution
cifsw	Error	8	The specified share name can not be found.	The specified share name can not be found.	Check if the setting of file sharing has been canceled.
cifsw	Error	13	Error occurred while doing file check.	Error occurred while doing file check.	Check if local system account has the appropriate access right for executing specified method of monitoring.
cifsw	Error	14	Error occurred while doing folder check.	Error occurred while doing folder check.	Check if local system account has the appropriate access right for executing specified method of monitoring.
cifsw	Error	19	Failed to check the shared configuration file.	Failed to execute checking the configuration data saved in the shared configuration file.	Check if the shared configuration file is corrupted.
cifsw	Warning	21	CIFS control process does not exist.	Failed to start up the process (clpcifsp.exe) that monitors the change of shared configuration.	Activate CIFS resource again.
cifsw	Warning	101	Setting has been changed.	Setting of file sharing has been changed.	Check if the user limit setting or the target folder of file sharing has been changed.
cifsw	Warning	103	Access denied.	Local system account doesn't have the appropriate access right to the shared folder.	Set an access privilege for the local system account.
cifsw	Warning	106	Insufficient memory is available.	Insufficient memory is available.	Memory or OS resources may not be sufficient. Check them.
cifsw	Warning	189	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.6.3. DB2 monitor resource

Module Type	Type	Return Value	Message	Description	Solution
db2w	Warning	190	Initialization has failed[%1].	Initialization process has failed. It may be due to memory allocation failure. Information on the initialization may be displayed on %1.	OS itself may have errors. Restart the server or take other actions.
db2w	Warning	102	The configured value is not correct.	The configured value of the monitoring is not correct.	Check the configured value on the Cluster WebUI because they may not be correct.
db2w	Warning	110	A function error was detected.	A function error occurred.	Monitor applications or OS may have errors. Check the status of the system.
db2w	Error	11	An error was detected in accessing the monitor target.	Accessing the database failed.	Check configured values on the Cluster WebUI (such as a database name). If there is no error, check the database has errors.
db2w	Warning	112	An error was detected in user authentication.	Accessing the database failed.	Check configured values on the Cluster WebUI (such as a user name or a password). If there is no error, check the database has errors.
db2w	Warning	113	An application error was detected.	A database error was detected.	Refer to error messages for database described separately to fix errors.
db2w	Error	14	An error was detected in executing SQL statement [%1].	Executing SQL statement failed. The executed SQL statement is displayed on %1.	Refer to error messages for database described separately to fix errors.
db2w	Error	15	A data error was detected.	A value on the table of database has an error.	Database may be corrupt. Stop the database operation and investigate it. This error may occur when more than one monitoring is performed with the same monitor table name concurrently. Check if the values set in the multi-directional environment are appropriate.
db2w	Warning	140	No license is registered.	The license has not been registered.	Register the license.
db2w	Warning	160	Failed to obtain the configuration data.	The configured value could not be obtained.	OS may have errors. Restart the server or take other actions.
db2w	Warning	190	Internal error.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.6.4. Disk RW monitor resource

Module Type	Type	Return Value	Message	Description	Solution
diskw	Error	5	Failed to open the file.	Failed to open the file.	Check if the disk driver of the monitoring target disk is loaded, the disk is connected properly, the disk is powered on, or no other errors are occurred on the disk. Memory or OS resources may not be sufficient. Check them.
diskw	Error	6	Failed to write in the file.	Failed to write in the file.	Check if the monitoring target disk is connected properly, the disk is powered on, or no other errors are occurred on the disk. Memory or OS resources may not be sufficient. Check them.
diskw	Error	7	Failed to synchronize the disk of the file.	Failed to synchronize the disk of the file.	Check if the monitoring target disk is connected properly, the disk is powered on, or no other errors are occurred on the disk. Memory or OS resources may not be sufficient. Check them.
diskw	Error	8	Failed to close the file.	Failed to close the file.	Check if the monitoring target disk is connected properly, the disk is powered on, or no other errors are occurred on the disk. Memory or OS resources may not be sufficient. Check them.
diskw	Error	71	Timeout has occurred when opening the file.	Timeout has occurred when opening the file.	Check if the monitoring target disk is connected properly, the disk is powered on, or no other errors are occurred on the disk. The system may be under high load, or memory or OS resources may not be sufficient. Check them.
diskw	Error	72	Timeout has occurred when writing in the file.	Timeout has occurred when writing in the file.	Check if the monitoring target disk is connected properly, the disk is powered on, or no other errors are occurred on the disk. The system may be under high load, or memory or OS resources may not be sufficient. Check them.
diskw	Error	73	Timeout has occurred when synchronizing the disk of the file.	Timeout has occurred when synchronizing the disk of the file.	Check if the monitoring target disk is connected properly, the disk is powered on, or no other errors are occurred on the disk. The system may be under high load, or memory or OS resources may not be sufficient. Check them.
diskw	Error	74	Timeout has occurred when closing the file.	Timeout has occurred when closing the file.	Check if the monitoring target disk is connected properly, the disk is powered on, or no other errors are occurred on the disk. The system may be under high load, or memory or OS resources may not be sufficient. Check them.
diskw	Warning	100	Failed to add keep alive drive when initializing keep alive driver.	Failed to add keep alive drive when initializing keep alive driver.	Memory or OS resources may not be sufficient. Check them.
diskw	Warning	101	There is not enough disk space.	There is not enough disk space.	Secure free space on the monitoring target disk.
diskw	Warning	102	Timeout has occurred when initializing internal resources.	Timeout has occurred when initializing internal resources.	Memory or OS resources may not be sufficient. Check them.
diskw	Warning	103	Timeout has occurred when other timing.	Timeout has occurred when other timing.	The system may be under high load, or memory or OS resources may not be sufficient. Check them.
diskw	Warning	104	Failed to allocate memory.	Failed to allocate memory.	Memory or OS resources may not be sufficient. Check them.
diskw	Warning	105	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.
diskw	Warning	190	Initialization error has occurred in internal resource.	Initialization error has occurred in internal resource.	Memory or OS resources may not be sufficient. Check them.

10.6.5. Floating IP monitor resource

Module Type	Type	Return Value	Message	Description	Solution
fipw	Error	6	IP address does not exist.	IP address does not exist.	NIC may have been disabled. Check if the FIP address exists by the ipconfig command.
fipw	Error	11	Adapter Index is different.	Adapter Index is different.	NIC may have been disabled. Check if the FIP address exists by the ipconfig command.
fipw	Error	15	Detected NIC Link Down.	Detected NIC Link Down.	Check if the LAN cable is connected properly.
fipw	Warning	112	Failed to get the IP address list.	Failed to get the IP address list.	Memory or OS resources may not be sufficient. Check them.
fipw	Warning	113	Failed to get the NIC interface name.	Failed to get the NIC interface name.	Memory or OS resources may not be sufficient. Check them.
fipw	Warning	114	Failed to get the NIC status.	Failed to get the NIC status.	Check if the NIC device is supported by the device I/O controller.
fipw	Warning	189	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.6.6. FTP monitor resource

Module Type	Type	Return Value	Message	Description	Solution
ftpw	Error	11	An error was detected in accessing the monitor target.	The access to the monitor application failed.	Check configured values on the Cluster WebUI (such as an IP address). If there is no error, check if the monitor application has errors.
ftpw	Error	12	An error was detected in user authentication.	The user authentication failed.	Check configured values on the Cluster WebUI (such as a user name or a password). If there is no error, check if the monitor application has errors
ftpw	Warning	110	A function error was detected.	A function error occurred.	Monitor applications or OS may have errors. Check the status of the system.
ftpw	Warning	113	An application error was detected.	A monitor application error was detected.	Refer to error messages for monitor applications described separately to fix errors.
ftpw	Warning	115	A data error was detected.	A value of the response data has an error.	Refer to error messages for monitor applications described separately to fix errors.
ftpw	Warning	140	No license is registered.	The license has not been registered.	Register the license.
ftpw	Warning	188	Internal error.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.
ftpw	Warning	190	Initialization has failed[%1].	Initialization process has failed. It may be due to memory allocation failure or a failure in obtaining the configured value. Information on the initialization may be displayed on %1.	The configured value of the Cluster WebUI may be incorrect. Check the value. If there is no problem with the value, OS itself may have errors. Restart the server or take other actions

10.6.7. Custom monitor resource

Module Type	Type	Return Value	Message	Description	Solution
genw	Error	5	Failed to start script.	Failed to start script.	Check if the script can be executed.
genw	Error	6	Script did not exist.	The asynchronous type script terminated abnormally.	Check the cause of the termination of the script.
genw	Error	8	Returned exit code %1.	The synchronous type script returned abnormal error code.	Check the cause for the abnormal error code.
genw	Error	9	Failed to log on as a user.	Logon as a user failed	Check if the domain, account and password of the execution user are correctly set.
genw	Warning	100	Timeout occurred.	The synchronous type script did not terminate within the timeout period.	Check the cause of the delay of the script.
genw	Warning	100	Returned exit code %1.	The synchronous type script returned abnormal error code.	Check the cause for the abnormal error code.
genw	Warning	100 190	Script path is invalid.	The configured value of the script path is not correct.	Check the configured value on the Cluster WebUI.
genw	Warning	100 190	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.
genw	Warning	190	Parameter is invalid.	The configured value of the monitoring is not correct.	Check the configured value on the Cluster WebUI.
genw	Warning	190	Resource does not exist in cluster configuration data.	The cluster configuration data is not correct.	Check the cluster configuration data on the Cluster WebUI.
genw	Warning	190	Failed to get the value from cluster configuration data.	The cluster configuration data is not correct.	Check the cluster configuration data on the Cluster WebUI.
genw	Warning	190	Script did not exist.	The asynchronous type script terminated abnormally.	Check the cause of the termination of the script.
genw	Error	200	Failed to start script.	Failed to start script.	Check if the script can be executed.

10.6.8. Hybrid disk TUR monitor resource

Module Type	Type	Return Value	Message	Description	Solution
hdtw	Error	4	Failed to open device. Check the disk status of monitor destination volume.	Failed to open device. Check the disk status of monitor destination volume.	Check if the disk driver of the monitoring target disk is loaded, the device exists, the disk is connected properly, the disk is powered on, or no other errors are occurred on the disk. Memory or OS resources may not be sufficient. Check them.
hdtw	Error	5	Failed to control device. Check the disk status of monitor destination volume.	Failed to control device. Check the disk status of monitor destination volume.	Check if the monitoring target disk is connected properly, the disk is powered on, or no other errors are occurred on the disk.
hdtw	Warning	100	Other internal error has occurred. Check the system resource.	Other internal error has occurred. Check the system resource.	Memory or OS resources may not be sufficient. Check them.
hdtw	Warning	190	Initialization has failed. Check the cluster configuration data or system resources.	Initialization has failed. Check the cluster configuration data or system resources.	Memory or OS resources may not be sufficient. Check them.

10.6.9. Hybrid disk monitor resource

Module Type	Type	Return Value	Message	Description	Solution
hdw	Error	3	HDR %1 has old data.	The information in the activated hybrid disk %1 is not updated.	Check the status of the hybrid disk with Mirror disks.
hdw	Error	4	A disk error is detected in HDR %1.	A disk error has been detected in hybrid disk %1.	Make sure there is no HW failure in the disk or disk path where cluster partition or data partition exists.
hdw	Error	5	The status of HDR %1 is invalid.	The status of the hybrid disk %1 is invalid.	Restart the cluster.
hdw	Warning	101	HDR %1 recovery is in progress.	Hybrid disk %1 is being copied.	Wait for a while until mirror recovery completes.
hdw	Warning	102	HDR %1 is not being mirrored.	Hybrid disk %1 has not been mirrored.	Check the status of the hybrid disk with Mirror disks.
hdw	Warning	103	HDR %1 is activated on more than one server.	Hybrid disk %1 is activated on both server groups.	Deactivate the hybrid disk on one of the server groups.
hdw	Warning	104	The status of HDR %1 is unknown.	Hybrid disk to be monitored is stopped.	Stop the monitor resource or start the hybrid disk to be monitored.
hdw	Warning	105	Whether HDR %1 data is old/new is not determined.	Whether the data in hybrid disk %1 is old or new has not been determined.	Activate the hybrid disk on one of the servers.
hdw	Warning	106	Internal error.	An internal error has occurred.	Memory or OS resources may not be sufficient. Check them.

10.6.10. HTTP monitor resource

Module Type	Type	Return Value	Message	Description	Solution
httpw	Error	11	An error was detected in accessing the monitor target.	The access to the monitor application failed.	Check configured values on the Cluster WebUI (such as an IP address). If there is no error, check if the monitor application has errors.
httpw	Warning	110	A function error was detected.	A function error occurred.	Monitor applications or OS may have errors. Check the status of the system.
httpw	Warning	113	An application error was detected.	A monitor application error was detected.	Refer to error messages for monitor applications described separately to fix errors.
httpw	Warning	115	A data error was detected.	A value of the response data has an error.	Refer to error messages for monitor applications described separately to fix errors.
httpw	Warning	140	No license is registered.	The license has not been registered.	Register the license.
httpw	Warning	188	Internal error.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.
httpw	Warning	190	Initialization has failed[%1].	Initialization process has failed. It may be due to memory allocation failure or a failure in obtaining the configured value. Information on the initialization may be displayed on %1.	The configured value of the Cluster WebUI may be incorrect. Check the value. If there is no problem with the value, OS itself may have errors. Restart the server or take other actions.

10.6.11. IMAP4 monitor resource

Module Type	Type	Return Value	Message	Description	Solution
imap4w	Error	11	An error was detected in accessing the monitor target.	The access to the monitor application failed.	Check configured values on the Cluster WebUI (such as an IP address). If there is no error, check if the monitor application has errors.
imap4w	Error	12	An error was detected in user authentication.	The access to the monitor application failed.	Check configured values on the Cluster WebUI (such as a user name or a password). If there is no error, check if the monitor application has errors.
imap4w	Warning	110	A function error was detected.	A function error occurred.	Monitor applications or OS may have errors. Check the status of the system.
imap4w	Warning	113	An application error was detected.	A monitor application error was detected.	Refer to error messages for monitor applications described separately to fix errors.
imap4w	Warning	115	A data error was detected.	A value of the response data has an error.	Refer to error messages for monitor applications described separately to fix errors.
imap4w	Warning	140	No license is registered.	The license has not been registered.	Register the license.
imap4w	Warning	188	Internal error.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.
imap4w	Warning	190	Initialization has failed[%1].	Initialization process has failed. It may be due to memory allocation failure or a failure in obtaining the configured value. Information on the initialization may be displayed on %1.	The configured value of the Cluster WebUI may be incorrect. Check the value. If there is no problem with the value, OS itself may have errors. Restart the server or take other actions

10.6.12. IP monitor resource

Module Type	Type	Return Value	Message	Description	Solution
ipw	Error	4	Ping could not reach.	Ping could not reach.	Check if the ping command to the corresponding IP address succeeds. When the command fails, check the status of the device that has the IP address and the network interface.
ipw	Warning	105	Timeout occurred.	Timeout occurred.	Memory or OS resources may not be sufficient. Check them.
ipw	Warning	189	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.6.13. Mirror disk monitor resource

Module Type	Type	Return Value	Message	Description	Solution
mdw	Error	3	Mirror disk %1 is abnormal.	Mirror disk %1 is abnormal.	The mirror disk of the local server has errors. Check it on the mirror disks.
mdw	Warning	101	Mirror disk %1 recovery is in progress.	Mirror disk %1 recovery is in progress.	Wait for a while until the mirror recovery completes.
mdw	Warning	102	Mirror disk %1 is not being mirrored.	Mirror disk %1 is not being mirrored.	Check the mirror disk on the mirror disks.
mdw	Warning	103	Mirror disk %1 is uncertain status.	Mirror disk %1 is uncertain status.	Check the mirror disk on the mirror disks.
mdw	Warning	104	Mirror disk %1 is activated on more than one server.	Mirror disk %1 is activated on more than one server.	When activation of the mirror disk resources on both servers is detected, the server is automatically shut down. Restart the server.
mdw	Warning	105	Mirror disk %1 is unknown status.	Mirror disk %1 is unknown status.	Memory or OS resources may not be sufficient. Check them.
mdw	Warning	106	Internal error.	Internal error.	Memory or OS resources may not be sufficient. Check them.

10.6.14. Mirror connect monitor resource

Module Type	Type	Return Value	Message	Description	Solution
mdnw	Warning	100	Network was interrupted.	Network was interrupted.	Check the connection status of the mirror connect.
mdnw	Warning	101	An internal error has occurred.	An internal error has occurred.	Memory or OS resources may not be sufficient. Check them.

10.6.15. NIC Link Up/Down monitor resource

Module Type	Type	Return Value	Message	Description	Solution
miiw	Error	4	IP address does not exist.	IP address does not exist.	NIC may have been disabled. Check if the IP address of the specified NIC exists by the ipconfig command.
miiw	Error	8	Detected NIC Link Down.	Detected NIC Link Down.	Check if the LAN cable is connected properly.
miiw	Warning	105	Failed to get the IP address list.	Failed to get the IP address list.	Memory or OS resources may not be sufficient. Check them.
miiw	Warning	106	Failed to get the NIC interface name.	Failed to get the NIC interface name.	Memory or OS resources may not be sufficient. Check them.
miiw	Warning	107	Failed to get the NIC status.	Failed to get the NIC status.	Check if the NIC device is supported by the device I/O controller.
miiw	Warning	189	An internal error has occurred.	An internal error has occurred.	Memory or OS resources may not be sufficient. Check them.

10.6.16. Multi target monitor resource

Module Type	Type	Return Value	Message	Description	Solution
mtw	Error	Other	Internal error occurred.(status:%1!d!)	Internal error occurred.(status:%1!d!)	Memory or OS resources may not be sufficient. Check them.
mtw	Error	5	Status of resources is abnormal.	Status of resources is abnormal.	Check the status of the monitor resources listed on the monitor resources list.
mtw	Error	1	This option is invalid.	This option is invalid.	Memory or OS resources may not be sufficient. Check them.

10.6.17. NAS monitor resource

Module Type	Type	Return Value	Message	Description	Solution
nasw	Error	5	Invalid nas drive. drv:%1	The target drive is not the network drive.	Check if the drive letters have been changed
nasw	Error	7	The network resource is not connected. path:%1	The target drive is not being mounted.	Check if the network drive has been unmounted.
nasw	Error	8	The network resource is different from that of the configuration value. drv:%1	The network resource is different from that of the configuration value.	Check if the setting of the network drive has been changed.
nasw	Warning	106	Failed to get the network resource mapped by the specified drive. drv:%1 errcode:%2	The target drive is not being mounted.	Check if the network drive has been unmounted.
nasw	Warning	189	An internal error has occurred.	An internal error has occurred.	Memory or OS resources may not be sufficient. Check them.

10.6.18. Process name monitor resource

Module Type	Type	Return Value	Message	Description	Solution
psw	Error	4	Process [%1, pid=%2] down.	Loss of the process to be monitored has been detected.	Check whether the process to be monitored is running properly.
psw	Error	5	The number of processes is less than the specified minimum process count. %1/%2 (%3)	The number of running processes to be monitored does not reach the specified lower limit.	Check whether the process to be monitored is running properly.
psw	Warning	100	Internal error occurred.	An internal error has occurred.	Check the following possible causes: memory shortage or OS resource insufficiency. Check it.
psw	Warning	190	Parameter is invalid.	The monitor setting value is incorrect.	The setting value for the Cluster WebUI may be incorrect. Check it.

10.6.19. ODBC monitor resource

Module Type	Type	Return Value	Message	Description	Solution
odbcw	Warning	190	Initialization has failed[%1].	Initialization process has failed. It may be due to memory allocation failure. Information on the initialization may be displayed on %1.	OS itself may have errors. Restart the server or take other actions.
odbcw	Warning	102	The configured value is not correct.	The configured value of the monitoring is not correct.	Check the configured value on the Cluster WebUI because it may not be correct.
odbcw	Warning	110	A function error was detected.	A function error occurred.	Monitor applications or OS may have errors. Check the status of the system.
odbcw	Error	11	An error was detected in accessing the monitor target.	The access to the database failed.	Check configured values on the Cluster WebUI (such as a database name). If there is no error, check the database has errors.
odbcw	Warning	112	An error was detected in user authentication.	The access to the database failed.	Check configured values on the Cluster WebUI (such as a user name or a password). If there is no error, check if the database has errors.
odbcw	Warning	113	An application error was detected.	The database error was detected.	Refer to error messages for database described separately to fix errors.
odbcw	Error	14	An error was detected in executing SQL statement [%1].	Executing SQL statement failed. The executed SQL statement is displayed on %1.	Refer to error messages for database described separately to fix errors.
odbcw	Error	15	A data error was detected.	A value on the table of database has an error.	Database may be corrupt. Stop the database operation and investigate it. This error may occur when more than one monitoring is performed with the same monitor table name concurrently. Check if the values set in the multi-directional environment are appropriate.
odbcw	Warning	140	No license is registered.	The license has not been registered.	Register the license.
odbcw	Warning	160	Failed to obtain the configuration data.	The configured value could not be obtained.	OS may have errors. Restart the server or take other actions
odbcw	Warning	190	Internal error.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.6.20. Oracle monitor resource

Module Type	Type	Return Value	Message	Description	Solution
oraclew	Warning	190	Initialization has failed[%1].	Initialization process has failed. It may be due to memory allocation failure. Information on the initialization may be displayed on %1.	OS itself may have errors. Restart the server or take other actions
oraclew	Warning	102	The configured value is not correct.	The configured value of the monitoring is not correct.	Check the configured value on the Cluster WebUI because it may not be correct.
oraclew	Warning	110	A function error was detected.	A function error occurred.	Monitor applications or OS may have errors. Check the status of the system.
oraclew	Error	11	An error was detected in accessing the monitor target.	The access to the database failed.	Check configured values on the Cluster WebUI (such as a database name). If there is no error, check the database has errors.
oraclew	Warning	112	An error was detected in user authentication.	The access to the database failed.	Check configured values on the Cluster WebUI (such as a user name or a password). If there is no error, check if the database has errors.
oraclew	Warning	113	An application error was detected.	The database error was detected.	Refer to error messages for database described separately to fix errors.
oraclew	Error	14	An error was detected in executing SQL statement [%1].	Executing SQL statement failed. The executed SQL statement is displayed on %1.	Refer to error messages for database described separately to fix errors.
oraclew	Error	15	A data error was detected.	A value on the table of database has an error.	Database may be corrupt. Stop the database operation and investigate it. This error may occur when more than one monitoring is performed with the same monitor table name concurrently. Check if the values set in the multi-directional environment are appropriate.
oraclew	Warning	140	No license is registered.	The license has not been registered.	Register the license.
oraclew	Warning	160	Failed to obtain the configuration data.	The configured value could not be obtained.	OS may have errors. Restart the server or take other actions.
oraclew	Warning	190	Internal error.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.6.21. POP3 monitor resource

Module Type	Type	Return Value	Message	Description	Solution
pop3w	Error	11	An error was detected in accessing the monitor target.	The access to the monitor application failed.	Check configured values on the Cluster WebUI (such as an IP address). If there is no error, check if the monitor application has errors.
pop3w	Error	12	An error was detected in user authentication.	The access to the monitor application failed.	Check configured values on the Cluster WebUI (such as a user name or a password). If there is no error, check if the monitor application has errors.
pop3w	Warning	110	A function error was detected.	A function error occurred.	Monitor applications or OS may have errors. Check the status of the system.
pop3w	Warning	113	An application error was detected.	The monitor application error was detected.	Refer to error messages for monitor applications described separately to fix errors.
pop3w	Warning	115	A data error was detected.	A value of the response data has an error.	Refer to error messages for monitor applications described separately to fix errors.
pop3w	Warning	140	No license is registered.	The license has not been registered.	Register the license.
pop3w	Warning	188	Internal error.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.
pop3w	Warning	190	Initialization has failed[%1].	Initialization process has failed. It may be due to memory allocation failure or a failure in obtaining the configured value. Information on the initialization may be displayed on %1.	The configured value of the Cluster WebUI may be incorrect. Check the value. If there is no problem with the value, OS itself may have errors. Restart the server or take other actions.

10.6.22. PostgreSQL monitor resource

Module Type	Type	Return Value	Message	Description	Solution
psqlw	Warning	190	Initialization has failed[%1].	Initialization process has failed. It may be due to memory allocation failure. Information on the initialization may be displayed on %1.	OS itself may have errors. Restart the server or take other actions.
psqlw	Warning	102	The configured value is not correct.	The configured value of the monitoring is not correct.	Check the configured value on the Cluster WebUI because it may not be correct.
psqlw	Warning	110	A function error was detected.	A function error occurred.	Monitor applications or OS may have errors. Check the status of the system.
psqlw	Error	11	An error was detected in accessing the monitor target.	The access to the database failed.	Check configured values on the Cluster WebUI (such as a database name). If there is no error, check the database has errors.
psqlw	Warning	112	An error was detected in user authentication.	The access to the database failed.	Check configured values on the Cluster WebUI (such as a user name or a password). If there is no error, check if the database has errors.
psqlw	Warning	113	An application error was detected.	The database error was detected.	Refer to error messages for database described separately to fix errors.
psqlw	Error	14	An error was detected in executing SQL statement [%1].	Executing SQL statement failed. The executed SQL statement is displayed on %1.	Refer to error messages for database described separately to fix errors.
psqlw	Error	15	A data error was detected.	A value on the table of database has an error.	Database may be corrupt. Stop the database operation and investigate it. This error may occur when more than one monitoring is performed with the same monitor table name concurrently. Check if the values set in the multi-directional environment are appropriate.
psqlw	Warning	140	No license is registered.	The license has not been registered.	Register the license.
psqlw	Warning	160	Failed to obtain the configuration data.	The configured value could not be obtained.	OS may have errors. Restart the server or take other actions.
psqlw	Warning	190	Internal error.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.6.23. Registry synchronization monitor resource

Module Type	Type	Return Value	Message	Description	Solution
regsyncw	Error	50	Failed to save registry.	The process of storing to a file at detection of registry update failed.	Check if the process other than EXPRESSCLUSTER opens the registry storage file. Memory or OS resources may not be sufficient. Check the status of the system.
regsyncw	Warning	101	Setting of registry keys is invalid.	An invalid registry key is registered to the resource.	Check the value set on the Cluster WebUI (Details on Resource Properties), and change to a correct registry key.
regsyncw	Warning	191	Delivery processing to other nodes has failed.	Registry storage files cannot be delivered to other nodes.	There may be an error on the connection to the other node. Check the status of the network. OS of the local or other server may have an error. Check the status of the system.

10.6.24. Disk TUR monitor resource

Module Type	Type	Return Value	Message	Description	Solution
sdw	Error	4	Failed to open device. Check the disk status of monitor destination volume.	Failed to open device. Check the disk status of monitor destination volume.	Check if the disk driver of the monitoring target disk is loaded, the device exists, the disk is connected properly, the disk is powered on, or no other errors are occurred on the disk. Memory or OS resources may not be sufficient. Check them.
sdw	Error	5	Failed to control device. Check the disk status of monitor destination volume.	Failed to control device. Check the disk status of monitor destination volume.	Check if the monitoring target disk is connected properly, the disk is powered on, or no other errors are occurred on the disk.
sdw	Warning	100	Other internal error has occurred. Check the system resource.	Other internal error has occurred. Check the system resource.	Memory or OS resources may not be sufficient. Check them.
sdw	Warning	190	Initialization has failed. Check the cluster configuration data or system resources.	Initialization has failed. Check the cluster configuration data or system resources.	Memory or OS resources may not be sufficient. Check them.

10.6.25. Service monitor resource

Module Type	Type	Return Value	Message	Description	Solution
servicew	Error	9	Service has been stopped.	Service has been stopped.	Check the status of the service.
servicew	Warning	100	Failed to obtain the service control right.	Failed to obtain the service control right.	Check if the service name is correct.
servicew	Warning	Others	An internal error has occurred.	An internal error has occurred.	Memory or OS resources may not be sufficient. Check them.

10.6.26. Print spooler monitor resource

Module Type	Type	Return Value	Message	Description	Solution
spoolw	Error	2	Print spooler service has been stopped.	Print spooler service has been stopped.	Start the print spooler service.
spoolw	Error	3	Print spooler service has not been started.(%1)	Print spooler service has not been started.(%1)	Start the print spooler service.
spoolw	Warning	190	Failed to get status of print spooler service.(errcode:%1)	Failed to get status of print spooler service.(errcode:%1)	Check the status of the print spooler service.
spoolw	Warning	191	Print spooler service is being started.	Print spooler service is being started.	Check the status of the print spooler service.

10.6.27. SMTP monitor resource

Module Type	Type	Return Value	Message	Description	Solution
smtpw	Error	11	An error was detected in accessing the monitor target.	The access to the monitor application failed.	Check configured values on the Cluster WebUI (such as an IP address). If there is no error, check if the monitor application has errors.
smtpw	Error	12	An error was detected in user authentication.	The access to the monitor application failed.	Check configured values on the Cluster WebUI (such as a user name or a password). If there is no error, check if the monitor application has errors.
smtpw	Warning	110	A function error was detected.	A function error occurred.	Monitor applications or OS may have errors. Check the status of the system.
smtpw	Warning	113	An application error was detected.	The monitor application error was detected.	Refer to error messages for monitor applications described separately to fix errors.
smtpw	Warning	115	A data error was detected.	A value of the response data has an error.	Refer to error messages for monitor applications described separately to fix errors.
smtpw	Warning	140	No license is registered.	The license has not been registered.	Register the license.
smtpw	Warning	188	Internal error.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.
smtpw	Warning	190	Initialization has failed[%1].	Initialization process has failed. It may be due to memory allocation failure or a failure in obtaining the configured value. Information on the initialization may be displayed on %1.	The configured value of the Cluster WebUI may be incorrect. Check the value. If there is no problem with the value, OS itself may have errors. Restart the server or take other actions.

10.6.28. SQL Server monitor resource

Module Type	Type	Return Value	Message	Description	Solution
sqlserverw	Warning	190	Initialization has failed[%1].	Initialization process has failed. It may be due to memory allocation failure. Information on the initialization may be displayed on %1.	OS itself may have errors. Restart the server or take other actions.
sqlserverw	Warning	102	The configured value is not correct.	The configured value of the monitoring is not correct.	Check the configured value on the Cluster WebUI because it may not be correct.
sqlserverw	Warning	110	A function error was detected.	A function error occurred.	Monitor applications or OS may have errors. Check the status of the system.
sqlserverw	Error	11	An error was detected in accessing the monitor target.	The access to the database failed.	Check configured values on the Cluster WebUI (such as a database name). If there is no error, check the database has errors.
sqlserverw	Warning	112	An error was detected in user authentication.	The access to the database failed.	Check configured values on the Cluster WebUI (such as a user name or a password). If there is no error, check if the database has errors.
sqlserverw	Warning	113	An application error was detected.	The database error was detected.	Refer to error messages for database described separately to fix errors.
sqlserverw	Error	14	An error was detected in executing SQL statement [%1].	Executing SQL statement failed. The executed SQL statement is displayed on %1.	Refer to error messages for database described separately to fix errors.
sqlserverw	Error	15	A data error was detected.	A value on the table of database has an error.	Database may be corrupt. Stop the database operation and investigate it. This error may occur when more than one monitoring is performed with the same monitor table name concurrently. Check if the values set in the multi-directional environment are appropriate.
sqlserverw	Warning	140	No license is registered.	The license has not been registered.	Register the license.
sqlserverw	Warning	160	Failed to obtain the configuration data.	The configured value could not be obtained.	OS may have errors. Restart the server or take other actions.
sqlserverw	Warning	190	Internal error.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.6.29. Tuxedo monitor resource

Module Type	Type	Return Value	Message	Description	Solution
tuxw	Error	11	An error was detected in accessing the monitor target.	The access to the monitor application failed.	Check configured values on the Cluster WebUI (such as an application config file). If there is no error, check if the monitor application has errors.
tuxw	Warning	110	A function error was detected.	A function error occurred.	Monitor applications or OS may have errors. Check the status of the system.
tuxw	Warning	113	An application error was detected.	The monitor application error was detected.	Refer to error messages for monitor applications described separately to fix errors.
tuxw	Warning	140	No license is registered.	The license has not been registered.	Register the license.
tuxw	Warning	188	Internal error.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.
tuxw	Warning	190	Initialization has failed[%1].	Initialization process has failed. It may be due to memory allocation failure or a failure in obtaining the configured value. Information on the initialization may be displayed on %1.	The configured value of the Cluster WebUI may be incorrect. Check the value. If there is no problem with the value, OS itself may have errors. Restart the server or take other actions.

10.6.30. Virtual computer name monitor resource

Module Type	Type	Return Value	Message	Description	Solution
vcomw	Error	5	VCOM control process has already been started.	VCOM control process has already been started.	Memory or OS resources may not be sufficient. Check them. Restart the OS.
vcomw	Error	6	VCOM control process has not been started.	VCOM control process has not been started.	Memory or OS resources may not be sufficient. Check them. Restart the OS.
vcomw	Error	8	VCOM control process does not exist.	VCOM control process does not exist.	The VCOM control process ID does not exist. Restart the OS.
vcomw	Warning	189	An internal error has occurred.	An internal error has occurred.	Memory or OS resources may not be sufficient. Check them.

10.6.31. Virtual IP monitor resource

Module Type	Type	Return Value	Message	Description	Solution
vipw	Error	6	IP address does not exist.	IP address does not exist.	NIC may have been disabled. Check if the VIP address exists by the ipconfig command.
vipw	Error	11	Adapter Index is different.	Adapter Index is different.	NIC may have been disabled. Check if the VIP address exists by the ipconfig command.
vipw	Warning	189	An internal error has occurred.	An internal error has occurred.	Memory or OS resources may not be sufficient. Check them.

10.6.32. VM monitor resource

Module Type	Type	Return Value	Message	Description	Solution
vmw	Error	12	Virtual machine is unnormal [%1]	The status of the virtual machine is other than Running.	Check the status of the virtual machine on Hyper-V manager.
vmw	Error	Others	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.6.33. WebSphere monitor resource

Module Type	Type	Return Value	Message	Description	Solution
wasw	Error	12	An error was detected in user authentication.	The access to the monitor application failed.	Check configured values on the Cluster WebUI (such as a user name or a password). If there is no error, check if the monitor application has errors.
wasw	Warning	110	A function error was detected.	A function error occurred.	Monitor applications or OS may have errors. Check the status of the system.
wasw	Warning	113	An application error was detected.	The monitor application error was detected.	Refer to error messages for monitor applications described separately to fix errors.
wasw	Warning	140	No license is registered.	The license has not been registered.	Register the license.
wasw	Warning	188	Internal error.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.
wasw	Warning	190	Initialization has failed[%1].	Initialization process has failed. It may be due to memory allocation failure or a failure in obtaining the configured value. Information on the initialization may be displayed on %1.	The configured value of the Cluster WebUI may be incorrect. Check the value. If there is no problem with the value, OS itself may have errors. Restart the server or take other actions.

10.6.34. WebLogic monitor resource

Module Type	Type	Return Value	Message	Description	Solution
wlsw	Error	11	An error was detected in accessing the monitor target.	The access to the monitor application failed.	Check configured values on the Cluster WebUI (such as an IP address). If there is no error, check if the monitor application has errors.
wlsw	Error	12	An error was detected in user authentication.	The access to the monitor application failed.	Check configured values on the Cluster WebUI (such as a user name or a password). If there is no error, check if the monitor application has errors.
wlsw	Warning	110	A function error was detected.	A function error occurred.	Monitor applications or OS may have errors. Check the status of the system.
wlsw	Warning	113	An application error was detected.	The monitor application error was detected.	Refer to error messages for monitor applications described separately to fix errors.
wlsw	Warning	140	No license is registered.	The license has not been registered.	Register the license.
wlsw	Warning	188	Internal error.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.
wlsw	Warning	190	Initialization has failed[%1].	Initialization process has failed. It may be due to memory allocation failure or a failure in obtaining the configured value. Information on the initialization may be displayed on %1.	The configured value of the Cluster WebUI may be incorrect. Check the value. If there is no problem with the value, OS itself may have errors. Restart the server or take other actions.

10.6.35. WebOTX monitor resource

Module Type	Type	Return Value	Message	Description	Solution
otxw	Error	11	An error was detected in accessing the monitor target.	The access to the monitor application failed.	Check configured values on the Cluster WebUI (such as an IP address or an application server name). If there is no error, check if the monitor application has errors.
otxw	Error	12	An error was detected in user authentication.	The access to the monitor application failed.	Check configured values on the Cluster WebUI (such as a user name or a password). If there is no error, check if the monitor application has errors.
otxw	Warning	110	A function error was detected.	A function error occurred.	Monitor applications or OS may have errors. Check the status of the system.
otxw	Warning	113	An application error was detected.	The monitor application error was detected.	Refer to error messages for monitor applications described separately to fix errors.
otxw	Warning	140	No license is registered.	The license has not been registered.	Register the license.
otxw	Warning	188	Internal error.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.
otxw	Warning	190	Initialization has failed[%1].	Initialization process has failed. It may be due to memory allocation failure or a failure in obtaining the configured value. Information on the initialization may be displayed on %1.	The configured value of the Cluster WebUI may be incorrect. Check the value. If there is no problem with the value, OS itself may have errors. Restart the server or take other actions.

10.6.36. JVM monitor resource

Module Type	Type	Return Value	Message	Description	Solution
jraw	Error	11	An error was detected in accessing the monitor target.	Connection to the target to be monitored has failed.	Check that the Java VM to be monitored is running.
jraw	Error	12	%1 to be monitored has become abnormal. %1:Error generation cause	An error in the target to be monitored has been detected.	Based on the message, check the Java application that is running on Java VM to be monitored.
jraw	Warning	192	Internal error occurred.	An internal error has occurred.	Execute cluster suspend and cluster resume.

10.6.37. System monitor resource

Module Type	Type	Return Value	Message	Description	Solution
sraw	Error	11	Monitor sraw has detected an error. (11: Detected an error in monitoring system resource.)	An error was detected when monitoring system resources.	There may be an error with the resources.

10.6.38. Process resource monitor resource

Module Type	Type	Return Value	Message	Description	Solution
psrw	Error	11	Monitor psrw has detected an error. (11: Detected an error in monitoring process resource.)	An error was detected when monitoring process resources.	There may be an error with the resources. Check them.

10.6.39. User space monitoring resource

Module Type	Type	Return Value	Message	Description	Solution
userw	Error	71	Timeout has occurred when creating dummy thread.	Timeout has occurred when creating dummy thread.	The system may be under high load, or memory or OS resources may not be sufficient. Check them.
userw	Warning	100	A timeout occurred when initializing internal resources.	A timeout occurred when initializing internal resources.	Memory or OS resources may not be sufficient. Check them.
userw	Warning	101	Timeout has occurred when closing dummy thread handle.	Timeout has occurred when closing dummy thread handle.	The system may be under high load, or memory or OS resources may not be sufficient. Check them.
userw	Warning	102	Timeout has occurred when other timing.	Timeout has occurred when other timing.	The system may be under high load, or memory or OS resources may not be sufficient. Check them.
userw	Warning	190	An initialization error has occurred in an internal resource.	An initialization error has occurred in an internal resource.	Memory or OS resources may not be sufficient. Check them.

10.6.40. Dynamic DNS monitoring resource

Module Type	Type	Return Value	Message	Description	Solution
ddnsw	Error	5	Query to DNS has failed.	Query to DNS has failed.	Check the DNS server setting. Make sure that communication with the DNS server is enabled.
ddnsw	Warning	13	DDNS control process has already started.	DDNS control process has already started.	Memory or OS resources may not be sufficient. Check them. Or, the previous activation might fail. In this case, stop the cluster and kill the DDNS control process (clpddnsp.exe) manually.
ddnsw	Warning	14	DDNS control process is not running.	DDNS control process is not running.	Check the DNS server setting. Make sure that communication with the DNS server is enabled. Or, memory or OS resources may not be sufficient. Check them.
ddnsw	Warning	16	Failed to start DDNS control process.	Failed to start DDNS control process.	Check the DNS server setting. Make sure that communication with the DNS server is enabled. Or, memory or OS resources may not be sufficient. Check them.
ddnsw	Warning	17	Failed to stop DDNS control process.	Failed to stop DDNS control process.	Check the DNS server setting. Make sure that communication with the DNS server is enabled. Or, memory or OS resources may not be sufficient. Check them.
ddnsw	Warning	18	DDNS control process path is invalid.	DDNS control process path is invalid.	The executable file is damaged, or memory or OS resources may not be sufficient. Check them.
ddnsw	Warning	106	Failed to delete DNS.	Failed to delete DNS.	Check the DNS server setting. Make sure that communication with the DNS server is enabled.
ddnsw	Warning	107	Failed to update DNS.	Failed to update DNS.	Check the DNS server setting. Make sure that communication with the DNS server is enabled.
ddnsw	Warning	108	A reception timeout occurred.	A reception timeout occurred.	Memory or OS resources may not be sufficient. Check them.
ddnsw	Warning	109	Failed to send to the DNS server.	Failed to send to the DNS server.	Check the DNS server setting. Make sure that communication with the DNS server is enabled.
ddnsw	Warning	110	Failed to receive from the DNS server.	Failed to receive from the DNS server.	Check the DNS server setting. Make sure that communication with the DNS server is enabled.
ddnsw	Warning	111	Ping has not reached.	Ping has not reached.	Check whether the ping command is successfully executed for the target IP address. If the ping command failed, check the status of the device that uses the target IP address, or the network interface status.
ddnsw	Warning	112	Ping timeout occurred.	Ping timeout occurred.	Memory or OS resources may not be sufficient. Check them.
ddnsw	Warning	189	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.
ddnsw	Warning	190	Initialization has failed.	Initialization process has failed. A failure in obtaining the configuration data might occur.	Check the cluster configuration data.

10.6.41. AWS elastic ip monitor resources

Module type	Type	Return value	Message	Description	Solution
awseipw	Error	5	AWS CLI command failed.	Failed in the AWS CLI command.	Check if the settings in the AWS CLI file are correct.
awseipw	Error	6	Timeout occurred.	Timeout occurred.	Memory or OS resources may not be sufficient. Check them.
awseipw	Error	7	The EIP address does not exist.	The EIP address does not exist.	The EIP may have been detached. Check it.
awseipw	Warning	105	AWS CLI command failed.	Failed in the AWS CLI command.	Check if the settings in the AWS CLI file are correct.
awseipw	Warning	106	Timeout occurred.	Timeout occurred.	Memory or OS resources may not be sufficient. Check them.
awseipw	Warning	189	Internal error occurred.	Internal error occurred.	Check if Python is installed correctly. Check if AWS CLI is installed correctly. Memory or OS resources may not be sufficient. Check them.

10.6.42. AWS virtual ip monitor resources

Module type	Type	Return value	Message	Description	Solution
awsvipw	Error	5	AWS CLI command failed.	Failed in the AWS CLI command.	Check if the settings in the AWS CLI file are correct.
awsvipw	Error	6	Timeout occurred.	Timeout occurred.	Memory or OS resources may not be sufficient. Check them.
awsvipw	Error	7	The VIP address does not exist.	The VIP address does not exist.	NIC may have been disabled. Check if the VIP address exists with the ifconfig command.
awsvipw	Error	8	The routing for VIP was changed.	The routing for VIP was changed.	The VIP routing may have been changed. Check the Route Tables of the VPC.
awsvipw	Warning	105	AWS CLI command failed.	Failed in the AWS CLI command.	Check if the settings in the AWS CLI file are correct.
awsvipw	Warning	106	Timeout occurred.	Timeout occurred.	Memory or OS resources may not be sufficient. Check them.
awsvipw	Warning	189	Internal error occurred.	Internal error occurred.	Check if Python is installed correctly. Check if AWS CLI is installed correctly. Memory or OS resources may not be sufficient. Check them.

10.6.43. AWS AZ monitor resources

Module type	Type	Return value	Message	Description	Solution
awsazw	Error	4	Failed to monitor the availability zone.	Failed to monitor the availability zone.	The availability zone to which the server belongs may have a problem. Check it.
awsazw	Error	5	AWS CLI command failed.	Failed in the AWS CLI command.	Check if the settings in the AWS CLI file are correct.
awsazw	Error	5	Invalid availability zone: [%1]	The specified availability zone %1 does not exist.	Check if the settings of the availability zone are correct.
awsazw	Error	6	Timeout occurred.	Timeout occurred.	Memory or OS resources may not be sufficient. Check them.
awsazw	Warning	105	AWS CLI command failed.	Failed in the AWS CLI command.	Check if the settings in the AWS CLI file are correct.
awsazw	Warning	105	Invalid availability zone: [%1]	The specified availability zone %1 does not exist.	Check if the settings of the availability zone are correct.
awsazw	Warning	106	Timeout occurred.	Timeout occurred.	Memory or OS resources may not be sufficient. Check them.
awsazw	Warning	189	Internal error occurred.	Internal error occurred.	Check if Python is installed correctly. Check if AWS CLI is installed correctly. Memory or OS resources may not be sufficient. Check them.

10.6.44. AWS DNS monitor resource

Module type	Type	Return value	Message	Description	Solution
awsdnsw	Error	5	AWS CLI command failed.	Failed in the AWS CLI command.	Check if the settings in the AWS CLI file are correct.
awsdnsw	Error	6	Timeout occurred.	Timeout occurred.	Check the load status of the server and remove the load.
awsdnsw	Error	7	Resource record set does not exist in Amazon Route 53.	Resource record set not exists in Amazon Route 53.	The resource record set to be monitored might be deleted. Check the registration of the resource record set of Amazon Route 53.
awsdnsw	Error	8	An IP address different from the setting value is registered in the resource record set of Amazon Route 53.	An IP address different from the setting value is registered in the resource record set of Amazon Route 53.	Make sure that the IP address registered int the resource record set to be monitored is correct.
awsdnsw	Error	9	Name resolution has failed.	Failed to check name resolution of the resource record set.	Name resolution has failed. Set a resolver, or make sure that there is no problem with the network. For a resource record set name using escape characters, name resolution will fail. Therefore, set the checkbox of Check Name Resolution to off.
awsdnsw	Error	10	The IP address of the result of name resolution is different from the setting value.	The IP address of the result of name resolution is different from the setting value.	Make sure that the settings of DNS resolver are correct and that there is no unintended entry in the hosts file.
awsdnsw	Warning	105	AWS CLI command failed.	Failed in the AWS CLI command.	Check if the settings in the AWS CLI file are correct.
awsdnsw	Warning	106	Timeout occurred.	Timeout occurred.	Check the load status of the server and remove the load.
awsdnsw	Warning	189	Internal error occurred.	Internal error occurred.	Check if Python is installed correctly. Check if AWS CLI is installed correctly. Memory or OS resources may not be sufficient. Check them.

10.6.45. Azure probe port monitor resource

Module type	Type	Return value	Message	Description	Solution
azureppw	Error	4	Probe port is closed.	Probe port is closed.	The probe port is closed. Check the network settings on the server.
azureppw	Error	5	Timeout of waiting probe port occurred.	Timeout of waiting probe port occurred.	The server could not receive the probe from the Azure load balancer in the probe wait timeout. Check if an error does not occur with a network adaptor. Check if the server is connected to the network correctly.
azureppw	Warning	105	Timeout of waiting probe port occurred.	Timeout of waiting probe port occurred.	The server could not receive the probe from the Azure load balancer in the probe wait timeout. Check if an error does not occur with a network adaptor. Check if the server is connected to the network correctly.
azureppw	Warning	189	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.6.46. Azure load balance monitor resource

Module type	Type	Return value	Message	Description	Solution
azurelbw	Error	4	Probe port is opened.	Probe port is opened.	The probe has been opend on the standby server. Make sure that the probe port is not opend on the standby server.
azurelbw	Warning	189	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.6.47. Azure DNS monitor resource

Module type	Type	Return value	Message	Description	Solution
azurednsw	Error	11	Query to DNS server has failed.	Query for name resolution was executed to DNS server of Microsoft Azure. However, it failed.	Make sure that EXPRESSCLUSTER server can communicate with DNS server of Microsoft Azure. From DNS zone of Microsoft Azure portal, check if DNS zone and the record set are registered.
azurednsw	Error	12	An IP address different from the setting value is registered in the record set of Azure DNS zone.	The record set of DNS server might be deleted or rewritten from external.	From DNS zone of Microsoft Azure portal, check the record set.
azurednsw	Warning	189	Internal error occurred.	An internal error occurred.	Memory or OS resources may not be sufficient. Check them.

10.6.48. Google Cloud virtual IP monitor resource

Module type	Type	Return value	Message	Description	Solution
gcvipw	Error	4	Port is closed.	Port is closed.	The port specified for Port Number is closed. Check the network settings of the server.
gcvipw	Error	5	Timeout of waiting port occurred.	Health check timeout occurred.	The health check could not be received from the load balancer within Health check timeout. Check if there is an error with the network adopter or the network is properly connected. Or, extend Health check timeout.
gcvipw	Error	6	Monitoring port failed.	Monitoring port failed.	Check if memory or OS resources are sufficient.
gcvipw	Error	7	Monitoring port is frozen.	Monitoring port is frozen.	Check if memory or OS resources are sufficient.
gcvipw	Error	99	Internal error.	Internal error occurred.	Check if memory or OS resources are sufficient.
gcvipw	Warning	105	Timeout of waiting port occurred.	Health check timeout occurred.	The health check could not be received from the load balancer within Health check timeout. Check if there is an error with the network adopter or the network is properly connected. Or, extend Health check timeout.
gcvipw	Warning	189	Internal error occurred.	Internal error occurred.	Check if memory or OS resources are sufficient.

10.6.49. Google Cloud load balance monitor resource

Module type	Type	Return value	Message	Description	Solution
gclbw	Error	4	Port is opened.	Port is opened.	The port specified for Port Number on the standby server is opened. Make sure that the port will not be opened on the standby server.
gclbw	Error	5	Monitoring port failed.	Monitoring port failed.	Check if memory or OS resources are sufficient.
gclbw	Error	99	Internal error.	Internal error occurred.	Check if memory or OS resources are sufficient.
gclbw	Warning	189	Internal error occurred.	Internal error occurred.	Check if memory or OS resources are sufficient.

10.6.50. Google Cloud DNS monitor resources

Module Type	Type	Return Value	Message	Description	Solution
gcdnsw	Error	5	Failed to start script.	Failed to start script.	Check if the script can be executed.
gcdnsw	Error	6	Script did not exist.	The asynchronous type script terminated abnormally.	Check the cause of the termination of the script.
gcdnsw	Error	8	Returned exit code %1.	The synchronous type script returned abnormal error code.	Check the cause for the abnormal error code.
gcdnsw	Error	9	Failed to log on as a user.	Logon as a user failed	Check if the domain, account and password of the execution user are correctly set.
gcdnsw	Warning	100	Timeout occurred.	The synchronous type script did not terminate within the timeout period.	Check the cause of the delay of the script.
gcdnsw	Warning	100	Returned exit code %1.	The synchronous type script returned abnormal error code.	Check the cause for the abnormal error code.
gcdnsw	Warning	100 190	Script path is invalid.	The configured value of the script path is not correct.	Check the configured value on the Cluster WebUI.
gcdnsw	Warning	100 190	Internal error occurred.	Internal error occurred.	Memory or OS resources may not be sufficient. Check them.
gcdnsw	Warning	190	Parameter is invalid.	The configured value of the monitoring is not correct.	Check the configured value on the Cluster WebUI.
gcdnsw	Warning	190	Resource does not exist in cluster configuration data.	The cluster configuration data is not correct.	Check the cluster configuration data on the Cluster WebUI.
gcdnsw	Warning	190	Failed to get the value from cluster configuration data.	The cluster configuration data is not correct.	Check the cluster configuration data on the Cluster WebUI.
gcdnsw	Warning	190	Script did not exist.	The asynchronous type script terminated abnormally.	Check the cause of the termination of the script.
gcdnsw	Error	200	Failed to start script.	Failed to start script.	Check if the script can be executed.

10.6.51. Oracle Cloud virtual IP monitor resource

Module type	Type	Return value	Message	Description	Solution
ocvipw	Error	4	Port is closed.	Port is closed.	The port specified for Port Number is closed. Check the network settings of the server.
ocvipw	Error	5	Timeout of waiting port occurred.	Health check timeout occurred.	The health check could not be received from the load balancer within Health check timeout. Check if there is an error with the network adopter or the network is properly connected. Or, extend Health check timeout.
ocvipw	Error	6	Monitoring port failed.	Monitoring port failed.	Check if memory or OS resources are sufficient.
ocvipw	Error	7	Monitoring port is frozen.	Monitoring port is frozen.	Check if memory or OS resources are sufficient.
ocvipw	Error	99	Internal error.	Internal error occurred.	Check if memory or OS resources are sufficient.
ocvipw	Warning	105	Timeout of waiting port occurred.	Health check timeout occurred.	The health check could not be received from the load balancer within Health check timeout. Check if there is an error with the network adopter or the network is properly connected. Or, extend Health check timeout.
ocvipw	Warning	189	Internal error occurred.	Internal error occurred.	Check if memory or OS resources are sufficient.

10.6.52. Oracle Cloud load balance monitor resource

Module type	Type	Return value	Message	Description	Solution
oclbw	Error	4	Port is opened.	Port is opened.	The port specified for Port Number on the standby server is opened. Make sure that the port will not be opened on the standby server.
oclbw	Error	5	Monitoring port failed.	Monitoring port failed.	Check if memory or OS resources are sufficient.
oclbw	Error	99	Internal error.	Internal error occurred.	Check if memory or OS resources are sufficient.
oclbw	Warning	189	Internal error occurred.	Internal error occurred.	Check if memory or OS resources are sufficient.

10.7. STOP codes list of disk RW monitor resources

The following information is the STOP codes list which are generated when selecting Generating of intentional Stop Error on Action when stalling is detected of disk RW monitor resource.

STOP code	Description
0xE0000000	The STOP error which was generated as the Final action at detection of an error of the monitor resource at activation or deactivation failure of the group resource.
0xE000FF**	The STOP error which was generated by keep alive timeout (the timeout of disk RW monitor). The lower 8 bits (the part of "**") shows the following checkpoint (The chances are high that it was being executed during timeout).
0xE000FF00	The internal processing of EXPRESSCLUSTER
0xE000FF01	free(), SetWaitableTimer(), GetTickCount(), WaitForMultipleObjects()
0xE000FF02	CreateFile(), _beginthreadex()
0xE000FF03	malloc(), WriteFile()
0xE000FF04	FlushFileBuffers()
0xE000FF05	CloseHandle()
0xE000FF06	The internal processing of EXPRESSCLUSTER

10.8. Filter driver STOP code list

The following lists the STOP codes generated by the EXPRESSCLUSTER filter driver (clpdiskfltr.sys).

STOP code	Description
0xE000FD00	A fatal internal error has occurred in the filter driver.
0xE000FD01	A timeout has occurred during monitoring of the CLUSTER partitions (monitoring by reading and writing for partitions).
0xE000FD02	It is not possible to access the data partition for mirror disk resources or hybrid disk resources.
0xE000FD03	It is not possible to access the cluster partition for mirror disk resources or hybrid disk resources.

10.9. JVM monitor resource log output messages

The following messages belong to the JVM operation and JVM load balancer linkage log files that are specific to the JVM monitor resources.

The file is created in the following location:

JVM operation log: <EXPRESSCLUSTER_install_path>\log\ha\jra\jragent*.log (* indicates a number starting at 0.)

JVM load balancer linkage log: <EXPRESSCLUSTER_install_path>\log\ha\jra\lbadmin.log

10.9.1. JVM operation log

Message	Cause of generation	Action
Failed to write the %1.stat.	Writing to the JVM statistics log has failed. %1 .stat: JVM statistics log file name	Check whether there is sufficient free disk space.
%1: analyze finish[%4]. state = %2, cause = %3	(When the status of the Java VM to be monitored is abnormal) the resource use amount has exceeded the threshold in the Java VM to be monitored. %1: Name of the Java VM to be monitored %2: Status of Java VM to be monitored (1=normal, 0=abnormal) %3: Error generation location at abnormality occurrence %4: Measurement thread name	Review the Java application that runs on the Java VM to be monitored.
thread stopped by UncaughtException.	The thread of the JVM monitor resource has stopped.	Execute cluster suspend/cluster resume and then restart the JVM monitor resource.
thread wait stopped by Exception.	The thread of the JVM monitor resource has stopped.	Execute cluster suspend/cluster resume and then restart the JVM monitor resource.
%1: monitor thread can't connect to JVM.	The Java VM to be monitored could not be connected. %1: Name of the Java VM to be monitored	Check that the Java VM to be monitored is running.
%1: monitor thread can't get the JVM state.	The resource use amount could not be acquired from Java VM to be monitored. %1: Name of the Java VM to be monitored	Check that the Java VM to be monitored is running.
%1: JVM state is changed [abnormal -> normal].	The status of the Java VM to be monitored has changed from abnormal to normal. %1: Name of the Java VM to be monitored	-
%1: JVM state is changed [normal -> abnormal].	The status of the Java VM to be monitored has changed from normal to abnormal. %1: Name of the Java VM to be monitored	Review the Java application that runs on the Java VM to be monitored.
%1: Failed to connect to JVM.	The Java VM to be monitored could not be connected.	Check that the Java VM to be monitored is running. %1: Name of the Java VM to be monitored
Failed to write exit code.	The JVM monitor resource failed to write data to the file for recording the exit code.	Check whether there is sufficient free disk space.
Failed to be started JVM Monitor.	Starting of the JVM monitor resource has failed.	Check the JVM operation log, remove the cause preventing the start, execute cluster suspend/cluster resume, and then restart the JVM monitor resource.
JVM Monitor already started.	The JVM monitor resource has already been started.	Execute cluster suspend/cluster resume and then restart the JVM monitor resource.
%1: GARBAGE_COLLECTOR_MXBEAN_DOMAIN_TYPE is invalid.	GC information could not be acquired from the Java VM to be monitored. %1: Name of the Java VM to be monitored	Check whether the operating environment of the Java VM to be monitored is correct.
%1: GarbageCollectorMXBean is invalid.	GC information could not be acquired from the Java VM to be monitored. %1: Name of the Java VM to be monitored	Check whether the operating environment of the Java VM to be monitored is correct.
%1: Failed to measure the GC stat.	GC information could not be acquired from the Java VM to be monitored. %1: Name of the Java VM to be monitored	Check whether the operating environment of the Java VM to be monitored is correct.
%1: GC stat is invalid. last.getCount = %2, last.getTime = %3, now.getCount = %4, now.getTime = %5.	The GC generation count and GC execution time could not be measured for the Java VM to be monitored. %1: Name of the Java VM to be monitored %2: GC generation count at last measurement %3: Total GC execution time at last measurement %4: GC generation count at this measurement %5: Total GC execution time at this measurement	Check whether the operating environment of the Java VM to be monitored is correct.
%1: GC average time is too long. av = %6, last.getCount = %2, last.getTime = %3, now.getCount = %4, now.getTime = %5.	The average GC execution time has exceeded the threshold in the Java VM to be monitored. %1: Name of the Java VM to be monitored %2: GC generation count at last measurement %3: Total GC execution time at last measurement %4: GC generation count at this measurement %5: Total GC execution time at this measurement %6: Average of the GC execution time used from the last measurement to this measurement	Review the Java application that runs on the Java VM to be monitored.
%1: GC average time is too long compared with the last connection. av = %6, last.getCount = %2, last.getTime = %3, now.getCount = %4, now.getTime = %5.	After the Java VM to be monitored was reconnected, the average of the GC execution time has exceeded the threshold in the Java VM to be monitored. %1: Name of the Java VM to be monitored %2: GC generation count at last measurement %3: Total GC execution time at last measurement %4: GC generation count at this measurement %5: Total GC execution time at this measurement %6: Average of the GC execution time used from the last measurement to this measurement	Review the Java application that runs on the Java VM to be monitored.
%1: GC count is too frequently. count = %4 last.getCount = %2, now.getCount = %3.	The GC generation count has exceeded the threshold in the Java VM to be monitored. %1: Name of the Java VM to be monitored %2: GC generation count at last measurement %3: GC generation count at this measurement %4: GC generation count from the last measurement to this measurement	Review the Java application that runs on the Java VM to be monitored.
%1: GC count is too frequently compared with the last connection. count = %4 last.getCount = %2, now.getCount = %3.	After the Java VM to be monitored was reconnected, the GC generation count has exceeded the threshold in the Java VM to be monitored. %1: Name of the Java VM to be monitored %2: GC generation count at last measurement %3: GC generation count at this measurement %4: GC generation count from the last measurement to this measurement	Review the Java application that runs on the Java VM to be monitored.
%1: RuntimeMXBean is invalid.	Information could not be acquired from the Java VM to be monitored. %1: Name of the Java VM to be monitored	Check whether the operating environment of the Java VM to be monitored is correct.
%1: Failed to measure the runtime stat.	Information could not be acquired from the Java VM to be monitored. %1: Name of the Java VM to be monitored	Check whether the operating environment of the Java VM to be monitored is correct. Check whether the processing load is high in the Java VM to be monitored.
%1: MEMORY_MXBEAN_NAME is invalid. %2, %3.	Memory information could not be acquired from the Java VM to be monitored. %1: Name of the Java VM to be monitored %2: Memory pool name %3: Memory name	Check whether the operating environment of the Java VM to be monitored is correct.
%1: MemoryMXBean is invalid.	Memory information could not be acquired from the Java VM to be monitored. %1: Name of the Java VM to be monitored	Check whether the operating environment of the Java VM to be monitored is correct.
%1: Failed to measure the memory stat.	Memory information could not be acquired from the Java VM to be monitored. %1: Name of the Java VM to be monitored	Check whether the operating environment of the Java VM to be monitored is correct. Check whether the processing load is high in the Java VM to be monitored.
%1: MemoryPool name is undefined. memory_name = %2.	Memory information could not be acquired from the Java VM to be monitored. %1: Name of the Java VM to be monitored %2: Name of the Java memory pool to be measured	Check whether the operating environment of the Java VM to be monitored is correct.
%1: MemoryPool capacity is too little. memory_name = %2, used = %3, max = %4, ratio = %5.	The Java memory pool free space has fallen below the threshold in the Java VM to be monitored. %1: Name of the Java VM to be monitored %2: Name of the Java memory pool to be measured %3: Use amount of the Java memory pool %4: Maximum usable amount of the Java memory pool %5: Use rate of the Java memory pool	Review the Java application that runs on the Java VM to be monitored.
%1: THREAD_MXBEAN_NAME is invalid.	Thread information could not be acquired from the Java VM to be monitored. %1: Name of the Java VM to be monitored	Check whether the operating environment of the Java VM to be monitored is correct.
%1: ThreadMXBean is invalid.	Thread information could not be acquired from the Java VM to be monitored.	Check whether the operating environment of the Java VM to be monitored is correct. %1: Name of the Java VM to be monitored
%1: Failed to measure the thread stat.	Thread information could not be acquired from Java VM to be monitored. %1: Name of the Java VM to be monitored	Check whether the operating environment of the Java VM to be monitored is correct.
%1: Detect Deadlock. threads = %2.	Thread deadlock has occurred in the Java VM to be monitored. %1: Name of the Java VM to be monitored %2: ID of the deadlock thread	Review the Java application that runs on the Java VM to be monitored.
%1: Thread count is too much(%2).	The number of activated threads has exceeded the threshold in the Java VM to be monitored. %1: Name of the Java VM to be monitored %2: Number of activated threads at measurement	Review the Java application that runs on the Java VM to be monitored.
%1: ThreadInfo is null.Thread count = %2.	Thread information could not be acquired in the Java VM to be monitored. %1: Name of the Java VM to be monitored %2: Number of activated threads at measurement	Check whether the operating environment of the version of the Java VM to be monitored is correct.
%1: Failed to disconnect.	Disconnection from the Java VM to be monitored has failed. %1: Name of the Java VM to be monitored	-
%1: Failed to connect to WebLogicServer.	WebLogic Server to be monitored could not be connected. %1: Name of the Java VM to be monitored	Review the Java application that runs on the WebLogic Server to be monitored.
%1: Failed to connect to Sun JVM.	Java VM and WebOTX to be monitored could not be connected. %1: Name of the Java VM to be monitored	Review the Java application that runs on the Java VM and WebOTX to be monitored.
Failed to open the %1.	The JVM statistics log could not be output. %1: Name of the HA/JVMSaverJVM statistics log file	Check whether the disk has sufficient free space or whether the number of open files has exceeded the upper limit.
%1: Can't find monitor file.	No monitoring %1: Name of the Java VM to be monitored	-
%1: Can't find monitor file, monitor stopped[thread:%2].	Monitoring stops. %1: Name of the Java VM to be monitored %2: Type of the measurement thread	-
%1: Failed to create monitor status file.	An internal file could not be created. %1: Name of the Java VM to be monitored	Check whether the disk free space and the maximum number of volume files are sufficient.
%1: Failed to delete monitor status file.	An internal file could not be deleted.	Check whether there is a problem with the hard disk.
%1: com.bea:Type=ServerRuntime is invalid.	Information could not be acquired from the Java VM to be monitored. %1: Name of the Java VM to be monitored	Check whether the operating environment of the Java VM to be monitored is correct.
%1: WorkManagerRuntimeMBean or ThreadPoolRuntimeMBean is invalid.	Information could not be acquired from the WebLogic Server to be monitored. %1: Name of the Java VM to be monitored	Check whether the operating environment of the WebLogic Server to be monitored is correct.
%1: Failed to measure the WorkManager or ThreadPool stat.	Information could not be acquired from the WebLogic Server to be monitored. %1: Name of the Java VM to be monitored	Check whether the operating environment of the WebLogic Server to be monitored is correct.
%1: ThreadPool stat is invalid. last.pending = %2, now.pending = %3.	The number of waiting requests could not be measured in the thread pool of the WebLogic Server to be monitored. %1: Name of the Java VM to be monitored %2: Number of waiting requests at last measurement %3: Number of waiting requests at this measurement	Check whether the operating environment of the version of the WebLogic Server to be monitored is correct.
%1: WorkManager stat is invalid. last.pending = %2, now.pending = %3.	The number of waiting requests could not be measured in the work manager of the WebLogic Server to be monitored. %1: Name of the Java VM to be monitored %2: Number of waiting requests at last measurement %3: Number of waiting requests at this measurement	Check whether the operating environment of the version of the WebLogic Server to be monitored is correct.
%1: PendingRequest count is too much. count = %2.	The number of waiting requests has exceeded the threshold in the thread pool of the WebLogic Server to be monitored. %1: Name of the Java VM to be monitored %2: Number of waiting requests at this measurement	Review the Java application that runs on the WebLogic Server to be monitored.
%1: PendingRequest increment is too much. increment = %4, last.pending = %2, now.pending = %3.	The increment of the number of waiting requests has exceeded the threshold in the thread pool of the WebLogic Server to be monitored. %1: Name of the Java VM to be monitored %2: Number of waiting requests at last measurement %3: Number of waiting requests at this measurement %4: Increment of the number of waiting requests from the last measurement to this measurement	Review the Java application that runs on the WebLogic Server to be monitored.
%1: PendingRequest increment is too much compared with the last connection. increment = %4, last.pending = %2, now.pending = %3.	After the WebLogic Server to be monitored was reconnected, the increment of the number of waiting requests has exceeded the threshold in the thread pool of the WebLogic Server to be monitored. %1: Name of the Java VM to be monitored %2: Number of waiting requests at last measurement %3: Number of waiting requests at this measurement %4: Increment of the number of waiting requests from the last measurement to this measurement	Review the Java application that runs on the WebLogic Server to be monitored.
%1: Throughput count is too much. count = %2.	The number of requests executed per unit time has exceeded the threshold in the thread pool of the WebLogic Server to be monitored. %1: Name of the Java VM to be monitored %2: Number of requests executed per unit time at this measurement	Review the Java application that runs on the WebLogic Server to be monitored.
%1: Throughput increment is too much. increment = %4, last.throughput = %2, now.throughput = %3.	The increment of the number of requests executed per unit time has exceeded the threshold in the thread pool of the WebLogic Server to be monitored. %1: Name of the Java VM to be monitored %2: Number of requests executed per unit time at last measurement %3: Number of requests executed per unit time at this measurement %4: Increment of the number of requests executed per unit time from the last measurement to this measurement	Review the Java application that runs on the WebLogic Server to be monitored.
%1: Throughput increment is too much compared with the last connection. increment = %4:, last.throughput = %2, now.throughput = %3.	After the WebLogic Server to be monitored was reconnected, the increment of the number of requests executed per unit time has exceeded the threshold in the thread pool of the WebLogic Server to be monitored. %1: Name of the Java VM to be monitored %2: Number of requests executed per unit time at last measurement %3: Number of requests executed per unit time at this measurement %4: Increment of the number of requests executed per unit time from the last measurement to this measurement	Review the Java application that runs on the WebLogic Server to be monitored.
%1: PendingRequest count is too much. appName = %2, name = %3, count = %4.	The number of waiting requests has exceeded the threshold in the work manager of the WebLogic Server to be monitored. %1: Name of the Java VM to be monitored %2: Application name %3: Work manager name %4: Number of waiting requests	Review the Java application that runs on the WebLogic Server to be monitored.
%1: PendingRequest increment is too much. appName = %2, name = %3, increment = %6, last.pending = %4, now.pending = %5.	The increment of the number of waiting requests has exceeded the threshold in the work manager of the WebLogic Server to be monitored. %1: Name of the Java VM to be monitored %2: Application name %3: Work manager name %4: Number of waiting requests at last measurement %5: Number of waiting requests at this measurement %6: Increment of the number of waiting requests from the last measurement to this measurement	Review the Java application that runs on the WebLogic Server to be monitored.
%1: PendingRequest increment is too much compared with the last connection. AppName = %2, Name = %3, increment = %6, last.pending = %4, now.pending = %5.	After the WebLogic Server to be monitored was reconnected, the increment of the number of waiting requests has exceeded the threshold in the work manager of the WebLogic Server to be monitored. %1: Name of the Java VM to be monitored %2: Application name %3: Work manager name %4: Number of waiting requests at last measurement %5: Number of waiting requests at this measurement %6: Increment of the number of waiting requests from the last measurement to this measurement	Review the Java application that runs on the WebLogic Server to be monitored.
%1: Can't find WorkManager. appName = %2, name = %3.	The work manager which was set could not be acquired from the WebLogic Server. %1: Name of the Java VM to be monitored %2: Application name %3: Work manager name	Review the setting of Target WebLogic Work Managers.
%1: analyze of average start[%2].	Analyzing of the average value has started. %1: Name of the Java VM to be monitored %2: Thread name	-
%1: analyze of average finish[%2].state = %3.	Analyzing of the average value has been completed. %1: Name of the Java VM to be monitored %2: Thread name %3: Status of the target to be monitored	-
%1: Average of PendingRequest count is too much. count = %2.	The average of the number of waiting requests has exceeded the threshold in the thread pool of the WebLogic Server to be monitored. %1: Name of the Java VM to be monitored %2: Number of waiting requests at this measurement	Review the Java application that runs on the WebLogic Server to be monitored.
%1: Average of Throughput count is too high. count = %2.	The average of the number of requests executed per unit time has exceeded the threshold in the thread pool of the WebLogic Server to be monitored. %1: Name of the Java VM to be monitored %2: Number of requests executed per unit time at this measurement	Review the Java application that runs on the WebLogic Server to be monitored.
%1: Average of PendingRequest count is too high. AppName = %2, Name = %3, count = %4.	The average of the number of waiting requests has exceeded the threshold in the work manager of the WebLogic Server to be monitored. %1: Name of the Java VM to be monitored %2: Application name %3: Work manager name %4: Number of waiting requests at this measurement	Review the Java application that runs on the WebLogic Server to be monitored.
Error: Failed to operate clpjra_bigip.[%1]	%1: Error code	Review the setting.

10.9.2. JVM load balancer linkage log

Message	Cause of generation	Action
lbadmin command start.	Execution of the load balancer linkage command has started.	-
lbadmin command finish.	Execution of the load balancer linkage command has been completed.	-
Into HealthCheck mode.	The health check function is enabled.	-
Into Weight mode.	The load calculation function of the Java VM to be monitored is valid.	-
The PID of lbadmin.jar is "%1".	ID of the process relating to the load balancer linkage %1: Process ID of lbadmin.jar	-
Thread wait stopped by Exception	Waiting for down judgment has been stopped.	-
Rename Command succeeded.	Renaming of the HTML file has been successful.	-
Rename Command failed.	Renaming of the HTML file has failed.	Check the HTML file name and HTML rename destination file name.
%1 doesn't exist.	The rename source HTML file does not exist. %1: HTML file name	Check the HTML file name.
%1 already exists.	The rename destination HTML file already exists. %1: HTML rename destination file name	Check the HTML rename destination file name.
Can't rename file:%1.	Renaming of the HTML file has failed. %1: HTML file name	Check the HTML rename destination file name.
The number of retries exceeded the limit.	The retry count for renaming the HTML file has exceeded the upper limit.	Check the HTML rename destination file name.
The percent of the load is "%1".	Load calculation for the Java VM to be monitored has been successful. %1: Load of Java VM to be monitored	-
stat log (%1) doesn't exist.	There is no JVM statistics log file. %1: JVM statistics log file name	Execute cluster suspend/cluster resume and then restart the JVM monitor resource.
stat log(%1:) cannot be opened for reading.	The JVM statistics log file could not be opened. %1: JVM statistics log file name	Execute cluster suspend/cluster resume and then restart the JVM monitor resource.
format of stat log (%1) is wrong.	The contents of the JVM statistics log file are invalid. %1: Statistics log file name	After deleting the JVM statistics log file, execute cluster suspend/cluster resume and then restart the JVM monitor resource.
Failed to get load of application server.	Data for load calculation could not be acquired from the JVM statistics log file.	Review whether the load calculation setting of the Java VM to be monitored is correct.
Can't find lock file(%1s*.stat.lck), maybe HA/JVMSaver did not start yet.	JVM monitoring has not yet started. %1: Internal file name	Start the JVM monitor resource.

10.10. STOP codes list of user space monitor resources

The following information is a list of the STOP codes which are generated upon the selection of Generate an intentional stop error for Action When Timeout Occurs of the user space monitor resource.

STOP code	Description
0xE0000000	The STOP error which was generated as the final action upon the detection of an error of the monitor resource
0xE000FF**	The STOP error which was generated by keep alive timeout (the timeout of user space monitor) The lower 8 bits (the part of "**") shows the following checkpoint (The chances are high that it was being executed during timeout).
0xE000FF00	The internal processing of EXPRESSCLUSTER
0xE000FF01	SetWaitableTimer(), GetTickCount(), WaitForMultipleObjects()
0xE000FF02	_beginthreadex(),WaitForMultipleObjects()
0xE000FF05	CloseHandle()
0xE000FF06	The internal processing of EXPRESSCLUSTER