Explanation | An attempt was made to remove a user from the bus connector role when the user was not in that role. |
Action | Retry specifying a user that is in the bus connector role. |
Explanation | An attempt was made to remove a group from the bus connector role when the group was not in that role. |
Action | Retry specifying a group that is in the bus connector role. |
Explanation | A valid role name must be supplied. |
Action | Supply a role name of sender, receiver, browser, creator or identityAdopter. |
Explanation | The inheritDefaults permission applies only to destinations in the local namespace. |
Action | Do not set the inheritDefaults parameter to true when the destination is a foreign destination. |
Explanation | The queue name supplied to the command could not be located. |
Action | Ensure a valid queue name is supplied. |
Explanation | The Web service name supplied to the command could not be located. |
Action | Ensure a valid Web service name is supplied. |
Explanation | The port name supplied to the command could not be located. |
Action | Ensure a valid port name is supplied. |
Explanation | The alias name supplied to the command could not be located. |
Action | Ensure a valid alias name is supplied. |
Explanation | A valid type name must be supplied. |
Action | Supply a role name of queue, port, webService, topicSpace or alias. |
Explanation | A foreignBus parameter must be specified when the type parameter is set to foreignDestination. |
Action | Ensure the foreignBus parameter is supplied. |
Explanation | The foreign destination specified could not be located. |
Action | Make sure that valid bus and destination parameters are supplied to the command. |
Explanation | The user specified could not be located in the default authority role list. |
Action | Check that the user has a defined role in the default authority role list. |
Explanation | The group specified could not be located in the default authority role list. |
Action | Check that the group has a defined role in the default authority role list. |
Explanation | The user specified could not be located in the role list for the specified destination. |
Action | Check that the user has a defined role in the destination role list. |
Explanation | The group specified could not be located in the destination role list. |
Action | Check that the group has a defined role in the destination role list. |
Explanation | The foreign bus name supplied to the command could not be located. |
Action | Make sure that a valid foreign bus name is supplied. |
Explanation | The user specified could not be located in the foreign bus administrative domain. |
Action | Check that the user has a defined role for the foreign bus. |
Explanation | The group specified could not be located in the foreign bus administrative domain. |
Action | Check that the group has a defined role for the foreign bus. |
Explanation | The user specified could not be located in the bus administrative domain. |
Action | Check that the user has a defined role on the bus. |
Explanation | The group specified could not be located in the bus administrative domain. |
Action | Check that the group has a defined role on the bus. |
Explanation | The topic space name supplied to the command could not be located. |
Action | Make sure that a valid topic space name is supplied. |
Explanation | A valid role name must be supplied. |
Action | Supply a valid role name. Possiblities include sender, receiver, browser, creator and identityAdopter. |
Explanation | The topic name supplied to the command could not be located. |
Action | Make sure that a valid topic name is supplied. |
Explanation | The user specified could not be located in the topicspace security administrative domain. |
Action | Check that the user has a defined role in the topicspace. |
Explanation | The group specified could not be located in the topicspace security administrative domain. |
Action | Check that the group has a defined role in the topicspace. |
Explanation | A valid role name must be supplied. Allowable role names for a topic space destination are sender, receiver and identityAdopter. |
Action | Supply a valid role name. |
Explanation | A valid role name must be supplied. Allowable role names for an alias destination are sender, receiver, browser and identityAdopter. |
Action | Supply a valid role name. |
Explanation | A valid role name must be supplied. Allowable role names for a foreign destination are sender and identityAdopter. |
Action | Supply a valid role name. |
Explanation | A valid role name must be supplied. Allowable role names when configuring foreign bus permissions are sender and identityAdopter. |
Action | Supply a valid role name. |
Explanation | A valid role name must be supplied. Allowable role names when configuring topic space permissions are sender, receiver and identityAdopter. |
Action | Supply a valid role name. |
Explanation | A valid role name must be supplied. Allowable role names when configuring topic permissions are sender, receiver and identityAdopter. |
Action | Supply a valid role name. |
Explanation | The specified bus name could not be located within the administrative domain. |
Action | Make sure that the bus name specified is a valid bus name for an existing bus. |
Explanation | An AdminTask command is trying to work with a process that is not connected to a server that has a running configuration service. |
Action | Reissue the command on a process that is connected to a server that has a running configuration service. For example a deployment manager, managed server or unmanaged server. |
Explanation | When bus security is enabled, the Server group is not permitted in the bus connector role if the bus contains WebSphere Application Server Version 6.0 bus members. |
Action | Disable security on the named bus, or choose a different group name, or remove all pre-Version 6.1 nodes from the bus. |
Explanation | The user name and unique name specified on the command conflict with an existing user. |
Action | Retry the command using the user name and unique name that is not already in the policy. |
Explanation | An attempt was made to change a users authority, but the user information provided matches multiple users. |
Action | Retry the command using the correct user name and unique name. |
Explanation | The group name and unique name specified on the command conflict with an existing group. |
Action | Retry the command using the group name and unique name that is not already in the policy. |
Explanation | An attempt was made to change a groups authority, but the group information provided matches multiple groups. |
Action | Retry the command using the correct group name and unique name. |
Explanation | The command invoked did not specify the user or the uniqueName argument. At least one of these must be specified. |
Action | Rerun the command specifying the user or uniqueName argument. |
Explanation | The command invoked did not specify the group or the uniqueName argument. At least one of these must be specified. |
Action | Rerun the command specifying the group or uniqueName argument. |