Remote Heartbeat Monitor command (utlalivecheck.exe)
1
- Description:
-
A parameter error occurred.
- Measure:
-
Check whether the entered parameter is correct.
2 Failed to secure memory.
- Description:
-
A memory error occurred.
- Measure 1:
-
Check that sufficient memory has been allocated in the environment in use.
- Measure 2:
-
Terminate any unnecessary applications.
9 Execution environment error.
- Description:
-
An environment check error occurred.
- Measure:
-
Check that the environment is supported.
10 Failed to acquire HULFT Operation Language.
- Description:
-
Failed to acquire HULFT Operation Language.
- Measure:
-
Check the setting of HULFT Operation Language in the System Environment Settings.
20 An error in reading the System Environment Settings file.
- Description:
-
Reading the System Environment Settings file (hulenv.cnf) failed.
- Measure 1:
-
Check that the System Environment Settings file (hulenv.cnf) exists.
- Measure 2:
-
Check the access permissions for the System Environment Settings file (hulenv.cnf).
26 Failed to initialize the socket communication.
- Description:
-
Failed to initialize the socket communication.
- Measure 1:
-
Check that blocking processing is not in progress.
- Measure 2:
-
Check that the number of available sockets is not exceeded.
27 Failed to secure memory when creating message.
- Description:
-
Failed to create sending message.
- Measure:
-
Check that sufficient memory has been allocated in the environment in use.
28 Socket connect error.
- Description:
-
Connection to the target machine failed.
- Measure 1:
-
Check whether the process on the remote host has been started.
- Measure 2:
-
Check whether the port number of the remote host is correct.
29 Message sending error.
- Description:
-
Failed to send data.
- Measure:
-
The socket may be disconnected. Check the socket.
50 Message receiving error.
- Description:
-
Failed to receive response message.
- Measure:
-
The socket may be disconnected. Check the socket.
51 The value in response message is invalid.
- Description:
-
The invalid value has been set in the response message.
- Measure:
-
Check the status of the process on the remote host.
52 Failed to secure memory for storing received message.
- Description:
-
Insufficient Memory.
- Measure 1:
-
Check that sufficient memory has been allocated in the environment in use.
- Measure 2:
-
Terminate any unnecessary applications.
53 Message receiving error.
- Description:
-
Failed to receive response message.
- Measure:
-
The socket may be disconnected. Check the socket.
54 An error occurred in the process on the remote host.
- Description:
-
Sending and receiving of message has ended successfully, but error may have occurred within the process on the remote host.
- Measure:
-
Check the status of the process on the remote host.
55 Failed to secure memory for storing received message.
- Description:
-
Failed to allocate buffer for receiving response message.
- Measure 1:
-
Check that sufficient memory has been allocated in the environment in use.
- Measure 2:
-
Terminate any unnecessary applications.
56 Failed to secure memory for storing received message.
- Description:
-
Failed to allocate buffer for receiving response message.
- Measure 1:
-
Check that sufficient memory has been allocated in the environment in use.
- Measure 2:
-
Terminate any unnecessary applications.
57 Receiving of message timed out.
- Description:
-
Time-out occurred in the socket read processing.
- Measure 1:
-
Increase the setting of Socket Read Timeout (socktime).
- Measure 2:
-
There may be problems in the socket, operating system failure, or the processing speed and the like. Check the environment.
58 Receiving message timed out.
- Description:
-
Time-out occurred in the socket read processing.
- Measure 1:
-
Increase the setting of Socket Read Timeout (socktime).
- Measure 2:
-
There may be problems in the socket, operating system failure, or the processing speed and the like. Check the environment.
156 Failed to open the Command Message file of the command that you ran.
- Description:
-
Failed to open the Command Message file of the command that you ran.
- Measure 1:
-
Check that the file exists.
- Measure 2:
-
Check the access permissions for the file.