Detail codes when error code is FF
10022 Referred Windows Sockets is not supported.
- Measures:
-
Check the Management Host Setting screen to see whether the Observe port number is correctly registered. Check whether the version of the Windows Sockets is Version 1.1.
10024 There is no file descriptor which can be used.
- Measures:
-
Reduce the number of hosts connected. Close the files used by other applications.
10036 A communication with another processing is ongoing.
- Measures:
-
Wait until the communication with the other screen is complete.
10038 Connection is canceled.
- Measures:
-
Reconnect.
10047 Specified address family cannot be used.
- Measures:
-
Check whether the network environment is correct (can use IPv6).
10048 The specified IP address is already used.
- Measures:
-
Check whether the specified IP address is duplicate.
10049 Incorrect IP address.
- Measures:
-
Contact the network administrator, and use the correct IP address.
10050 An error occurred on the network subsystem.
- Measures:
-
Check whether the network sub-system is running normally.
10051 Cannot connect to the network from this host.
- Measures:
-
Check whether the TCP/IP is set correctly (such as IP Address, Subnet Mask and Default Gateway).
10052 Timeout occurred when connecting with the host.
- Measures:
-
Check whether the condition of the line is normal.
10053 Connection is canceled.
- Measures:
-
The line was disconnected due to a timeout or error. Check whether the condition of the line is normal.
10054 Failed to connect with the Observe program.
- Measures:
-
The destination host has reset the connection. Check whether the HULFT Observe process is running at the destination host. Check whether IP Address and Observe Port No. you have specified on the Management Host Setting screen are correct.
10055 Memory is insufficient.
- Measures:
-
Buffer for socket communication cannot be allocated. Reduce the number of hosts connected. Terminate other applications.
10056 Connection has been already established.
- Measures:
-
You have started the connection process when the line is already connected to the host. Continue with your process.
10057 Connection is canceled.
- Measures:
-
Reconnect.
10058 Connection is canceled.
- Measures:
-
Reconnect.
10060 Timeout occurred when connecting with the Observe program.
- Description:
-
Tried to connect to the host, but the connection process failed due to the timeout.
- Measure 1:
-
Check whether the destination host is booted.
- Measure 2:
-
Check the TCP/IP settings.
- Measure 3:
-
Check whether the line is connected.
- Measure 4:
-
Check whether the IP address you have specified is correct.
- Measure 5:
-
If the processing speed of the connected host is slow, set a larger value for Socket Read Timeout and increase Connect Retry Count.
- Measure 6:
-
If the connected host is on Mainframe, check whether TISP and other items are set to recognize the PC on which HULFT Manager is installed.
10061 The Observe program of the destination host is not started.
- Measures:
-
The destination host has rejected the connection request. Check whether the Observe program of the HULFT on the destination host is running. Check whether IP Address and Observe Port No. you have specified on the Management Host Setting screen is correct.
10065 Host cannot be reached.
- Measures:
-
Check whether IP Address and Subnet Mask are correctly set in the TCP/IP settings.
10091 The network subsystem is not started.
- Measure 1:
-
The network subsystem is not ready. Check whether the TCP/IP protocol has been started.
- Measure 2:
-
Check that the router is not down.
10092 Referred Windows Sockets is not supported.
- Measures:
-
The Windows sockets referred to is not supported. Check whether the version of Windows Sockets is Version 1.1.
10093 Communication start processing is not performed.
- Measures:
-
Reconnect.
11001 The host name is not found.
- Measures:
-
The local host name has not been found. Check whether the local host name is registered in the HOSTS file. Check whether the TCP/IP settings are correct.
11002 The host name is not found.
- Measures:
-
The local host name has not been found. Check whether the local host name is registered in the HOSTS file. Check whether the TCP/IP settings are correct.
11004 Failed to obtain local host name.
- Measures:
-
The local host name has not been found. Check whether the local host name is registered in the HOSTS file. Check whether the TCP/IP settings are correct.
20000 Referred Windows Sockets is not supported.
- Measures:
-
The Windows sockets referred to is not supported. Check whether the version of Windows Sockets is Version 1.1.
20001 The host name is not found.
- Measures:
-
The local host name has not been found. Check whether the local host name is registered in the HOSTS file. Check whether the TCP/IP settings are correct.
20003 Data has not been received normally.
- Measures:
-
Check whether the condition of the line is normal.
20004 Data has not been transmitted normally.
- Measures:
-
Check whether the condition of the line is normal.
20005 Data has not been transmitted and received normally.
- Measures:
-
Check whether the condition of the line is normal.
20007 Data has not been transmitted normally.
- Measures:
-
Check whether the condition of the line is normal.
20008 Data has not been received normally.
- Measures:
-
Check whether the connection is normal. Also check whether the connected host is operating normally.
20009 An application error.
- Measures:
-
Restart it.
20010 Communication start processing is not performed.
- Measures:
-
Reconnect.
20011 No response from the destination host. The timeout occurred during reception of data.
- Measures:
-
Check whether the destination host is operating normally. Set a larger value for Socket Read Timeout on HULFT Manager.
20012 Failed to get the destination address.
- Measures:
-
Check the environment on which the name resolution is made.
30005 The system became unstable.
- Measures:
-
Restart HULFT Manager.
30099 The system became unstable.
- Measures:
-
Restart HULFT Manager.
40000 Canceled by the destination host.
- Measures:
-
Check whether the destination host is operating normally. Check the Observe Log of the destination host.
40020 The HULADMIN service is not installed on the destination host.
- Measures:
-
HULFT ManagerConnection Option is not installed on the destination host. Install HULFT ManagerConnection Option on the destination host.
40101 The memory of the destination host is insufficient.
- Measures:
-
Memory capacity of the destination host is insufficient. Check the environment for HULFT on the destination host.
40332 The host name is not registered in the HOSTS file on the destination host.
- Measures:
-
Register the local host name in the HOSTS file on the destination host.
40333 The connection timeout (read timeout) occurred on the Observe process of the destination host.
- Measures:
-
Set a larger timeout value for the Observe process on the destination host.
40440 The local host name is not registered in the Host Information on the destination host.
- Measures:
-
Register the local host name to the Host Information on the destination host.
40450 The Observe program of the destination host is not started.
- Measures:
-
The connection request from the destination host has been refused. Check that the Observe process of HULFT is running on the destination host.
40452 The Observe program of the destination host is not started.
- Measures:
-
The connection request from the destination host has been refused. Check that the Observe process of HULFT is running on the destination host.
40474 The limit of the multiplex level has reached.
- Measures:
-
Check the load status and try to reconnect at a timing when the multiplex level is low.
40482 The HULADMIN service is not installed on the destination host.
- Measures:
-
HULFT ManagerConnection Option is not installed on the destination host. Install HULFT ManagerConnection Option on the destination host.
40736 The host name is not registered in the host file on the destination host.
- Measures:
-
Register the local host name in the HOSTS file on the destination host.
40881 The HULADMIN service is not installed on the destination host.
- Measures:
-
The Manager Connection module is not installed on the destination host. Install HULFT ManagerConnection Option on the destination host.