AWSBEH - Web library messages

This section lists error and warning messages that might be issued by the routines that use the Web library.

The message component code is BEH.

AWSBEH001E

The connection configuration file "file_name" containing the connection properties cannot be found.

The error occurred while trying to open the file that contains the connection properties. The files checked are the useropts and localopts files.

The command line client does not have the connection configuration data to contact the server.

file_name identifies the configuration file that cannot be found.

The operation cannot be performed.

Check whether and why this file is missing. If it has been renamed or moved to another location, rename it or move it back and retry the operation. If the file cannot be found, uninstall and reinstall HCL Workload Automation on this computer.

AWSBEH002E

The target host computer is not defined in the connection configuration file or the supplied command parameters.

Host is one of the required parameters for the connection to the command line server.

The command line client does not have the connection configuration data to contact the server.

The operation cannot be performed.

Check the useropts and localopts files and ensure that the host keyword is defined and identifies a valid host.

Alternatively, supply the host as a command parameter.

The Reference Manual for the full syntax of the connection parameters.

AWSBEH003E

The protocol is not defined in the connection configuration file or the supplied command parameters.

Protocol is one of the required parameters for the connection to the command line server.

The command line client does not have the connection configuration data to contact the server.

The operation cannot be performed.

Check the useropts and localopts files and ensure that the protocol keyword is defined and identifies a valid protocol.

Alternatively, supply the protocol as a command parameter.

The Reference Manual for the full syntax of the connection parameters.

AWSBEH004E

The target host port is not defined in the connection configuration file or the supplied command parameters.

Port is one of the required parameters for the connection to the command line server.

The command line client does not have the connection configuration data to contact the server.

The operation cannot be performed.

Check the useropts and localopts files and ensure that the port keyword is defined and identifies a valid port.

Alternatively, supply the port as a command parameter.

The Reference Manual for the full syntax of the connection parameters.

AWSBEH005E

The user is not defined in the connection configuration file or the supplied command parameters.

User is one of the required parameters for the connection to the command line server.

The command line client does not have the connection configuration data to contact the server.

The operation cannot be performed.

Check the useropts and localopts files and ensure that the username keyword is defined and identifies the user making the connection.

Alternatively, supply the user as a command parameter.

The Reference Manual for the full syntax of the connection parameters.

AWSBEH006E

The password is not defined in the connection configuration file or the supplied command parameters.

Password is one of the required parameters for the connection to the command line server.

The command line client does not have the connection configuration data to contact the server.

The operation cannot be performed.

Check the useropts and localopts files and ensure that the password keyword is defined and identifies the password of the user making the connection.

Alternatively, supply the password as a command parameter.

The Reference Manual for the full syntax of the connection parameters.

AWSBEH007W

The supplied protocol "protocol" is not valid. It must be http or https.

Protocol is one of the required parameters for the connection to the command line server.

protocol is the value that is not valid.

The command line client does not have the connection configuration data to contact the server.

The operation cannot be performed.

Check the supplied value of the protocol keyword and change it to a valid value (http or https).

The Reference Manual for the full syntax of the connection parameters.

AWSBEH008E

The user options properties file "file_name" could not be opened or was not found.

The error occurred while opening the user file that contains the connection properties.

file_name identifies the user file that cannot be opened.

The command line client does not have the connection configuration data to contact the server.

The operation cannot be performed.

Check whether and why this file could not be opened. If it has been renamed or moved to another location, rename it or move it back and retry the operation. If the file cannot be found, uninstall and reinstall HCL Workload Automation on this computer.

AWSBEH009E

The connection configuration file "file_name" identified in the command by the -file keyword could not be opened or was not found.

The command line client does not have the connection configuration data to contact the server.

file_name identifies the connection parameters file that cannot be opened.

The operation cannot be performed.

Check that you have supplied the correct name and path for the file. Correct the error found and retry the operation.

AWSBEH010E

An internal error has occurred. A function has tried to initialize the HTTP libraries more than once.

See message.

The operation is not performed.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBEH011E

An error occurred while contacting the server "server_name" on port "port_number".

See message.

server_name identifies the server that cannot be contacted.

port_number identifies the port being used for the communication.

The operation is not performed.

Check that the connection parameters (the keywords: host, protocol, port, username, password, proxy, and timeout in the localopts file or supplied with the command) are correct. Check that the server is accessible in the network by pinging it. Fix any errors found and retry the operation.

AWSBEH012E

The supplied file "file_name" could not be found or opened.

See message.

The operation is not performed.

Check that the file has been correctly identified. If not, retry the operation, identifying the file correctly.

If it has been correctly identified, verify the following:
  • That the file exists. If it does not, create it.
  • That the user of HCL Workload Automation can access the file in all modes. If it does not, change the access permissions.
  • That the file has not been locked by another process. If it has, close that process.
Retry the operation. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBEH013E

An internal error has occurred. WebLib could not allocate memory for processing the supplied file.

See message.

The operation is not performed.

The file might be too large. Retry the operation with a smaller file. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBEH014E

An error occurred while reading the supplied file "file_name".

See message.

The operation is not performed.

Verify the following:
  • That the user of HCL Workload Automation has read access to the file. If it does not, change the access permissions.
  • That the file has not been locked by another process. If it has, close that process.
Retry the operation. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBEH015E

An internal error occurred while initializing the AXIS HTTP libraries.

See message.

The operation is not performed.

If this is the first time you have tried using the command line client it might be that the libraries were not installed correctly, in which case uninstall and reinstall the command line client, and retry the operation.

If this is not the first time, retry the operation, and if the error persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBEH016E

An error occurred while contacting the server using the AXIS HTTP libraries.

See message.

The operation is not performed.

Check that the server is accessible in the network by pinging it. Fix any errors found and retry the operation. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm..

AWSBEH017E

An internal error has occurred "error" while using the AXIS HTTP libraries.

See message.

The operation is not performed.

The quoted error message might help you to identify the problem and resolve it, in which case retry the operation. If you cannot identify or solve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBEH018E

An error occurred while setting the credentials for user ID "user".

An error occurred when setting the credentials with the AXIS HTTP libraries.

user identifies the user whose credentials cannot be set.

The operation is not performed.

Verify the connection and the user ID and password supplied. If the details are not correct, correct them and retry the operation. If they are correct, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBEH019W

The format of the proxy server "proxy_server" and its port "port" is not valid.

See message.

proxy_server and port identify the proxy server connection information that is not valid.

The operation is not performed.

Verify the proxy server and port information supplied. The proxy_server must be a correctly formed server name, expressed either as a host name or an IP address. The port must be a number between 1 and 65535. Do not supply the colon separator (:) between server and port; it is supplied by the software. Correct the error and retry the operation.

AWSBEH021E

The user "user" is not authorized to access the server on host "host" using port "port".

There has been an authentication failure on contacting the server.

The operation is not performed.

Check the following:
  • Check the supplied values for the indicated fields.
  • Check that the user details in the Security file are correct, and that the user has permission to access the server.
  • Ensure that your SSL configuration and certificates are correct.
  • If you have made any changes to the SSL configuration on the server, ensure that the application server has been restarted.

Correct any errors and retry the operation.

AWSBEH022E

The server on host "host" cannot be contacted.

The indicated server cannot be contacted.

The operation is not performed.

Check that the server is running and the network is up. Ping the server from the client.

If there is no network problem between the client and the server, check the supplied values for the connection. Ensure that your SSL configuration and certificates are correct. If you have made any changes to the SSL configuration on the server, ensure that the application server has been restarted. Correct any errors and retry the operation.

AWSBEH023E

Unable to establish communication with the server on host "host" using port "port".

The indicated server can be contacted, but is not listening on the indicated port.

The operation is not performed.

Check that you are using the correct port number. Check if there is a firewall in place between the client and the server that is blocking the indicated port. Correct any errors and retry the operation.

AWSBEH024E

The connection with the server on host "host" has timed out.

The timeout is supplied as one of the connection parameters, either as part of the command, in a file of connection parameters, or by default from the useropts or localopts file.

The operation is not performed.

Increase the value of the timeout parameter and retry the command.

AWSBEH025E

The server response cannot be understood. There is a probably a mismatch with language variables, codesets, codepages, or other configuration elements of the international communication environment.

See message.

The operation is not performed.

Check that the language variables, codesets, codepages, or other configuration elements of the international communication environment match on the client and server. Correct any error you find and retry the command.

AWSBEH026E

It was not possible to establish an SSL communication with the server on host: "host" using port "port" because of the following error: "error".

The server can be contacted but the SSL handshake failed.

The operation is not performed.

Check that the following parameters in the useropts or localopts file: port, clisslcipher, and clisslservercertificate match the required values on the server. Correct any errors and retry the operation.

AWSBEH027E

The connection parameters were not specified completely in your useropts or localopts file. Correct the file, or submit the connection parameters as part of the command syntax.

See message.

The command is not performed.

Do one of the following:
  • Edit the useropts or localopts file, correct the connection parameters, save the file and resubmit the command.
  • Create a file, insert the connection parameters, save the file, and resubmit the command, identifying the file of connection parameters with the -file attribute.
  • Resubmit the command, adding the connection parameters to the command line as arguments. Run <command_name> -U to determine the syntax, or look in the Reference Manual.
Reference Manual for full details of the connection parameters and their syntax.

AWSBEH028E

The SSL connection using GSKit (FIPS 140-2 mode active) with the server fails.

See message.

The command is not performed.

Check the certificate in the localopts.

User's Guide and Reference for full details of the connection parameters, certificates, and their syntax.

AWSBEH029E

The SSL connection using OpenSSL Toolkit with the server fails.

See message.

The command is not performed.

Check the certificate in the localopts.

User's Guide and Reference for full details of the connection parameters, certificates, and their syntax.

AWSBEH030E

The connection with the server fails.

See message.

The command is not performed.

Check the parameters in the localopts.

Reference Manual for full details of the connection parameters, certificates, and their syntax.

AWSBEH100E

There is a syntax error in the connection parameters.

See message.

The operation is not performed.

Check the supplied connection parameters. You might have mistyped a keyword, or omitted a separator between keywords or between a keyword and its value. Correct the error and retry the operation.

AWSBEH101E

An internal error occurred while initializing the WebLib HTTP libraries.

See message.

The operation is not performed.

Ensure that the connection parameters are correct. Retry the operation. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBEH102E

No valid command was supplied.

You submitted a command string from the command line client but it did not contain a recognizable command.

The operation is not performed.

Verify the syntax of the command. Correct the error and retry the operation.

AWSBEH103E

Too many commands have been supplied, or a command has been duplicated.

The command line string contains too many commands, or a command has been submitted twice. Each command string must comprise one command and its associated attributes.

The operation is not performed.

Verify the syntax of the command. Correct the error and retry the operation.

AWSBEH104E

The following HTTP communication failure has occurred: "HTTP_return_code".

See message.

The operation is not performed.

Check that the server is running and the network is up. Ping the server from the client.

If the network is working correctly, the problem might have been temporary. Retry the command.

Otherwise, solve the network connection problem and then retry the operation.

AWSBEH105E

The following HTTP response failure was received from the server: "HTTP_return_code".

See message.

The operation is not performed.

Use the information in the HTTP_return_code to diagnose and resolve the problem.

Check that the server is running and the network is up. Ping the server from the client.

If the network is working correctly, the problem might have been temporary. Retry the command.

Otherwise, solve the HTTP problem and then retry the operation.

AWSBEH106E

There is a syntax error. The required value for keyword "keyword" is missing.

Each keyword must have an associated value. After the indicated keyword the corresponding value was not found.

The operation is not performed.

Verify the syntax of the command. Correct the error and retry the operation.

AWSBEH107E

There is a syntax error. The supplied date is not in the format specified in the useropts or localopts files.

See message.

The operation is not performed.

Either reissue the command using the correct date format or change the date format in the useropts or localopts file.

AWSBEH108E

There is a syntax error. The format of the time in the date is incorrect.

See message.

The operation is not performed.

Either reissue the command using the correct time format or change the time format in the useropts or localopts file.

AWSBEH109E

There is a syntax error. The time zone is not valid.

See message.

The operation is not performed.

Reissue the command using the correct time format or change the time format in the useropts or localopts file.

AWSBEH110E

There is a syntax error. A start or finish time in the format hhmm is required when you specify a time zone in the -from or -to options.

One of the following has occurred:
  • The plan -from or -to time has not been explicitly defined when a time zone has been used. When you specify a time zone for the plan -from or -to date you cannot use the default time and so must define it explicitly. This is to avoid any ambiguity between the time zone of the master domain manager and the time zone defined in the command. If no time zone is specified, the default -from or -to time uses the time zone of the master domain manager.
  • You have supplied a plan -from or -to time that is not in the format hhmm (note that you must enter the leading zero if the start time is less than 1000).

The submitted command cannot be performed.

Correct the -from or -to time definition and retry the command.

AWSBEH111E

The following internal error occurred while opening the Symphony file: "error".

See message.

The confirm action cannot be executed

Verify the following:
  • That the Symphony file exists. Run JnextPlan to create it if not.
  • That the user issuing the command has access rights to the Symphony file. Change the user permissions, if not.
Retry the command. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBEH112W

There is a syntax error. The -from parameter was ignored because you are trying to extend a plan.

You are trying to extend the plan, for which action the -from parameter is not required.

The command is processed, ignoring the -from parameter.

To avoid the reproduction of this message, do not supply a -from parameter when you are extending a plan.

AWSBEH113E

There is a syntax error. A keyword has been used more than once.

See message.

The operation is not performed.

Check the command syntax. Reissue the command, supplying only one instance of each valid keyword.

AWSBEH114E

There is a syntax error. The -to keyword has been specified, but also the -for or the -days keywords, which is not allowed.

You can extend a plan for a period of hours (-for), or a period of days (-days), or both, or until a specific date and time (-to), but you cannot use -to with the -for and -days keywords.

The operation is not performed.

Check the command syntax. Reissue the command, supplying either -to, or one or both of the -for or -days keywords.

AWSBEH115E

The file "file" does not exist or you do not have read access to the file.

See message.

The operation is not performed.

Check that the file is identified correctly, retrying the command with the correct file path and name if it is not.

If it is identified correctly, verify the following:
  • That the file exists, creating it if not.
  • That the user of HCL Workload Automation has read access to the file.
  • That the file has not been locked by another process.
Correct any errors you find and rerun the command.

AWSBEH116E

An error occurred while converting the globalopts option "globalopts_option" to the database global option "db_global_option".

See message.

The operation is not performed.

Check the connection to the server. If the connection is broken solve the connection problem and retry the command. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSBEH118E

There is a syntax error. The time format for the -for value is not [h]hhmm.

See message.

The submitted command cannot be performed.

Correct the value of the -for time definition and retry the command.

AWSBEH144W

Unable to execute the Resync command because the Symphony file is not found.

See message.

The operation is not performed.

Generate the Symphony file and retry the operation.

AWSBEH145W

Unable to execute the Checksync command because the Symphony file is not found.

See message.

The operation is not performed.

Generate the Symphony file and retry the operation.