WebSphere Process Server messages     Operating Systems: All supported
CWLSP2000E: The bus "{0}" could not be found.
Explanation: The bus name that was supplied to the command could not be resolved to a Bus object.
User Action: Ensure that you used the correct spelling for the name, and that a Bus with that name exists in the configuration.

 

CWLSP2001E: The server "{1}" could not be found on node "{0}".
Explanation: The node and server names that were supplied to the command could not be used to resolve a Server object.
User Action: Ensure that you used the correct spelling for the node and server names, and that the Server exists in the configuration.

 

CWLSP2002E: A messaging engine for bus "{0}" could not be found on server "{1}".
Explanation: The old bus and server names that were supplied to the command could not be used to resolve a messaging engine object.
User Action: Ensure that you used the correct spelling for the old bus and server names, and that the server is a member of the old bus.

 

CWLSP2003E: The cluster "{0}" could not be found.
Explanation: The cluster name that were supplied to the command could not be used to resolve a Cluster object.
User Action: Ensure that you used the correct spelling for the cluster name, and that the Cluster exists in the configuration.

 

CWLSP2004E: The server "{1}" on node "{0}" is not a member of the cluster "{2}".
Explanation: The node and server supplied to the command do not correspond to a member of the cluster supplied.
User Action: Ensure that you used the correct spelling for the node, server and cluster name, and that the server is a member of the cluster.

 

CWLSP2005E: The cluster "{0}" is already a member of bus "{1}". Messaging engine migration is not supported in this scenario.
Explanation: To migrate a server messaging engine to a cluster, the cluster cannot be a member of the same bus already.
User Action: Ensure that the cluster is not a member of the same bus to which the server belongs.

 

CWLSP2006E: The server "{1}" on node "{0}" is not a member of the bus "{2}".
Explanation: The node and server supplied to the command do not correspond to a member of the bus supplied.
User Action: Ensure that you used the correct spelling for the node, server and bus name, and that the server is a member of the bus.

 

CWLSP2007E: No messaging engine names available for cluster.
Explanation: A suitable messaging engine name could not be created.
User Action: Try specifying different configuration data when creating the messaging engine.

 

CWLSP2008E: Incorrect parameter combination supplied : node name = "{0}", server name = "{1}", cluster name = "{2}".
Explanation: The parameters supplied do not provide a valid bus member configuration.
User Action: To correctly identify a bus member, specify node name and server name, or cluster name.

 

CWLSP2009E: Server supplied does not have a SIB Service.
Explanation: An exception occurred retrieving the SIB Services for the messaging server.
User Action: Ensure that a SIB Service exists for the messaging server.

 

CWLSP2010E: Scope specification is not valid.
Explanation: The details specified do not represent a valid scope specification.
User Action: Make sure that valid node name, server name and cluster name details are used to represent the scope.

 


Reference topic

Terms of use | Feedback

Timestamp icon Last updated: 9 June 2009