S Service Integration Bus - Web Services messages

CWSWS0101E: Error retrieving port from service {1} in the WSDL.
Explanation: An error occurred retrieving the port from the service in the WSDL.
User Response: Ensure that the service name is specified correctly and that the service has been deployed.

CWSWS0102E: The following exception occurred retrieving service {0}
Explanation: See message contents for details.
User Response: Ensure that the service name is specified correctly and that the service has been deployed.

CWSWS0103E: The following exception occurred while retrieving service definition from URL: {0}. Exception: {1}
Explanation: See message contents for details.
User Response: Ensure that the service name is specified correctly and that the service has been deployed.

CWSWS1001I: Endpoint Listener {0} started.
Explanation: The endpoint listener has been started.
User Response: No action required.

CWSWS1002E: JAXRPC Handler List {0} is not defined.
Explanation: The JAXRPC Handler List has not been defined.
User Response: Configure a JAXRPC Handler List

CWSWS1003E: JAXRPC Handler {0} referenced in Handler List {1} is not defined.
Explanation: The JAXRPC Handler has not been defined.
User Response: Configure a JAXRPC Handler

CWSWS1004E: JAXRPC Handler {0} missing handler class {1}
Explanation: The class defined could not be loaded.
User Response: Create the JAXRPC Handler class.

CWSWS1005E: JAXRPC Handler {0} handler class {1} does not implement javax.xml.rpc.handler.Handler
Explanation: A JAXRPC Handler class must implement javax.xml.rpc.handler.Handler.
User Response: Correct the handler class and recompile it.

CWSWS1006E: The WSDL for inbound service {0} associated with the service integration bus {1} does not contain any services.
Explanation: The specified WSDL does not contain any services.
User Response: Ensure that the WSDL reference contains at least one service.

CWSWS1007E: The following exception occurred: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS1008W: A report message with feedback code {0} was received.
Explanation: Extra information was received from an unexpected source.
User Response: No action required.

CWSWS1009E: The following exception occurred while restoring WSDL {0}
Explanation: The WSDL could not be restored.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS1010E: The following exception occurred while processing response {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS1011E: The following exception occurred while processing request {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS1012E: A required file is missing. The file {0} must exist. Exception thrown is {1}
Explanation: The file described is required. The file will be created the first time you create an object of a type stored in that file.
User Response: Use either the administrative console or the command line scripting tool to create the required object and file.

CWSWS1013E: The following exception occurred while storing WS-Security {0}
Explanation: The WS-Security object could not be stored, see the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS1014E: The following exception occurred while loading WS-Security: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS1015E: JAXRPC Handler {0} does not specify a class.
Explanation: A JAXRPC Handler must be implemented by a handler class.
User Response: Configure the handler to reference a JAXRPC handler class.

CWSWS1016E: The following exception occurred while storing WSDL for {0}: {1}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS1017E: Can not retrieve WSDL from the malformed URL {0}
Explanation: The WSDL must be well formed.
User Response: Ensure that the WSDL is well formed.

CWSWS1018E: The following exception occurred while configuring port {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS1019E: Unable to resolve destination {0}: {1}
Explanation: The configured destination must be available.
User Response: Ensure that the destination is correctly configured and available.

CWSWS1020E: No WSDL defined for key {0}.
Explanation: The WSDL could not be found.
User Response: Reload the WSDL.

CWSWS1021E: Unable to determine WSDL service for inbound service {0} associated with service integration bus {1}.
Explanation: There is more than one service defined in the WSDL.
User Response: Specify a WSDLServiceName for the SIBWSWSDLLocation for this inbound service.

CWSWS1022E: The following exception occurred while retrieving WSDL to configure the inbound service {0} associated with service integration bus {1}: {2}
Explanation: The WSDL for this inbound service must exist.
User Response: Ensure that the WSDL is available.

CWSWS1023E: The following exception occurred while processing imports for the WSDL defined to the inbound service {0} associated with service integration bus {1}: {2}
Explanation: See exception contents for details.
User Response: Ensure that the WSDL is well formed.

CWSWS1024E: The following exception occurred while retrieving WSDL defined for key {0}: {1}
Explanation: The WSDL could not be found.
User Response: Reload the WSDL.

CWSWS1025E: The following exception occurred while retrieving authentication information: {0}
Explanation: See exception contents for details.
User Response: Ensure that the authentication information is available.

CWSWS1026E: WSDL Service {0} is not defined in the outbound service {1} associated with service integration bus {2}.
Explanation: A WSDL Service must exist which matches the outbound service.
User Response: Ensure that the service has been defined in the WSDL.

CWSWS1027E: The following exception occurred while retrieving WSDL from {0}: {1}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS1028E: No WSDL defined.
Explanation: You have not configured the WSDLLocation in the SIBWSWSDLLocation.
User Response: Ensure that the WSDLLocation has been configured.

CWSWS1029W: The property {0} for service integration bus {1} is not set on the endpoint listener {2}. Defaulting to {3}.
Explanation: You have not configured a value, so the default will be used.
User Response: No action required.

CWSWS1030W: Received unexpected response message {0}.
Explanation: See the message contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS1031E: The following exception occurred while processing messages in endpoint listener {0} associated with service integration bus {1}: {2}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS1032E: The following exception occurred while sending messages in endpoint listener {0} associated with service integration bus {1} to destination {2}: {3}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS1033E: Message timed out awaiting response.
Explanation: A response was not received within the configured time limits.
User Response: Ensure that the target destination is configured correctly and available. If the problem persists, contact your IBM representative.

CWSWS1034E: The following exception occurred while connecting to the service integration bus {0}. {1}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS1035E: The following exception occurred while resolving the reply destination {0}. {1}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS1036E: The following exception occurred while connecting to the service integration bus {0}. {1}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS1037E: The following exception occurred while connecting the consumer session to the reply destination {0}. {1}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS1038E: Failed to start endpoint listener {0} associated with the service integration bus {1}, due to exception {2}.
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS1039E: The following exception occurred while performing operation level security check. {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS1040E: The following exception occurred while performing operation level security check on method {0}. {1}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS1041E: The template WSDL service {0} defined in the inbound service {1} associated with service integration bus {2} cannot be found in the template WSDL.
Explanation: =A WSDL Service must exist which matches the inbound service.
User Response: Ensure that the service has been defined in the WSDL.

CWSWS1042E: The template WSDL port {0} defined in the inbound port {1} for inbound service {2} associated with service integration bus {3} cannot be found in the template WSDL.
Explanation: The WSDL Service must contain the template port.
User Response: Ensure that the service contains the template port.

CWSWS1043E: For the template WSDL service {0} defined in the inbound service {1} associated with service integration bus {2}, the template WSDL does not contain any ports or the ports do not have a portType.
Explanation: A WSDL Service must contain at least one port.
User Response: Ensure that the service contains at least one port.

CWSWS1044E: A serious error occurred before the request could be fully processed.
Explanation: An exception occurred and the request was discarded before it could be fully processed.
User Response: Try sending the request again or ask the system administrator what the problem is.

CWSWS1045E: The request timed out before it could be fully processed.
Explanation: The request timed out and was discarded before it could be fully processed.
User Response: Try sending the request again or ask the system administrator what the problem is.

CWSWS1046E: Failed to insert context into request message.
Explanation: The current execution context could not be inserted into the request message.
User Response: Examine the FFDC logs for the original cause of the failure.

CWSWS1047E: Failed to insert context into response message.
Explanation: The current execution context could not be inserted into the response message.
User Response: Examine the FFDC logs for the original cause of the failure.

CWSWS3000E: Message type not supported: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3001E: The following exception occurred in ''Call.invoke()'': {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3002E: The following exception occurred getting DataGraph from request message: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3003E: The following exception occurred creating reply SIBusSdoMessage: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3004E: The following exception occurred in Service createCall: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3005E: The following exception occurred creating Service: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3006E: Destination ''{0}'' has not been configured with the ProtocolInvokerFactory property: {1}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3007E: Factory name is null
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3008E: Factory class not found: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3009E: Failed to instantiate factory class {0}, due to exception {1}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3010E: The following exception occurred getting operation name from request message: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3011E: The following exception occurred getting message property {0} : {1}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3012E: Cannot invoke SOAP service, RequestConfiguration is null
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3013E: Unable to produce format string due to exception {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3014E: Failed to get information from request configuration due to exception {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3015E: The following exception occurred getting DataMediator for format {0} : {1}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3016E: Failed to write SOAP message to buffer, due to exception {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3017E: Failed to successfully invoke SOAP service due to exception {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3018E: Failed to read SOAP message into buffer, due to exception {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3019E: Target endpoint protocol not supported: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3020E: The following exception occurred creating WSIFServiceProvider: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3021E: Operation arguments have not been set
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3022E: The following exception occurred converting objects to DataGraph: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3023E: Parameter does not represent a fault
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3024E: The following exception occurred getting unique ID root from SICoreConnection: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3025E: Cannot make exception reply for message class: {0}
Explanation: This exception would normally be returned in a reply message, which is not possible. See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3026E: DataMediator {0} is unusable for making an exception reply, the exception is {1}
Explanation: This exception would normally be returned in a reply message, which is not possible. See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3027E: The following exception occurred creating message from fault DataGraph: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3028E: The following exception occurred getting SOAP envelope: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3029E: The following exception occurred writing SOAP fault message envelope to buffer: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3030E: The following exception occurred getting DataGraph from SOAPDataMediator: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3031E: The following exception occurred creating DataGraph for fault: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3032E: Unable to create exception reply, format string is null
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3033E: Unable to create exception reply, operation name from request is null
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3034E: Expecting wsdlLocation to start with ''file:'' : {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3035E: Unable to read WSDL from location: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3036E: The following exception occurred getting SDO repository output stream: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3037E: The following exception occurred copying WSDL to SDO repository: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3038E: The following exception occurred while sending request: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3039E: The following exception occurred while receiving reply: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3040E: Reply message was not received
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3041E: Reply message type: {0} is not an SIBusSdoMessage
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3042E: The following exception occurred creating SIBusSdoMessage: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3043E: The following exception occurred getting DataGraph from response message: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3044E: The following exception occurred getting response fault: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3045E: The following exception occurred creating temporary replyTo destination: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3046E: The following exception occurred getting SICoreConnectionFactory: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3047E: The following exception occurred creating SICoreConnection: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3048E: The following exception occurred closing WSIFPort: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3049E: The following exception occurred getting WSIFService: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3050E: The following exception occurred mapping type on WSIFService: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3051E: The following exception occurred setting WSIFMessage part: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3052E: The following exception occurred getting host value in endpoint URL: {0} : {1}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3053E: Host ''{0}'' invalid. Must be ''{1}'' or ''{2}'' in endpoint URL: {3}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3054E: Invalid property ''{0}'' in endpoint URL: {1}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3055E: Properties ''{0}'' and ''{1}'' are mutually exclusive in endpoint URL: {2}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3056E: Property ''{0}'' must be specified when host is {1} in endpoint URL: {2}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3057E: Property ''{0}'' must be specified with property ''{1}'' in endpoint URL: {2}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3058E: Invalid value ''{0}'' for property ''{1}'' in endpoint URL: {2}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3059E: Invalid destination name ''{0}'' in property ''{1}'' in endpoint URL: {2}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3060E: The following exception occurred parsing endpoint URL: {0} : {1}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3061E: NumberFormatException parsing value of property ''{0}'' in endpoint URL: {1}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3062E: The following exception occurred getting SIDestinationAddressFactory: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3063E: The following exception occurred getting URL properties in endpoint URL: {0} : {1}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3064E: No ServiceProvider found for namespace: {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS3065E: Operation level security check failed. User is not authorized to invoke operation {0}
Explanation: See the exception contents for details.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS5001E: Service definition not found: {0}.
Explanation: The specified service was not found within the service WSDL.
User Response: Ensure the specified service is defined within the service WSDL.

CWSWS5002E: No service specified and {0} service elements defined in the service WSDL.
Explanation: A unique service could not be identified within the service WSDL.
User Response: Specify the required service within the service WSDL.

CWSWS5003E: Invalid port: {0}.
Explanation: The specified port is not defined for the service.
User Response: Ensure a valid port name is supplied.

CWSWS5004E: Invalid parameter combination: {0}.
Explanation: The specified parameters are not a valid combination.
User Response: Consult the user documentation for valid parameter combinations.

CWSWS5005E: Failed to locate endpoint listener: {0}.
Explanation: The specified endpoint listener does not exist.
User Response: Ensure a valid endpoint listener name and location is specified.

CWSWS5006W: The following exception occurred while removing inbound port reference: {0}.
Explanation: See the message description to determine the cause of the exception.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS5007E: The following exception occurred reading WSDL located at {0}: {1}.
Explanation: See the message description to determine the cause of the exception.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS5008E: No connection to service integration bus {0} found for endpoint listener {1}.
Explanation: The specified service integration bus connection does not exist for the endpoint listener.
User Response: Ensure a valid service integration bus connection for the endpoint listener is specified

CWSWS5009E: The endpoint listener is still referenced by inbound ports.
Explanation: Inbound ports still exist that reference the endpoint listener.
User Response: Remove all inbound ports that reference the endpoint listener.

CWSWS5010E: Failed to store WSDL located at {0} due to the following exception: {1}.
Explanation: An internal exception prevented a copy of the WSDL from being stored.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS5011E: No WSDL location is configured for {0}.
Explanation: No WSDL location configuration has been defined for the named object.
User Response: Ensure that a valid WSDL location configuration exists.

CWSWS5012E: No WSDL service is configured for {0}.
Explanation: The WSDL location configuration for the named object does not contain a service name or namespace.
User Response: Ensure the WSDL location configuration contains a valid service name and namespace.

CWSWS5013E: UDDI publication {0} not found for service {1}.
Explanation: The specified UDDI publication information does not exist.
User Response: Ensure that the service configuration contains the named UDDI publication.

CWSWS5014E: An inbound service named {0} already exists.
Explanation: An inbound service with the specified name already exists.
User Response: Ensure the name of the inbound service is unique within the service integration bus.

CWSWS5015E: An outbound service named {0} already exists.
Explanation: An outbound service with the specified name already exists.
User Response: Ensure the name of the outbound service is unique within the service integration bus.

CWSWS5016E: A port named {0} already exists for outbound service {1}.
Explanation: This WSDL port has already been configured for the outbound service.
User Response: Each port can only be configured once for an outbound service.

CWSWS5017E: A port named {0} already exists for inbound service {1}.
Explanation: An inbound port with the specified name already exists.
User Response: Ensure the name of the inbound port is unique within the inbound service.

CWSWS5018E: An endpoint listener named {0} already exists for server {1}.
Explanation: An endpoint listener with the specified name already exists.
User Response: Ensure the name of the endpoint listener is unique within the server.

CWSWS5019E: A connection to service integration bus {0} already exists for endpoint listener {1}.
Explanation: A connection to the specified service integration bus already exists for the endpoint listener.
User Response: Only create one connection between the endpoint listener and each required service integration bus.

CWSWS5020E: Failed to modify routing for destination {0} due to the following exception: {1}.
Explanation: See the message description to determine the cause of the exception.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS5021W: An update to UDDI has been performed. The configuration must be saved to ensure consistency.
Explanation: An update to UDDI has been performed and associated information has been written to the local configuration. The local configuration changes require saving to ensure consistency with UDDI.
User Response: Save the current configuration session.

CWSWS5022E: The UDDI publication command failed for the publication named {0} in inbound service {1} on service integration bus {2}: No ports found
Explanation: An inbound service cannot be published to UDDI unless it has at least one port.
User Response: Add a port to the inbound service and publish it again.

CWSWS5023E: The UDDI publication command for the publication named {0} in inbound service {1} on service integration bus {2} failed with this exception: {3}
Explanation: See the message description to determine the cause of the exception.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS5024I: The publication named {0} in inbound service {1} on service integration bus {2} was published to UDDI registry {3} and has service key {4}
Explanation: The inbound service with these details was published successfully.
User Response: No action required.

CWSWS5025E: The delete UDDI service command failed for the publication named {0} in inbound service {1} on service integration bus {2}. No service key found
Explanation: A service cannot be deleted from a UDDI registry unless its service key is known, and no service key was set in the publication object.
User Response: Publish the service or delete the named UDDIPublication object before re-issuing the command.

CWSWS5026E: The delete UDDI service command for the publication named {0} in inbound service {1} on service integration bus {2} failed with this exception: {3}
Explanation: See the message description to determine the cause of the exception.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS5027W: The delete UDDI service command for the publication named {0} in inbound service {1} on service integration bus {2} failed because the service with key {3} could not be found in the UDDI registry
Explanation: The service may have been removed from the registry already. The service key is removed from the publication object and the command continues to run.
User Response: Check that the service details in the UDDI registry are correct.

CWSWS5028I: The publication named {0} in inbound service {1} on service integration bus {2} with service key {3} was removed from the UDDI registry {4}
Explanation: The inbound service with these details was successfully removed from the registry.
User Response: No action required.

CWSWS5029E: Access to the UDDI registry referenced by the UDDIReference named {0} failed with this exception: {1}
Explanation: See the message description to determine the cause of the exception.
User Response: Check, and if necessary correct, the proxy userid and password in the command if any, the URLs and authentication alias in the named UDDIReference object, and that the UDDI registry can be accessed over the network. Then rerun the command.

CWSWS5030E: The service integration bus named {0} was not found.
Explanation: The named service integration bus could not be found. The configuration may be inconsistent.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS5031E: No destination named {0} is associated with service integration bus {1}.
Explanation: The destination was not found.
User Response: Ensure the required destination exists.

CWSWS5032E: No ports are defined for WSDL service {0}.
Explanation: The WSDL service contained no port definitions.
User Response: Ensure the WSDL service contains at least one port definition.

CWSWS5050I: Installing application : {0}
Explanation: Installing the application
User Response: No action required

CWSWS5051E: Error occurred installing application : {0}
Explanation: An unknown error has occurred when installing the application
User Response: See messages for more information

CWSWS5052I: The application has installed successfully : {0}
Explanation: The application has installed successfully
User Response: No action required

CWSWS5053I: The application is being started : {0}
Explanation: The application is being started
User Response: No action required

CWSWS5054E: Error occurred starting application : {0}
Explanation: An unknown error has occurred when starting the application
User Response: See messages for more information

CWSWS5055I: The application has started : {0}
Explanation: The application has started
User Response: No action required

CWSWS5056I: Installing resource adapter : {0}
Explanation: Installing the resource adapter
User Response: No action required

CWSWS5057E: Error occurred installing resource adapter : {0}
Explanation: An unknown error occurred installing resource adapter
User Response: See messages for more information

CWSWS5058I: The resource adapter has started successfully : {0}
Explanation: The resource adapter has started successfully
User Response: No action required

CWSWS5059I: Creating activation specification : {0}
Explanation: The activation specification required by the resource adapter is being created
User Response: No action required

CWSWS5060I: Saving configuration
Explanation: The configuration is being saved
User Response: No action required

CWSWS5061E: An error occurred saving the configuration : {0}
Explanation: An unknown error occurred saving the configuration
User Response: See messages for more information

CWSWS5062E: An error occurred creating the activation specification : {0}
Explanation: An unknown error occurred creating the activation specification
User Response: See messages for more information

CWSWS5063I: An unknown command was specified : {0}
Explanation: An unknown command was specified
User Response: Use a valid command when running the script

CWSWS5064E: The INSTALL_RA option should be executed first.
Explanation: The RA adapter needs to be installed before you can install the Service Integration Bus - Web Services application.
User Response: Run the install command using the INSTALL_RA option.

CWSWS5065E: The application {0} could not be found.
Explanation: The application specified could not be found.
User Response: Check that the file exists and that you have given the correct path name. Forward slashes (/) should be used for all paths.

CWSWS5066I: The application {0} has already been installed.
Explanation: The application specified has already been installed.
User Response: No action required.

CWSWS6001E: The associated destination for {0} does not exist.
Explanation: A serious error has occurred within the configuration.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS6002E: A serious error has occurred within the configuration.
Explanation: The configuration is corrupt.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS6003E: The destination {0} does not exist in the bus {1}.
Explanation: A serious error has occurred within the configuration.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWSWS6004E: Cannot create hyperlink to destination detail panel.
Explanation: A serious error has occurred within the configuration.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.