If you detect abnormality when the instructions of the operation to each server using the file transfer infrastructure are executed, the operation components are ended with return value 187 or 189. When this happens, the detailed code for the file transfer infrastructure is output to the execution results of the operation component using the following format.
[LinkExpRBA] CategoryCode : Error category [LinkExpRBA] ErrorCode : Error code [LinkExpRBA] DetailCode : Error details
Remove the cause of the error based on the error category and error code.
Details of the error categories and error codes are covered below.
Error Classification: 40, Error Code: 10
[Description]
In communication processing with the Business Server using the file transfer infrastructure, because the following abnormalities had been detected, the processing of the operation components was discontinued.
The specification of OS type is different from OS of the Business Server.
[Measures]
Confirm the specification of OS type. If the specification of OS type is correct, there is a possibility that abnormality is occurring in the file transfer infrastructure of the Business Server. Confirm the system log or event log in the Business Server whether abnormality is not occurring in the file transfer infrastructure of the Business Server.
Error Classification: 40, Error Code: 30
[Description]
In communication processing with the Business Server using the file transfer infrastructure, because the following abnormalities had been detected, the processing of the operation components was discontinued.
The line fault occurred. The following causes are thought.
Abnormality occurred in the circuit to the Business Server.
Abnormality occurred in the file transfer infrastructure of the Business Server.
There is mistake in IP address information of own server set to the hosts file.
[Measures]
Confirm the following information:
Confirm whether abnormality is not occurring in the circuit to the Business Server.
Confirm the system log or event log in the Business Server whether abnormality is not occurring in the file transfer infrastructure of the Business Server.
Confirm a set value of the hosts file.
Error Classification: 40, Error Code: 40
Error Classification: 40, Error Code: 50
Error Classification: 40, Error Code: 60
[Description]
In communication processing with the Business Server using the file transfer infrastructure, because the following abnormalities had been detected, the processing of the operation components was discontinued.
In the file transfer infrastructure of the Business Server, the system error that it is impossible to continue processing occurred.
[Measures]
Confirm the system log or event log in the Business Server whether abnormality is not occurring in the file transfer infrastructure of the Business Server.
Error Classification: 50, Error Code: 10
[Description]
In communication processing with the Business Server using the file transfer infrastructure, because the following abnormalities had been detected, the processing of the operation components was discontinued.
File transfer infrastructure is not started in the Management Server.
[Measures]
Start the file transfer infrastructure in the Management Server.
[Windows]
Restart "Systemwalker File Transfer Library Control" service.
[Linux]
# service FJSVlnkbs start
[Solaris]
# /etc/init.d/FJSVlnkbs start
Error Classification: 50, Error Code: 60
[Description]
In communication processing with the Business Server using the file transfer infrastructure, because the following abnormalities had been detected, the processing of the operation components was discontinued.
The time-out was occurred in the communication with the Business Server.
The following causes are thought.
Slowdown of Business Server
Overload of communication environment
Processing delay of the file transfer infrastructure or Agent.
[Description]
Confirm the following:
Confirm whether the Business Server is not slowing down.
Confirm the status of the load of the communication environment.
Confirm the system log or event log in the Business Server.
Error Classification: 50, Error Code: 80
[Description]
In communication processing with the Business Server using the file transfer infrastructure, because the following abnormalities had been detected, the processing of the operation components was discontinued.
It failed in the network communication connection with the Business Server.
[Description]
Confirm the following:
There is a possibility that the file transfer infrastructure is not setting up in the Business Server. Confirm whether the file transfer infrastructure is setting up.
There is a possibility that the Business Server is stopping. Confirm the startup status of the Business Server.
There is a possibility that the file transfer infrastructure is not starting in the Business Server. Start the file transfer infrastructure.
[Windows]
Restart "Systemwalker File Transfer Library Control" service.
[Linux]
# service FJSVlnkbs start
[Solaris]
# /etc/init.d/FJSVlnkbs start
There is a possibility that IP address of the corresponding Business Server name specified for the hosts file is incorrect. Confirm IP address specified for the hosts file.
If the port number of the file transfer infrastructure has been changed, there is a possibility that information of the port number is incorrect. Confirm whether the port number set to the network definition of the Business Server and the port number set to the network definition of the file transfer infrastructure is corresponding. Refer to How to Change Port Numbers in the Systemwalker Runbook Automation Installation Guide for the setting of the port number.
When it is a connection of TCP/IP and the server of connection destination is PC server, there is a possibility that the connection demand to exceed the number that WinSock is treatable at the same time is occurred in the Business Server.
There is a possibility that the connection is refused by the firewall on the communication route.
When the Business Server is Windows system, there is a possibility that the connection is being refused by the security setting of the Windows firewall etc.
Error Classification: 50, Error Code: 90
[Description]
In communication processing with the Business Server using the file transfer infrastructure, because the following abnormalities had been detected, the processing of the operation components was discontinued.
It failed in the name resolution of the Business Server name.
[Measures]
Confirm whether the host name specified for a Business Server is correctly described in the hosts file or DNS.
Error Classification: 50, Error Code: 100
[Description]
One of the following errors has been detected with the communication processing with a Business Server using the file transfer infrastructure, and so, the processing for the operation component has been terminated.
A temporary shortage of resources occurred.
The number of operation component instances awaiting execution due to the number of instances exceeding the multiplicity limit has exceeded the maximum number allowed.
[Measures]
Check that there are no other operation processes running, and then restart the file transfer infrastructure on the Management Server.
[Windows]
Restart the "Systemwalker File Transfer Library Control" service.
[Linux]
# service FJSVlnkbs stop # service FJSVlnkbs start
[Solaris]
# /etc/init.d/FJSVlnkbs stop # /etc/init.d/FJSVlnkbs start
