3 Error Code Reference

242

A Verb has encountered a problem with a dependency specific to the implementation of the Verb (INSIDE of its abstraction barrier) unrelated to the Verb's semantics.

248

Configuration files are corrupt or inaccessible.

253

The command name is not recognized.

254

Internal system error.

243

License has not been accepted by the current user.

249

Cannot connect to the OMS.

250

Wrong credentials for log in to the OMS.

244

Cannot find an option value file.

245

Cannot read in an option value file.

246

An option value file is too big.

add_beacon

0—Beacon added successfully.

129— Syntax Error. The displayed message indicates which argument is syntactically incorrect.

170—Service does not exist.

173—Beacon does not exist.

201—Beacon is already in the monitoring beacons list.

230—Insufficient privileges.

255—Back-end error. Verb failed.

add_group_to_mpa

2—I/O error occurred while writing to the MPA file.

3—The specified MP already exists in the MPA.

4—The group name is empty or not specified.

223—The supplied options are syntactically incorrect.

add_mp_to_mpa

1—File does not exist, is unreadable, or an I/O error occurred.

2—I/O error occurred while writing to the MPA file.

3—The specified MP already exists in the MPA.

4—The target-type definition file cannot be parsed.

5—The MPA filename is not between 1 and 255 characters.

6 —A file of a particular file type is required for another file.

223—The supplied options are syntactically incorrect.

add_target

1—The supplied target type does not exist. Unable to retrieve target metadata from the specified host's Management Agent.

2—Host does not exist.

3—Agent does not exist.

4—Group does not exist.

5—No monitoring credentials set found for target in the repository.

6—Target instance already exists in the repository.

7—The supplied target properties are incomplete.

8—One or more of the supplied target properties are invalid.

15—Target deletion in progress.

20—Unable to connect to the specified host's Agent.

21—Unable to save the target instance to the specified host's Agent.

22—Cannot add more than one Agent target for a single Agent URL.

23—Unable to add an instance of an Agent target without a URL.

219—Insufficient privileges to add the target to the group.

223—Unable to parse command line correctly. Invalid argument value.

File-Fed Option Errors—The errors associated with file-fed options.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

apply_privilege_delegation_setting

0—Setting successfully applied.2—Setting does not exist.3—All or some of the targets are invalid.129—Syntax error. The displayed message indicates which argument is syntactically incorrect.

apply_template_tests

1—Error processing input XML file.4—Insufficient privileges for apply template.6—Target does not exist.7—Incompatible template and target types during apply.8—Test(s) specified for overwriteExisting do not exist in the template.9—Key test(s) specified as disabled for apply.10—Stepgroup contains a step that does not exist in the file.11—Some text property in file does not conform to valid syntax.12—Some text property contains variable but variable value is missing.13—Some transaction property/threshold/collection setting does not conform to required restrictions.50—Generic error.

argfile

Possible return error codes consist of the following list plus all of the errors returned by the Verb specified in the command line file for execution.

244—The file does not exist.

245—There is a problem reading in the file or it does not exist.

246—The file ends inside a quoted token.

247—The argfile options are specified incorrectly.

assign_test_to_target

0—Test assigned to target type successfully.

129—Syntax Error. The displayed message indicates which argument is syntactically incorrect.

190—Test or target type invalid.

230—Insufficient privileges.

255—Back-end error. Verb failed.

change_service_system_assoc

0—Service system changed successfully.

129—Syntax Error. The displayed message indicates which argument is syntactically incorrect.

170—Service does not exist.

171—System <system> does not exist.

172—Key component does not exist.

230—Insufficient privileges.

255—Back-end error. Verb failed.

clone_as_home

1—The source_params parameter is invalid or in wrong format. Example: Source Home location, hostname are missing.

2—Destination properties file format is invalid.

3—Source Home/software library data invalid. No Source Home/software library fetched from the repository matches data specified by user.

4—Product type does not match the specified cloning verb. Example: Attempted to clone a database but specified an Application Server as a source.

5—Invalid input parameters specified. This is a generic error message for all cases not covered by the previous error messages. In some cases, the parameter itself may be in a valid format, but may point to a home that is not readable or corrupt.

6—Error validating Destination home.7—Error validating/collecting information from Source Home. This error is typically returned during Application Server cloning when the Application Server properties file cannot be read from the Source Home.

8—Other internal error occurred: Exceptions within cloning APIs, or validation, database access APIs.

clone_crs_home

1—The source_params parameter is invalid or in wrong format. Example: Source Home location, host name are missing.

2—Destination properties file format is invalid.

3—Source Home/software library data is invalid. No Source Home/software library fetched from the repository matches data specified by user.

4—Product type does not match the cloning verb used. Example: Attempted to clone a database, but supplied an Application Server as a source.

5—Invalid input parameters specified. Generic error message for all cases not covered by previous error messages. In some situations, the parameter itself may be in a valid format, but may point to a home that is not readable or corrupt.

6—Error validating Destination home.7—Error validating/collecting information from Source Home. This error is typically returned during Application Server cloning when the Application Server properties file cannot be read from the Source Home.

8—Other internal error occurred. Exceptions raised within cloning APIs, or validation database access APIs.

clone_database_home

1—The source_params parameter is invalid or in wrong format. Example: Source Home location, host name are missing.2—Destination properties file format is invalid.

3—Source Home/software library data invalid- no Source Home /software library fetched from the repository matches data specified by user.

4—Product type does not match the cloning verb used. Example: You attempted to clone a database but specified an Application Server as a source.

5—Invalid input parameters specified: generic error message for all cases not covered above. In some cases, the parameter itself may be in a valid format, but may point to a home that is not readable or corrupt.

6—Error validating Destination home.7—Error validating/collecting information from Source Home: This error is typically returned during Application Server cloning when the Application Server properties file cannot be read from the Source Home.

8—Other internal error occurred: Exceptions within cloning APIs, or validation, database access APIs.

create_aggregate_service

1—Target does not exist.

2—Target exists.

create_blackout

1—Blackout X already exists.

2—Only Super Administrators are allowed to add a new reason (use get_ blackout_reasons).

3—Agent targets cannot be directly blacked out.

217—The blackout end_time cannot be in the past.

The dates specified will never cause this blackout to take effect.

The difference between the end_time and the start_time must be equal to the duration.

The difference between the repeat interval and the duration must be at least X minutes.

The duration must be -1 (for indefinite blackouts) or positive.

The duration must be at least X minutes.

219—Current user does not have OPERATOR privilege over all blackout targets.

220—Target X does not exist.

223—Unable to parse command line correctly.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

create_group

1—Group X already exists.

2—Cannot add target X to typed group of base type Y.

218—Group X is currently in the process of being deleted.

219—Current user does not have privilege X over all member targets.

220—Member target X does not exist.

223—Unable to parse command line correctly.

Invalid argument value.

Group type is invalid.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

create_privilege_delegation_setting

0—Setting successfully created.

129—Syntax error. The displayed message indicates which argument is syntactically incorrect.

create_red_group

0—Redundancy Group "<red_group_name>" created successfully.

1—Redundancy Group "<red_group_name>" of target type <red_group_type> already exists.

2—Cannot add target "<member_target_type>" to typed group of base type "<red_group_type>".

3—Time Zone Region <timezone_region> does not exist.

4—Redundancy Group Type "<red_group_type>" is invalid.

218—Redundancy Group "<red_group_name>:<red_group_type>" is currently in the process of being deleted.

220—Target "<member_target_name>:<member_target_type>" does not exist.

223—Redundancy Group name "<red_group_name>" is not valid. It may contain only alphanumeric characters, multi-byte characters, a space, "-", "_", ".", ":", and have a maximum length of 256 characters.

223—User name "<owner>" is not valid. It must begin with an alphabetic character, contain only alphanumeric characters, underscores (\"_\"), or periods (\".\"), and have a maximum length of 256 characters.

223—Invalid value for parameter "add_targets": "<add_targets>". Reason: "<add_targets>" is not a name-value pair.

223—Member Targets not of same type.

223—"<generic_redundancy_group>" does not support member of type "<member_target_type>" .

create_role

1—Role by same name already exists.

2—User with same name as role already exists.

4—Privilege is invalid or nonexistent.

5—Target specified in one of the privileges is invalid.

6—The Super Administrator privilege cannot be granted to a role.

7—Role does not exist.

8—Group specified in one of the privileges is invalid.

9—Job in privilege is invalid or nonexistent.

10—Creating a role that you are assigning to the new role.

11—The specified user does not exist.

219—User is unauthorized to perform this action.

223—Unable to parse command line correctly.

Invalid argument value.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

create_service

0—Web application created successfully.

129—Syntax Error. The displayed message indicates which argument is syntactically incorrect.

130—Missing key components.

151—Test validation failed.

171—System <system> does not exist.

172—Key component does not exist.173—Beacon does not exist.

181—No key tests defined.

182—No key beacons defined.

200—Service <target_name> already exists.

230—Insufficient privileges.

255—Back-end error. Verb failed.

create_system

0—System "<system_name:system_type>" created successfully.

110—System "<system_name:system_type>" already exists.

120—Member target "<member_target_name>:<member_target_type>" does not exist.

122—Type "<system_type>" is not a valid System type.

123—Time Zone Region "<timezone_region>" does not exist.

130—Type meta version "<type_meta_ver>" is invalid.

223—System name "<system_name>" is not valid. It must begin with an alphabetic char, contain only alphanumeric chars or any of "- _.:", and have a maximum length of 256 chars.

223—Type meta version "<type_meta_ver>" is invalid. It must contain only numeric and "." characters, and have a maximum length of 8 chars.

223—Timezone_region cannot be null or blank.

223—Invalid value for parameter "add_members": "<add_members>". Reason: "<add_members>" is not a name-value pair.

create_user

1—Target specified in one of the privileges is invalid.

2—Group specified in one of the privileges is invalid.

3—Job specified in one of the privileges is invalid.

4—One of the specified privileges is invalid.

5—Such user already exists.

6—One or more roles to be granted to the new user does not exist.

7—A role with the same name as the new user already exists.

218—A delete is pending against this user until all blackouts and jobs submitted by this user are stopped.

219—User has insufficient privileges to perform this operation.

223—Unable to parse command line correctly:

Invalid argument value.

User name is somehow invalid.

Supplied password does not have the proper format. Example: Password left empty.

File-Fed Option Errors—The errors associated with file-fed options.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

delete_blackout

1—Blackout X created by user Y does not exist.

2—Cannot delete a blackout that has not ended or was not stopped.

219—You (X) do not have the SUPER_USER privilege needed to stop, delete, or modify blackout Y created by user Z.

Only the blackout owner can stop, delete, or modify the blackout.

Current user does not have OPERATOR privilege over all blackout targets.

223—Unable to parse command line correctly.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

delete_group

1—Group X does not exist.

218—Group X is currently in the process of being deleted.

219—Current user does not have sufficient privileges to perform this action.

223—Unable to parse command line correctly.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

delete_job

1—Specified job is invalid or non-existent.

219—User has insufficient privileges to perform this operation.

218—Some executions are not stopped when delete happens.

223—Unable to parse command line correctly.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

delete_metric_promotion

0—SUCCESS

223—SYNTAX_ERRNUM: Input is malformed.

255—VERB_FAILED_ERRNUM: Back-end validation fails.

delete_privilege_delegation_settings

0—Setting successfully deleted.2—All or some of the names are invalid.129—Syntax error. The displayed message indicates which argument is syntactically incorrect.

delete_role

1—Role does not exist.

219—User is unauthorized to perform this action.

223—Unable to parse command line correctly.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

delete_system

0—System "<system_name:system_type>" deleted successfully.

121—System "<system_name:system_type>" does not exist.

122—Type "<system_type>" is not a valid System type.

219—Current user does not have sufficient privileges to perform this action.

223—System name "<system_name>" is not valid. It must begin with an alphabetic character, contain only alphanumeric characters or any of "- _.:", and have a maximum length of 256 chars.

delete_target

15—Target deletion in progress.

219—Insufficient privileges to delete specified target.

220—Target does not exist.

223—Unable to parse command line correctly.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

delete_test

0—Test deleted successfully.

129—Syntax Error. The displayed message indicates which argument is syntactically incorrect.

170—Service does not exist.

174—Test does not exist.

230—Insufficient privileges.

255—Back-end error. Verb failed.

delete_user

1—Cannot delete the repository owner.

2—Specified user does not exist.

3—Cannot delete the current user.

218—A delete is pending against this user until all blackouts and jobs submitted by this user are stopped.

219—User has insufficient privileges to perform this operation.

223—Unable to parse command line correctly.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

disable_test

0—Test disabled successfully.

129—Syntax Error. The displayed message indicates which argument is syntactically incorrect.

170—Service does not exist.

174—Test does not exist

203—Test already disabled.

230—Insufficient privileges.

255—Back-end error. Verb failed.

enable_test

0—Test enabled successfully.

129—Syntax Error. The displayed message indicates which argument is syntactically incorrect.

170—Service does not exist.

174—Test does not exist

202—Test already enabled.

230—Insufficient privileges.

255—Back-end error. Verb failed.

execute_hostcmd

0—Command execution succeeded for all targets.

2—Command execution failed for one or more targets. Detailed errors will be displayed for each failed target.

3—Invalid or unknown targets in the targets list.

4—Preferred credentials are missing for one or more targets.

5—Invalid credential set name.

223—Unable to parse the command line properly.

execute_sql

0—Command execution succeeded for all targets.

2—Command execution failed for one or more targets. Detailed errors will be displayed for each failed target.

3—Invalid or unknown targets in the targets list.

4—Preferred credentials are missing for one or more targets.

5—Invalid credential set name.

223—Unable to parse the command line properly.

export_template

223—Unable to parse command line correctly, or an exception was thrown during SQL handling.

245—There is a problem writing to the file.

extend_as_home

1—The source_params argument is invalid or in the wrong format. Example: Source Home location or host name are missing.

2—Destination properties file format is invalid.

3—Source Home/software library data invalid. No Source Home/software library fetched from the repository matches data specified by user.

4—Product type does not match the cloning verb used. Example: Attempted to clone a database but specified an Application Server as a source.

5—Invalid input parameters specified. Generic error message for all cases not covered by previous error messages. In some cases, the parameter itself may be in a valid format, but may point to a home that is not readable or corrupt.

6—Error validating destination home.

7 —Error validating/collecting information from source home.

Typically returned during Application Server cloning when the Application Server properties file cannot be read from the Source Home.

8—Other internal error occurred: Exceptions within cloning APIs, or validation, database access APIs.

extend_crs_home

1—The source_params parameter is invalid or in the wrong format. Example: Source Home location or host name are missing.

2—Destination properties file format is invalid.

3—Source Home/software library data invalid. No Source Home/software library fetched from the repository matches data specified by user.

4—Product type not matching with the cloning verb used. Example: Attempted to clone a database, but specified an Application Server as a source.

5—Invalid input parameters specified. Generic error message for all cases not covered by previous error messages. In some cases, the parameter itself may be in a valid format, but may point to a home that is not readable or is corrupt.

6—Error validating destination home.

7—Error validating/collecting information from Source Home:

Typically returned during Application Server cloning when the Application Server properties file cannot be read from the Source Home.

8—Other internal error occurred: Exceptions within cloning APIs, or validation, database access APIs.

extend_rac_home

1—The source_params parameter is invalid or in wrong format. Example: Source Home location, host name are missing.

2—Destination properties file format is invalid.

3—Source Home/software lib data invalid- no Source Home /software library fetched from the repository matches data specified by user.

4—Product type does not match the cloning verb used. Example: tried to clone database, but gave app server as source.

5—Invalid input parameters specified: generic error message for all cases not covered above. In some cases the parameter itself may be in a valid format, but may point to a home which is not readable or corrupt.

6—Error validating destination home.

7—Error validating/collecting information from Source Home: Typically returned during Application Server cloning when the Application Server properties file cannot be read from the Source Home.

8—Other internal error occurred: Exceptions within cloning APIs, or validation, database access APIs.

extract_template_tests

2—Error serializing XML output.3—Insufficient privileges for extract template.5—Template does not exist in repository.50—Generic error.

get_aggregate_service_info

1—Target does not exist.

2—Target exists.

get_aggregate_service_members

1—Target does not exist.

2—Target exists.

get_blackout_details

1—Blackout X created by user Y does not exist.

223—Unable to parse command line correctly.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

get_blackout_reasons

OMS Connection Errors—The errors associated with connecting to the executing OMS.

get_blackout_targets

1—Host X does not exist.223—Unable to parse command line correctly.220—Target X does not exist.

get_blackouts

1—Host X does not exist.

220—Target X does not exist.

223—Unable to parse command line correctly.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

get_group_members

1—Group X does not exist.

223—Unable to parse command line correctly.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

get_groups

Other than the confirmation message, the get_groups verb only generates syntax errors. The SQL invoked by get_groups does not throw any exception.

0—All groups (TargetName, TargetType) in the repository are displayed.

223—Syntax Error: Argument -script cannot be specified with a value.

223—Syntax Error: -format argument "name" value must match one of these strings: "script|pretty|csv".

223—Syntax Error: Invalid value for parameter "format": "name:<format_name>;column_separator=<column_separator_char>". Reason: "column_separator=column_separator_char" is not a name-value pair.

223—Syntax Error: -format argument contains an unrecognized key name <key_name>

get_jobs

223—Unable to parse command line correctly.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

get_system_members

121—System "<system_name:system_type>" does not exist.

get_targets

223—Unable to parse command line correctly.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

help

1—There is no help available.

223—Unable to parse the command line correctly.

import_template

21—Occurs if one of the templates has an OMS version specified in it that does not match the version of the OMS you are importing it into, and there are no other errors.

22—Occurs if one of the template files cannot be parsed, and there are no other errors.

99—More than one of the templates to be imported had errors during processing.

223—Unable to parse command line correctly, or an exception was thrown during SQL handling.

245—There is a problem reading in the file, or it does not exist.

modify_aggregate_service

1—Target does not exist.

2—Target exists.

modify_group

1—Group X does not exist.

2—Cannot add target X to typed group of base type Y.

3—Group X contains itself as a sub-group at some level.

219—Current user does not have sufficient privileges to perform this action:

Current user does not have privilege X over all member targets. Current user does not have sufficient privileges on target X to add it to the group.

220—Target X does not exist.

223—Unable to parse command line correctly. Group type is invalid.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

modify_red_group

0—Redundancy Group ""<red_group_name>" modified successfully.

1—Redundancy Group ""<red_group_name>:<red_group_type>" does not exist.

2—Cannot add target "<member_target_type>" to typed group of base type "<red_group_type>".

4—Redundancy Group Type "<red_group_type>" is invalid.

218—Redundancy Group "<red_group_name>:<red_group_type>" is currently in the process of being deleted.

220—Target "<member_target_name>:<member_target_type>" does not exist.

223—Redundancy Group name "<red_group_name>" is not valid. It may contain only alphanumeric characters, multi-byte characters, a space, "-", "_", ".", ":", and have a maximum length of 256 characters.

223—User name "<owner>" is not valid. It must begin with an alphabetic character, contain only alphanumeric characters, underscores (\"_\"), or periods (\".\"), and have a maximum length of 256 characters.

223—Invalid value for parameter "add_targets": "<add_targets>". Reason: "<add_targets>" is not a name-value pair.

223—Member Targets not of same type.

223—"Generic redundancy group" does not support member of type "<member_target_type>" .

modify_role

4—Privilege is invalid or nonexistent.

5—Target specified in one of the privileges is invalid.

6—The Super Administrator privilege cannot be granted to a role.

7—Role does not exist.

8—Group specified in one of the privileges is invalid.

9—Job in privilege is invalid or nonexistent.

10—Cannot have a circular chain of role grants.

11—The specified user does not exist.

219—User is unauthorized to perform this action.

223—Unable to parse command line correctly. Invalid argument value.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

modify_system

0—System "<system_name:system_type>" modified successfully.

101—System <system_name:system_type> contains itself as a sub-system at some level.

120—Member target "<member_target_name>:<member_target_type>" does not exist.

121—System "<system_name:system_type>" does not exist.

122—Type "<system_type>" is not a valid System type.

219—Current user does not have sufficient privileges on target <member_target_name> to add it to the system.

219—Current user does not have sufficient privileges to perform this action.

223—Invalid value for parameter "add_members": "<add_members>". Reason: "<add_members>" is not a name-value pair.

modify_target

8—One or more of the supplied target properties are invalid.

15—Target deletion in progress.

219—Insufficient privileges to modify target.

220—Target does not exist.

223—Unable to parse command line correctly.

File-Fed Option Errors—The errors associated with file-fed options.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

modify_user

1—Target specified in one of the privileges is invalid.

2—Group specified in one of the privileges is invalid.

3—Job specified in one of the privileges is invalid.

4—One of the specified privileges is invalid.

5—Specified user does not exist.

6—One or more roles to be granted to the new user does not exist.

218—A delete is pending against this user until all blackouts and jobs submitted by this user are stopped.

219—User has insufficient privileges to perform this operation.

223—Unable to parse command line correctly: Invalid argument value or user name is somehow invalid.

File-Fed Option Errors—The errors associated with file-fed options.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

provision

1—An Internal error occurred. Could not get an Instance of the Assignment Manager. Exception occurred when getting URN from path.

2—Could not provision. Exception occurred either in getting editable ProvisioningAssigment object, or during call to Initiate Provisioning.

3—Could not get one or more URNs. Returned if any of imageUrn, bootServerUrn, stageServerUrn, networkProfileUrn, targetUrn retrieved is null.

4—Could not create assignment state. Failed to create an AssignmentState object.

5—Could not set assignment properties. Failed to set the assignment properties in the assignment state object.

Since this verb uses the FileArgRemoteVerb, the following errors are also possible:

• This Verb posts Verb.SYNTAX_ERRNUM if a specified option/file mapping on the command line is not properly formatted.

• This Verb posts Verb.LOGIN_SYSTEM_ERRNUM if it cannot log in to the OMS.

• This Verb posts Verb.OMS_CONNECTION_SYSTEM_ERRNUM if it cannot connect to the OMS.

• This Verb posts Verb.CONFIGURATION_SYSTEM_ERRNUM if the configuration files are corrupt or inaccessible.

• This Verb posts Verb.MISSING_FILE_SYSTEM_ERRNUM if it cannot find an option value file.

• This Verb posts Verb.FILE_READ_SYSTEM_ERRNUM if it cannot read in an option value file.

• This Verb posts Verb.FILE_SYNTAX_SYSTEM_ERRNUM.

relocate_targets

0—Moved all targets from Source Agent to Destination Agent.

1—Target relocation has failed. The following errors are possible:

• SQL exception when relocating targets : <Database-specific error message>.

• Communication exception when relocating targets: < communication exception message >.

• Verb usage error:

  emcli relocate_targets
     -src_agent=<source agent target name>   -dest_agent=<dest agent target name>
      {-target_name=<name of the target to be relocated>
     - target_type=<type of the target to be relocated>}
  | {-input_file=dupTargets:<complete path to file>}
    {-force=yes}; "
  

• Errors relocating targets from Source Agent to Destination Agent:

  < error message >

  < error message >

• Exception in parsing targets from the command line argument <message>.

remove_beacon

0—Beacon removed successfully.

129—Syntax Error. The displayed message indicates which argument is syntactically incorrect.

170—Service does not exist.

173—Beacon does not exist.

225—Beacon not in monitoring beacons list.

230—Insufficient privileges.

255—Back-end error. Verb failed.

remove_service_system_assoc

0—System removed from service successfully.

129—Syntax Error. The displayed message indicates which argument is syntactically incorrect.

170—Service does not exist.

180—System does not exist.

230—Insufficient privileges.

255—Back-end error. Verb failed.

retry_job

1—Cannot restart job of a non-restartable type.

2—Specified job execution does not exist or has not failed.

3—The specified job execution has already been restarted and failed on restart.

219—User has insufficient privileges to perform this operation.

223—Unable to parse command line correctly.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

set_availability

0—Availability set successfully.

129—Syntax Error. The displayed message indicates which argument is syntactically incorrect.

170—Service does not exist.

180—No system defined.

181—No key tests defined.

182—No key beacons defined.

230—Insufficient privileges.

231—Availability not changed.

255—Back-end error. Verb failed.

set_credential

1—Target type does not exist.

2—Target (of given target type) does not exist.

3—Credential set does not exist.

4—Insufficient privileges.

5—Credential column does not exist.

6—Credential column number mismatch.

set_key_beacons_tests

0—Key beacons and tests set successfully.

129—Syntax Error. The displayed message indicates which argument is syntactically incorrect.

135—Must specify at least one key beacon and test.

170—Service does not exist.

173—Beacon does not exist.

175—Beacon not in list of monitoring beacons.

230—Insufficient privileges.

255—Back-end error. Verb failed.

set_metric_promotion

0—SUCCESS

223—SYNTAX_ERRNUM: Input is malformed.

255—VERB_FAILED_ERRNUM: Back-end validation fails.

set_properties

0—Properties set successfully.

129—Syntax Error. The displayed message indicates which argument is syntactically incorrect.

132—Invalid property.

133—Invalid property value.

170—Service does not exist.

173—Beacon does not exist.

175—Beacon not in list of monitoring beacons.

230—Insufficient privileges.

255—Back-end error. Verb failed.

setup

1—The Verb cannot establish a configuration area, or a corrupt area already exists.

2—A connection with the OMS cannot be established.

3—The login with the provided credentials fails at the OMS.

4—The supplied "url" option is malformed or is not http/https.

5—The configuration directory is not local as determined by the user in non-trustall HTTPS mode.

6—The Verb cannot collect the user password safely.

7—License is not been accepted by the user.

223—Unable to parse command line correctly.

stop_blackout

1—Blackout X created by user Y does not exist.

2—The blackout has already ended or stopped.

3—Agent-side blackouts cannot be edited or stopped.

218—The start of the blackout is currently being processed.

The blackout is already pending stop.

The last set of edits to the blackout have not yet been committed.

219—You (X) do not have the Super Administrator privilege needed to stop, delete, or modify blackout Y created by user Z.

Only the blackout owner can stop, delete, or modify the blackout.

Current user does not have OPERATOR privilege over all blackout targets.

223—Unable to parse command line correctly.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

stop_job

1—Specified job is invalid or non-existent.219—User has insufficient privileges to perform this operation.223—Unable to parse command line correctly.OMS Connection Errors—The errors associated with connecting to the executing OMS.

submit_job

1—Supplied job type is invalid or non-existent.

2—Job with the same name already exists.

3—One or more specified targets are invalid.

4—Missing job parameter.

5—Invalid job parameters, possibly including the security parameters such as "pwd".

217—Specified job schedule is invalid.

219—User has insufficient privileges to perform this operation.

223—Unable to parse command line correctly.

Invalid argument value.

File-Fed Option Errors—The errors associated with file-fed options.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

subscribeto_rule

1—Rule with name X and owner Y does not exist.2—EM user X does not exist.3—EM user X has no email addresses set up (see console tab Preferences->General).4—Outgoing Mail (SMTP) Server not set up (see console tab Setup->Notification Methods).219—You (X) do not have the SUPER_USER or MANAGE_ANY_ USER privilege needed to add email addresses for user Y.You (X) do not have the SUPER_USER or MANAGE_ANY_ USER privilege needed to subscribe Y to the rule owned by Z.223—Unable to parse command line correctly.

Invalid argument value.

OMS Connection Errors—The errors associated with connecting to the executing OMS.

sync

1—The Verb cannot establish a configuration area or a corrupt area already exists.

2—A connection with the OMS cannot be established.

3—The login with the provided credentials fails at the OMS.

4—The license has not been accepted by the current user.

223—Unable to parse the command line correctly.

sync_beacon

0—Beacon synced successfully.

129—Syntax Error. The displayed message indicates which argument is syntactically incorrect.

170—Service does not exist.

173—Beacon does not exist.

175—Beacon not in list of monitoring beacons.

230—Insufficient privileges.

255—Back-end error. Verb failed.

update_password

4—Target (of given target type) does not exist.

5—Credential type does not exist for given target.

6—Key value (that is, user name) does not exist.

7—Non-operator cannot change credentials.

8—Wrong value for old password.

9—Old and new passwords match.

10—No such non_key_column name.