AWS - R3Batch messages (twsinst)
This section lists error and warning messages that might be issued when using the R3Batch method.
The message component code is AWS.
AWKAWS001E Error during saving. Required field:
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS002E Error during saving. Please complete all fields
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS003E Test connection failed. Please check your credentials and your network connection.
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS005E No Instances.
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS006E Error. Please fill in at least one of these two sections: \"Manage Existing Virtual Server\" or \"Create New Virtual Server\".
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS007E Error. Please fill in one of these two sections: \"Manage Existing Virtual Server\" or \"Create New Virtual Server\".
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS008E Get Instances failed.
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS009E Get Instance Details failed.
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS010E Error. Please select an Instance.
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS011E No images.
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS012E Get Image Details failed.
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS013E Error. Please select an Image.
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS014E No types.
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS015E Unable to get region.
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS017E Operation failed
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS018E Operation unauthorized
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS019E No networks.
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS020E No subnets.
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS021E No security groups.
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS022E Start is not allowed. Instance must be in stopped status.
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS023E Stop is not allowed. Instance must be in pending, running, shutting down or stopping status.
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS024E Reboot is not allowed. Instance must be in running status.
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS025E Remove is not allowed. Instance must be in pending, running, shutting down, stopped or stopping status.
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWKAWS026E Error during saving. Please insert the AMI and the Instance Type
Explanation
See message text.
System action
The operation is not performed.
Operator response
Verify the error message and retry the operation.
AWSEDW001E The following value: "value" for the following netman command line option: "option" is not in the correct format.
Explanation
See message: option is the command line option (-timeout, -port, -mortal). value is the value for either the -timeout or the -port options.
System action
Netman stops.
Operator response
Use the command netman -U to display the correct usage for netman, or look in the Reference Manual. Make sure that netman is invoked correctly in the file named StartUp located in the HCL Workload Automation directory. When you have corrected the problem, run StartUp to start netman.
AWSEDW002E System error
AWSEDW003W Not running with root permissions
AWSEDW004E Message file already opened by another process: !1, !2
AWSEDW005E Netman was unable to open its configuration file: "file_name". The following error was given by the operating system: "system_error"
Explanation
See message text.
file_name is the fully qualified name of the netman configuration file.
system_error is the operating system error message.
System action
Netman stops.
Operator response
Use the operating system error message to determine what the problem is. Make sure that the netman configuration file exists and that netman has read permission for the file. Correct any errors you find and run StartUp to start netman.
AWSEDW006E Netman could not process the service information in its configuration file: "file_name". If the problem is with a specific entry, the details are as follows (if the following fields are blank the problem is a general one): "service_entry":"service_number".
Explanation
See message text.
file_name is the fully qualified configuration file name.
service_entry is the number of the service entry being processed, if any.
service_number is the service request number (for example, 2001, or 2002), if any.
Operator response
Ensure that the identified Netman configuration file exists, and is in the correct directory (see the Administration Guide for details of the file and the services it defines).
Edit the configuration file and make sure that all the entries are valid service entries. When you have corrected the problem, run StartUp to start netman.
AWSEDW007E Unable to open both message file and net connection
AWSEDW008E Error opening stdlist
AWSEDW009E Error duping stdlist
AWSEDW010I Stdlist duped to fd other than 1
AWSEDW011E Unable to create stdlist
AWSEDW012E An internal error has occurred. Netman has stopped because the following non-valid unlink request has been received: "service_request ". The error message and number are as follows: "error_number": "error_message"
Explanation
This request may be an obsolete request type.
service_request is the service request packet received by Netman.
error_number and error_message provide more information about the error. Depending on the type of error, thay might contain null values, or other information.
System action
Netman continues, but the operation is not performed.
Operator response
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW013E An internal error has occurred. Netman received the following unlink request "service_request" from the following message file: "message_file". Unlink requests received from a message file are not allowed.
Explanation
This may be an obsolete service request and therefore an obsolete error message.
service_request is the service request packet received by Netman.
message_file is the name of the file from which the request was received.
System action
Netman continues, but the operation is not performed.
Operator response
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW014E Invalid request !3 on !1: !2
AWSEDW015E Netman received the following unknown service request: "service_request"
Explanation
service_request is the service request packet received by Netman
System action
Netman continues, but the operation is not performed.
Operator response
Make sure that the Netman configuration file is not corrupted and that it contains entries for all the valid services. When you have corrected the problem, run StartUp to start netman.
If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW016I Starting: !1 pin !2
AWSEDW017E Netman received a service request for the following service that has a service type of disabled : "service_request"
Explanation
service_request is the service request packet received by Netman.
System action
Netman continues, but the operation is not performed.
Operator response
Make sure that the Netman configuration file is not corrupted and that it contains entries for all the valid services. When you have corrected the problem, run StartUp to start netman.
If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW018E Error building message file: !1, !2
AWSEDW019E An internal error has occurred. Netman was unable to open its message file, NetReq.msg, for reading. The following messages were given:Operating system error: "system_error"Events file library error: "library_error".
Explanation
system_error is the operating system error message.
library_error is a message retrieved from the events file library describing the error.
System action
Netman stops.
Operator response
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW020E An internal error has occurred. Netman was unable to set up its TCP/IP port to listen for service requests. The following operating system message was received: "error_message".
Explanation
error_message is the operating system error message for the error.
System action
Netman stops.
Operator response
Use the error message to try and identify and solve the problem. Make sure that the port number is not being used by another process. When you have corrected the problem, run StartUp to start netman.
If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW021E Netman was unable to stop the following service as part of the child process cleanup procedures performed before exiting: "service". The following error message was given by the operating system: "error_message".
Explanation
service identifies the service that cannot be stopped.
error_message is a message that contains the operating system error.
System action
Netman continues, but the operation is not performed.
Operator response
Use the operating system error message to determine the reason for the problem. Use operating system commands to stop any child processes that are still running. When you have corrected the problem, run StartUp to start netman.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW022E An internal error has occurred. Netman encountered an IPC error when waiting for a service request to arrive or when reading a service request, from the following port: "port_number". The error message is as follows: "system_error"
Explanation
port_number is the port to which Netman is waiting on request.
system_error indicates when the error occurred and the operating system error message.
Note: if the error occurred while waiting for a request, the port_number variable contains the system_error and the second variable is unused.
System action
Netman continues, but the operation is not performed.
Operator response
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW023E An internal error has occurred. Netman encountered an IPC error when trying to close the connection with the client process on the following port: "port_number", "system_error".
Explanation
port_number is the connection port number.
system_error is a message that contains the operating system error.
System action
Netman continues, but the operation is not performed.
Operator response
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW024E An internal error has occurred. Netman encountered an error while it was trying to read a service request from the following message file: "message_file". The following operating system error message is given: "error_message".
Explanation
message_file contains the fully qualified name for the message file.
error_message contains the operating system error message.
System action
Netman continues, but the operation is not performed.
Operator response
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW025E An internal error has occurred. Netman was unable to pass the circuit information as an argument to the program associated with the following service request: "service_request". The operating system error message is as follows: "error_message".
Explanation
Old message: Error forming string to pass circuit information.
error_message contains the operating system error message.
service_request is the service request packet received by netman.
System action
Netman continues, but the operation is not performed.
Operator response
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW026E Netman was unable to run the child process associated with the following service request: "service_request". The operating system error message is as follows: "error_message ".
Explanation
service_request is the service request packet received by netman
error_message contains the error type and the operating system error message. See the NetConf file for the list of service numbers and the associated programs.
System action
Netman continues, but the operation is not performed.
Operator response
Check that the associated program specified in the NetConf file is present and can be run by the <TWS_user>. If you find a problem and correct it, run StartUp to restart netman. If the program specifications in the NetConf file are correct, an internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW027E An internal error has occurred. Netman is unable to send an acknowledgment packet in response to the following service request: "service_request ". The following error message is given: "error_message"
Explanation
service_request is the service request packet received by Netman.
error_message gives more information about the error.
System action
Netman continues, but the operation is not performed
Operator response
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW028I Received stop_netman: !3
AWSEDW029E Error closing net link: !1, !2
AWSEDW030E An internal error has occurred. Netman was unable to set the signal handler to ignore one of the following signals: SIGTTOU, SIGTTIN, and SIGTSTP. The signal number is as follows: "signal_number". The operating system error message is as follows: "system_error"
Explanation
Old message: System error in sigaction.
signal_number is the number of the signal.
system_error is the operating system error message.
System action
Netman stops.
Operator response
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW031E An internal error has occurred. Netman was unable to create a new session when trying to become a daemon process. The operating system error message is as follows: "error_number", "error_message".
Explanation
Old message: System error in setsid.
error_number and error_message give more information about the error.
System action
Netman stops.
Operator response
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW032E An internal error has occurred. Netman was unable to change the current working directory to the root directory when trying to become a daemon process. The operating system error message is as follows: "error_number", "error_message".
Explanation
Old message: System error in chdir.
error_number and error_message give more information about the error.
System action
Netman stops.
Operator response
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW033W The following duplicate service request has been received: "service_request". The following is the error message: "error_message"
Explanation
service_request is the service request packet received by Netman
error_message gives more information about the error.
System action
Netman continues, but the duplicate service request is ignored.
Operator response
The service you are trying to start is already running. If you are trying to restart the service, issue a conman stop command and issue the start request again.
AWSEDW035W The following request cannot be performed because netman is emptying its request cache: "service_request"
Explanation
Netman empties service requests from its message file, NetReq.msg, at startup, and at other times, as required. All requests are discarded, except for the last one. The last one is also discarded if it is a netman stop request.
service_request is the service request received by netman.
System action
Netman continues.
Operator response
None. However, if this message appears repeatedly, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW042I Terminating, no sons active
AWSEDW043I Terminating, no children active
AWSEDW044W Son !1 pin !2 is gone, status: !3
AWSEDW045W Client pin !1 is gone, status: !2
AWSEDW046I Terminating, total cpu !1
AWSEDW047I Stdlists switched. Total cpu time !1
AWSEDW048I Command !1 is !2 options !3.
AWSEDW049I Opened IPC successfully.
AWSEDW050E An internal error has occurred. Netman, while attempting to launch itself as a daemon, cannot set the real group id (gid) to the HCL Workload Automation group id. The error occurred in the following source file: "file_name", at line: "line_number". The operating system error message is as follows: "error_message", !4.
Explanation
file_name is the name of the source file where the error occurred.
line_number is the line number of the source file where the error occurred.
error_message is the operating system error message.
System action
Netman stops.
Operator response
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW051E An internal error has occurred. Netman, while attempting to launch itself as a daemon, cannot set the real user id (uid) to the HCL Workload Automation user id. The error occurred in the following source file: "file_name", at line: "line_number". The operating system error message is as follows: "error_message", !4.
Explanation
file_name is the name of the source file where the error occurred.
line_number is the line number of the source file where the error occurred.
error_message is the operating system error message.
System action
Netman stops.
Operator response
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW052W IP address validation not performed for request: !1. Connection received from IP address: !2. !3. Service request accepted.
AWSEDW053E Netman could not validate the IP address for a service.Service request: "service_request"IP address: "IP_address"Error type: "error_type"Error message: "validation_error".
Explanation
service_request is the service request packet received by Netman
IP_address is the IP address of the client process.
error_type is a string containing either the string **ERROR** or the string **WARNING**.
validation_error is a message containing the validation error.
System action
Netman continues, but the operation is not performed.
Operator response
Refer to the HCL Workload Automation Administration Guide for a description of IP validation operations.
AWSEDW056E Netman was unable to retrieve its product group name from the components file. Netman might not have been installed correctly, or the components file might not be correct.
Explanation
See message.
System action
Netman stops.
Operator response
Update the components file so that there is a valid entry for Netman.
On UNIX, the default components file is located in /usr/unison/components. The following environment variable can be used to specify another location: UNISON_COMPONENT_FILE.
On Windows, the location of the components file is stored in the following Registry entry: \HKEY_LOCAL_MACHINE\SOFTWARE\Unison Software, Inc\ComponentLocationDB\DBPath.
When you have corrected the problem, run StartUp to restart netman.
AWSEDW057I Netman installed under group '!1'.
AWSEDW058E Netman cannot find the program file associated with the following service number: "service_number" and action number: "action_number" in its configuration file"netman_configuration_file".
Explanation
service_number identifies the service for which the program cannot be found.
action_number identifies the action in the netman configuration file.
netman_configuration_file is the name of the configuration file for netman.
System action
The program continues. The service is not launched.
Operator response
Verify the existence and accessibility of the program file associated with the service that Netman failed to launch. Correct the location and name of the file, if appropriate, either on disk or in the file, and run StartUp to restart netman.
AWSEDW059E Netman was unable to get information about its configuration file, "file_name". The operating system error message is as follows: "system_error"
Explanation
Netman periodically reads this file to update its internal service table.
file_name is the fully qualified name of the configuration file.
system_error is the operating system error message.
System action
If this problem occurs at start up, Netman stops. Otherwise, netman continues, using the configuration data it has in memory.
Operator response
Make sure that the configuration file exists and that the <TWS_user> has read access to it. If you find and correct an error, run StartUp to restart netman.
AWSEDW060E Netman found a non-valid service request in its configuration file. [ SEE AWSEDW058 FOR FORMATs , NetConf. "file_name":"ServiceEntry": "service_number" !4 !5
Explanation
file_name is the fully qualified name for the configuration file.
ServiceEntry specifies the entry number in the configuration file.
service_number is the invalid service number.
System action
Netman continues, but the operation is not performed.
Operator response
Edit the Netman configuration file, NetConf, and make sure that all the entries are valid service entries. If you find and correct an error, run StartUp to restart netman.
AWSEDW061E Netman was unable to create a new thread. Pipe connections are not supported.
Explanation
Old message: CreateThread failed
An API Window has failed.
System action
The program proceeds. Netman can continue supporting socket connections.
Operator response
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW062E Netman cannot enable a named pipe server process to wait for a client process. The error occurred in the following source file: "file_name", at line: "line_number". The operating system error message is as follows: "error_number", from the following call: "system_call".
Explanation
Old message: ConnectNamedPipe() failed
file_name is the name of the file where the error occurred.
line_number is the line number in the file where the error occurred.
error_number is the operating system error number.
system_call is the system call being performed when the error occurred.
System action
The program proceeds. Netman can continue supporting socket connections.
Operator response
Read the description of the internal system error and try to correct it. If you find and correct an error, run StartUp to restart netman.
If the error persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW063E An internal error has occurred. Netman was unable to identify the following user that is trying to start a service: "user_ID".
Explanation
This Windows problem occurs when gconman starts a connection as the logged-on user.
Old message: Received NULL token from token list for id:
user_ID is the ID of the user running gconman.
System action
Netman proceeds. The process will not be started.
Operator response
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW064I Pipe Connections will be supported
AWSEDW065E CreateEvent() failed: File !1 (line !4): Error !2 from !3
AWSEDW066E Netman encountered an error trying to write data to a pipe. The error occurred in the following source file: "file_name", at line: "line_number". The operating system error message is as follows: "error_number", from the following call: "system_call".
Explanation
Old message: WriteFile() failed:
file_name is the name of the file where the error occurred.
line_number is the line number in the file where the error occurred.
error_number is the operating system error number.
system_call is the system call being performed when the error occurred.
System action
The program proceeds.
Operator response
Read the description of the internal system error and try to correct it. If you find and correct an error, run StartUp to restart netman.
If the error persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW067E Netman encountered an error trying to read data from a pipe. The error occurred in the following source file: "file_name", at line: "line_number". The operating system error message is as follows: "error_number", from the following call: "system_call".
Explanation
Old message: ReadFile() failed:
file_name is the name of the file where the error occurred.
line_number is the line number in the file where the error occurred.
error_number is the operating system error number.
system_call is the system call being performed when the error occurred.
System action
The program proceeds.
Operator response
Read the description of the internal system error and try to correct it. If you find and correct an error, run StartUp to restart netman.
If the error persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW068E Netman encountered an error trying to create a named pipe. The error occurred in the following source file: "file_name", at line: "line_number". The operating system error message is as follows: "error_number", from the following call: "system_call".
Explanation
Old message: CreateNamedPipe() failed:
file_name is the name of the file where the error occurred.
line_number is the line number in the file where the error occurred.
error_number is the operating system error number.
system_call is the system call being performed when the error occurred.
System action
The program proceeds.
Operator response
Read the description of the internal system error and try to correct it. If you find and correct an error, run StartUp to restart netman.
If the error persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW069E Netman was unable to create a handle for a new thread starting Service Client thread. The error occurred in the following source file: "file_name", at line: "line_number". The operating system error message is as follows: "error_number", from the following call: "system_call".
Explanation
Old message: CreateThread() failed
file_name is the name of the file where the error occurred.
line_number is the line number in the file where the error occurred.
error_number is the operating system error number.
system_call is the system call being performed when the error occurred.
System action
The program proceeds. Netman can continue supporting socket connections.
Operator response
Read the description of the internal system error and try to correct it. If you find and correct an error, run StartUp to restart netman.
If the error persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW070E An internal error has occurred. Netman could not write to the Windows event log. The operating system error message is as follows: "error_number". The error occurred in the following source code file: "file_name" at line"line_number".
Explanation
error_number is the error code returned by the system.
file_name is the source code file name.
line_number is the source code line number.
System action
Netman continues, but the operation is not performed.
Operator response
This is a system error. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSEDW073I Alias !1 is !2 options !3.
AWSEDW074I Invalid alias entry in !1:!2: !3
AWSEDW075I Netman (pid=!1 pgid=!2) was started by the starter process (pid=!3 pgid=!4)
AWSEDW080I Opened SSL IPC successfully
AWSEDW081W SSL port set to 0 - no SSL IPC opened
AWSEDW090E An attempt has been made to perform a non-secure action from a remote workstation to the local workstation. The remote workstation does not have the correct security rights to access the local workstation.
Explanation
It is possible that the Security or Symphony files have been in some way corrupted on the remote workstation. It is also possible that the Security file on the remote workstation might have been hacked.
System action
The program proceeds.
Operator response
Verify that the Security file on the remote workstation is the same as that sent by the master domain manager during the centralized security initialization. Check that the Symphony files on both the remote and the local workstations are the same.
To resolve a problem of Symphony file corruption, see the chapter on the subject in the Troubleshooting guide.
If you find and correct an error, run StartUp to restart netman.
AWSEDW091E Netman was unable to start a new process. Your HCL Workload Automation license expired "exp_date".
Explanation
Your HCL Workload Automation license has expired.
System action
The program proceeds. Netman can continue but it is not able to start new processes.
Operator response
An internal error has occurred. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSETO001E An internal error has occurred. The HCL Workload Automation Object Monitor plug-in is unable to write the configuration for the agent "workstation_name", the reason is: "reason".
Explanation
This problem indicates that the HCL Workload Automation Object Monitor plug-in has encountered an error while attempting to produce the configuration file for the agent workstation_name.
reason is the system error that is causing the problem.
System action
The configuration for the agent is not produced. The monitors on the agent do not work correctly.
Operator response
See and resolve the error reported as reason.
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSETO002E The event "event_name" of type "event_type" is not valid, because filters are not allowed on Stop reason when Running=true is specified.
Explanation
The user has created an event rule where the event event_name of type event_type has both Running=true and the Stop reason filters specified.
This is not allowed because, for WorkstationStatusChanged events, the StopReason field is present only when the workstation is going down and then when Running=false
System action
The event rule is not saved.
Operator response
Specify only one of the two filters.
AWSETO003E The event "event_name" of type "event_type" is not valid, because filters are not allowed on Restarting when Running=true is specified.
Explanation
The user has created an event rule where the event event_name of type event_type has both Running=true and the Restarting filters specified.
This is not allowed because, for events of type event_type, the Restarting field is present only when the process on the workstation is going down and then when Running=false
System action
The event rule is not saved.
Operator response
Specify only one of the two filters.
AWSETO004E The event "event_name" of type "event_type" is not valid, because filters are not allowed on No restart reason when Restarting=true is specified.
Explanation
The user has created an event rule where the event event_name of type event_type has both Restarting=true and the No restart reason filters specified.
This is not allowed because, for events of type event_type, the No Restart Reason field is present only when the process is not automatically restarted, and then when Restarting=false
System action
The event rule is not saved.
Operator response
Specify only one of the two filters.
AWSETO005E The event "event_name" of type "event_type" is not valid, because filters are not allowed on No restart reason when StopReason=Stop is specified.
Explanation
The user has created an event rule where the event event_name of type event_type has both Restarting=true and the No restart reason filters specified.
This is not allowed because, for events of type event_type, the No Restart Reason field is present only when the process is not automatically restarted, and then when Restarting=false
System action
The event rule is not saved.
Operator response
Specify only one of the two filters.
AWSETO006E The event "event_name" of type "event_type" is not valid, because filters are not allowed on Unlink reason when LinkStatus=Linked is specified.
Explanation
The user has created an event rule where the event event_name of type event_type has both LinkStatus=Linked and the Unlink reason filters specified.
This is not allowed because, for ParentWorkstationLinkChanged and ChildWorkstationLinkChanged events, the UnlinkReason field is present only when the link to the parent or to the child workstation is lost and then when LinkStatus=Unlinked.
System action
The event rule is not saved.
Operator response
Specify only one of the two filters.