4.2.12 OS Restart Failure Check

An "OS restart failure check" task is generated when the operating system has failed to restart.

The operating system is restarted when a restart is required after the patch has been applied and when Yes has been specified for Restart operating system after execution in the application settings. If No is specified for Restart operating system after execution in the application settings, the operating system will not be restarted even if the operating system needs to be restarted after the patch is applied. Also, if there is no need to restart the operating system after the patch is applied, the operating system will not be restarted, regardless of the settings for Restart operating system after execution.

$D:\SWCFMG_DEV\15.1\src_Manual\eng\help\image\help0419.gif$

If an "OS restart failure check" task is generated, a log will be output to the Details field in the OS restart failure check tab, indicating the type of error that has occurred.

Refer to the "returnCode" information. The following table shows the expected values and their meaning:

Keyword	returnCode	Meaning
All	189	If one of the following values has been output for "message", this means that the connection for network communications with the business server has failed. [LinkExpRBA] CategoryCode: 50 [LinkExpRBA] ErrorCode: 80 [Actions] Check the following items: The file transfer infrastructure may not have been set up on the business server. Check whether the file transfer infrastructure has been set up. The business server may have stopped. Check the operational status of the business server. The file transfer infrastructure may not be running on the business server. Start the file transfer infrastructure. [Windows] Restart the "Systemwalker File Transfer Library Control" service. [Linux] Execute the following command: # service FJSVlnkbs start There may be an error with the IP address of the business server that is specified in the "hosts" file. Check the IP address specified in the "hosts" file. If the remote server is a PC server with a TCP/IP connection, the number of connection requests on the business server may have exceeded the maximum number of requests that can be simultaneously processed by WinSock. The connection may have been blocked by a firewall on the communication path. If the business server is running Windows, the connection may have been blocked by security settings such as the Windows firewall. If the situation still does not change even after you have taken the appropriate action and then retried the processing, collect investigation data using the problem investigation data collection command (swcfmg_collectinfo), and then contact Fujitsu technical support.
If one of the following values has been output for "message", this means that a timeout has occurred during communications with the business server: [LinkExpRBA] CategoryCode: 50 [LinkExpRBA] ErrorCode: 60 [Actions] The following are the possible causes of the problem: The business server may be stopped. The business server may have slowed down. The network may be under high load. Check these possible causes and then try again. If the situation still does not change despite the retry attempt, collect investigation data using the problem investigation data collection command (swcfmg_collectinfo), and then contact Fujitsu technical support.
Other	Collect investigation data using the problem investigation data collection command (swcfmg_collectinfo), and then contact Fujitsu technical support.

Keyword

returnCode

Meaning

All

189

If one of the following values has been output for "message", this means that the connection for network communications with the business server has failed.

[LinkExpRBA] CategoryCode: 50

[LinkExpRBA] ErrorCode: 80

[Actions]

Check the following items:

The file transfer infrastructure may not have been set up on the business server. Check whether the file transfer infrastructure has been set up.
The business server may have stopped. Check the operational status of the business server.
The file transfer infrastructure may not be running on the business server. Start the file transfer infrastructure.
[Windows]
Restart the "Systemwalker File Transfer Library Control" service.
[Linux]
Execute the following command:
# service FJSVlnkbs start
There may be an error with the IP address of the business server that is specified in the "hosts" file. Check the IP address specified in the "hosts" file.
If the remote server is a PC server with a TCP/IP connection, the number of connection requests on the business server may have exceeded the maximum number of requests that can be simultaneously processed by WinSock.
The connection may have been blocked by a firewall on the communication path.
If the business server is running Windows, the connection may have been blocked by security settings such as the Windows firewall.
If the situation still does not change even after you have taken the appropriate action and then retried the processing, collect investigation data using the problem investigation data collection command (swcfmg_collectinfo), and then contact Fujitsu technical support.

If one of the following values has been output for "message", this means that a timeout has occurred during communications with the business server:

[LinkExpRBA] CategoryCode: 50

[LinkExpRBA] ErrorCode: 60

[Actions]

The following are the possible causes of the problem:

The business server may be stopped.
The business server may have slowed down.
The network may be under high load.

Check these possible causes and then try again.

If the situation still does not change despite the retry attempt, collect investigation data using the problem investigation data collection command (swcfmg_collectinfo), and then contact Fujitsu technical support.

Other

Collect investigation data using the problem investigation data collection command (swcfmg_collectinfo), and then contact Fujitsu technical support.

Make Choice panel

$D:\SWCFMG_DEV\15.1\src_Manual\eng\help\image\help0416.gif$

Click Retry to restart the operating system again.

Click Continue to ignore the error and continue processing.

Click Cancel to end the process.