Explanation | When the targetObject tag is allowed, the targetObjectType tag needs to be set in the CommandMetadata class. If the targetObject tag is not allowed, then command provider needs to set the targetObjectAllowed flag to false in the admin-command-def.xml file. |
Action | Set the targetObjectType tag in the CommandMetadata class within the admin-command-def.xml file. |
Explanation | One or more required parameters for the command is missing. |
Action | Set all of the required parameters. |
Explanation | The parameter value is not valid. |
Action | A valid value is needed for the parameter. |
Explanation | The specified parameter name is not valid. |
Action | See the information center to determine the correct parameter name. |
Explanation | The specified command or command group name is not valid. |
Action | Verify that the specified command or command group name is correct. |
Explanation | The step name is not valid for the specified command. |
Action | Verify that the specified step, command or command group name is correct. |
Explanation | This command requires a target object. |
Action | Specify the target object for the command. |
Explanation | Command Framework failed to initialize itself or cannot create CommandMgr in client, server or local mode. |
Action | Check the call stack for root cause. |
Explanation | The parameter value is not valid. |
Action | A valid value is needed for the parameter. |
Explanation | User does not have the correct authority to run the command. |
Action | Make sure user has correct authority or security role to perform the command. |