Error messages for the wrc and wrcmdpcr commands

If there is an error executing the wrc or wrcmdpcr command, the following error codes are returned as the program exit code and the corresponding message is displayed.

Table 1. Error messages for the wrc command
Exit Code Message Reason Applies to

1

Invalid argument: Malformed user:password

Invalid argument: Unknown action

Invalid argument: Target endpoint definition: {0}

Invalid argument: Controller endpoint definition: {0}

Error reserving memory for arguments

Invalid argument: Unknown option: {0}

 Invalid parameters passed to command. Verify the parameters in the command line are valid and comply with the expected command syntax both

2

 Error: No settings for the Server URL found There is no ServerURL setting in the registry or properties file. Ensure the configuration is correct and the ServerURL configuration field has the correct URL for the remote control server. both

3

Error {0}
(RC_SERVER_CONN_ERROR):
Unable to connect to the Server

 Unable to connect to the configured server. Ensure the configuration is correct and the ServerURL configuration field has the correct URL for the remote control server. both

4

Error {0} (RC_LOGIN_ERROR):
Unable to login to the Server
with the specified
credentials

 Cannot log in to the Remote Control server with the credentials provided in the command parameters. Ensure the correct user credentials are entered in the command line. both

5

Error {0}
(RC_CREATE_SESSION_ERROR):
Unable to create RC session

 The remote control session to launch the command cannot be created. The normal causes are that the user does not have permissions or the target cannot be found. both

6

Error {0}
(RC_LOCAL_LAUNCH_ERROR):
Unable to launch the Java™ Web Start
controller

 The Java™ Web Start Remote Control Controller cannot be launched on the local machine. Usually this would be caused by a supported JRE not being installed and set up to handle Java™ Web Start applications correctly. wrc

7

Error: Failed to load FIPS support
libraries

 The settings specify FIPS mode but the required libraries cannot be loaded. This can be caused by the installed files being corrupted. both

8

Error: Failed to load OpenSSL support
libraries

There was an error loading the OpenSSL libraries. This can be caused by the installed files being corrupted. both

10

Error {0}
(RC_REMOTE_CONNECT_ERROR):
Unable to connect to the remote
controller to launch the session

 The connection to the remote controller cannot be established. Verify that the target software is running on the specified remote controller endpoint and it is possible to establish remote control sessions to it. wrc

10

Error {0}
(RC_REMOTE_CONNECT_ERROR):
Unable to connect to the target

The connection to the target endpoint cannot be established. Verify that the target software is running on the specified target endpoint and it is possible to establish remote control sessions to it. wrcmdpcr

16

Error {0}
(RC_REMOTE_LAUNCH_ERROR):
Unable to launch controller on the
remote machine

 After connecting to the target, launching the controller failed. Usually this would be caused by a supported JRE not being installed and set up to handle Java™ Web Start applications correctly. wrc

16

Error {0}
(RC_REMOTE_CMD_EXEC_ERROR):
Unable to launch the command in the
remote machine

After connecting to the target, the specified command could not be executed. Verify the command is correct and is not interactive, and can be executed locally on the target machine. wrcmdpcr

17

Error {0}
(RC_REMOTE_CMD_TERM_ERROR):
The remote command terminated
abnormally

After connecting to the target and successfully launching the command, the command has terminated abnormally. Verify the command is correct and is not interactive, and can be executed locally on the target machine. wrcmdpcr

20

Error {0}
(RC_UNKNOWN_TARGET):
The specified target is not registered
with Remote Control

 The specified endpoint is not a registered remote control target. This could apply to the specified target endpoint or the controller endpoint. Verify the host names or IP addresses are correct and belong to machines that have a correctly registered remote control target. both

21

Error{0 (RC_UNREACHABLE_TARGET):
The specified target is offline
or does not have any connectivity
information associated with it.

The specified endpoint is a registered remote control target but it has no connectivity information or the connection cannot be established. This could apply to the specified target endpoint or the controller endpoint. Ensure the remote control target is running and has reported the current connectivity details to the remote control server and verify a remote control session can be established with that target. both

22

Error {0}
(RC_NO_PERMISSIONS):
No permissions to start the session
in the selected mode.

The specified endpoint is a registered remote control target but the user specified in the command line is not allowed to connect to the remote control target in the specified endpoint. This could apply to the specified target endpoint or the controller endpoint. Contact your remote control Administrator to verify the permissions both

23

Error {0}
(RC_TARGET_TOO_OLD):
The target on the remote machine is
too old and should be updated

The endpoint the CLI tool is attempting to connect to has an installed version of the remote control target software that is too old. This could apply to the specified target endpoint or the controller endpoint. Upgrade the target software in the endpoint. both

24

Error {0}
(RC_TARGET_IS_BUSY):
The target on the remote machine is
already in a session

The endpoint the CLI tool is attempting to connect to is already in a remote control session so it cannot handle the connection by the CLI tool. This could apply to the specified target endpoint or the controller endpoint. Try the CLI command again once the target is free. both