Problem | 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. |
Problem | See message contents for details. |
User response | Ensure that the service name is specified correctly and that the service has been deployed. |
Problem | See message contents for details. |
User response | Ensure that the service name is specified correctly and that the service has been deployed. |
Problem | The endpoint listener has been started. |
User response | No action required. |
Problem | The JAXRPC Handler List has not been defined. |
User response | Configure a JAXRPC Handler List |
Problem | The JAXRPC Handler has not been defined. |
User response | Configure a JAXRPC Handler |
Problem | The class defined could not be loaded. |
User response | Create the JAXRPC Handler class. |
Problem | A JAXRPC Handler class must implement javax.xml.rpc.handler.Handler. |
User response | Correct the handler class and recompile it. |
Problem | The specified WSDL does not contain any services. |
User response | Ensure that the WSDL reference contains at least one service. |
Problem | 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/. |
Problem | Extra information was received from an unexpected source. |
User response | No action required. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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. |
Problem | 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/. |
Problem | 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/. |
Problem | A JAXRPC Handler must be implemented by a handler class. |
User response | Configure the handler to reference a JAXRPC handler class. |
Problem | 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/. |
Problem | The WSDL must be well formed. |
User response | Ensure that the WSDL is well formed. |
Problem | 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/. |
Problem | The configured destination must be available. |
User response | Ensure that the destination is correctly configured and available. |
Problem | The WSDL could not be found. |
User response | Reload the WSDL. |
Problem | There is more than one service defined in the WSDL. |
User response | Specify a WSDLServiceName for the SIBWSWSDLLocation for this inbound service. |
Problem | The WSDL for this inbound service must exist. |
User response | Ensure that the WSDL is available. |
Problem | See exception contents for details. |
User response | Ensure that the WSDL is well formed. |
Problem | The WSDL could not be found. |
User response | Reload the WSDL. |
Problem | See exception contents for details. |
User response | Ensure that the authentication information is available. |
Problem | A WSDL Service must exist which matches the outbound service. |
User response | Ensure that the service has been defined in the WSDL. |
Problem | 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/. |
Problem | You have not configured the WSDLLocation in the SIBWSWSDLLocation. |
User response | Ensure that the WSDLLocation has been configured. |
Problem | You have not configured a value, so the default will be used. |
User response | No action required. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | =A WSDL Service must exist which matches the inbound service. |
User response | Ensure that the service has been defined in the WSDL. |
Problem | The WSDL Service must contain the template port. |
User response | Ensure that the service contains the template port. |
Problem | A WSDL Service must contain at least one port. |
User response | Ensure that the service contains at least one port. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | The WS-Security binding specified could not be found. |
User response | Ensure that the WS-Security binding exists, and that it matches the WS-Security version of the WS-Security configuration defined on the port. |
Problem | A WS-Security binding or bindings matching the WS-Security configuration could not be found. |
User response | Ensure that the WS-Security binding or bindings have been properly defined, that at least one WS-Security binding is specified, and that they match the WS-Security version of the WS-Security configuration defined on the port. |
Problem | A WS-Security configuration and bindings could not be applied to the port. |
User response | Ensure that the WS-Security configuration and binding objects defined on the port are valid, and that the WS-Security configuration and bindings are of the same version. |
Problem | The specified WS-Security configuration could not be found. |
User response | Ensure that the WS-Security configuration has been properly defined. |
Problem | This exception is unexpected. The cause is not immediately known. |
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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | The specified service was not found within the service WSDL. |
User response | Ensure the specified service is defined within the service WSDL. |
Problem | A unique service could not be identified within the service WSDL. |
User response | Specify the required service within the service WSDL. |
Problem | The specified port is not defined for the service. |
User response | Ensure a valid port name is supplied. |
Problem | The specified parameters are not a valid combination. |
User response | Consult the user documentation for valid parameter combinations. |
Problem | The specified endpoint listener does not exist. |
User response | Ensure a valid endpoint listener name and location is specified. |
Problem | 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/. |
Problem | 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/. |
Problem | 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 |
Problem | Inbound ports still exist that reference the endpoint listener. |
User response | Remove all inbound ports that reference the endpoint listener. |
Problem | 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/. |
Problem | No WSDL location configuration has been defined for the named object. |
User response | Ensure that a valid WSDL location configuration exists. |
Problem | 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. |
Problem | The specified UDDI publication information does not exist. |
User response | Ensure that the service configuration contains the named UDDI publication. |
Problem | 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. |
Problem | 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. |
Problem | This WSDL port has already been configured for the outbound service. |
User response | Each port can only be configured once for an outbound service. |
Problem | An inbound port with the specified name already exists. |
User response | Ensure the name of the inbound port is unique within the inbound service. |
Problem | An endpoint listener with the specified name already exists. |
User response | Ensure the name of the endpoint listener is unique within the server. |
Problem | 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. |
Problem | 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/. |
Problem | 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. |
Problem | 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. |
Problem | 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/. |
Problem | The inbound service with these details was published successfully. |
User response | No action required. |
Problem | 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. |
Problem | 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/. |
Problem | 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. |
Problem | The inbound service with these details was successfully removed from the registry. |
User response | No action required. |
Problem | 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. |
Problem | 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/. |
Problem | The destination was not found. |
User response | Ensure the required destination exists. |
Problem | The WSDL service contained no port definitions. |
User response | Ensure the WSDL service contains at least one port definition. |
Problem | There are either no servers configured or no deployment manager can be found for the configured servers. |
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/. |
Problem | The module information for an installed module was requested but it did not contain a module to server mapping. |
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/. |
Problem | No activation spec or JMS listener port matches the specified JMS destination information. |
User response | Ensure that JMS resources are correctly configured. |
Problem | A previously installed application exists for the endpoint listener. |
User response | Uninstall the existing application to allow the new endpoint listener application to be installed. |
Problem | The specified protocol is not supported. |
User response | Ensure that a supported protocol is specified. |
Problem | The endpoint application EAR file does not contain a suitable endpoint module. |
User response | Ensure that a valid endpoint application EAR file is used. |
Problem | A correctly configured SDO repository could not be located. |
User response | Ensure that all documented steps for configuring the SDO repository have been carried out correctly. |
Problem | The value supplied for the parameter is not valid. One possible reason is that the value contains illegal charcaters. |
User response | Ensure that the value supplied is valid. |
Problem | The node, server or cluster does not exist. |
User response | Ensure that the node/server or cluster is specified correctly. |
Problem | Installing the application |
User response | No action required |
Problem | An unknown error has occurred when installing the application |
User response | See messages for more information |
Problem | The application has installed successfully |
User response | No action required |
Problem | The application is being started |
User response | No action required |
Problem | An unknown error has occurred when starting the application |
User response | See messages for more information |
Problem | The application has started |
User response | No action required |
Problem | Installing the resource adapter |
User response | No action required |
Problem | An unknown error occurred installing resource adapter |
User response | See messages for more information |
Problem | The resource adapter has started successfully |
User response | No action required |
Problem | The activation specification required by the resource adapter is being created |
User response | No action required |
Problem | The configuration is being saved |
User response | No action required |
Problem | An unknown error occurred saving the configuration |
User response | See messages for more information |
Problem | An unknown error occurred creating the activation specification |
User response | See messages for more information |
Problem | An unknown command was specified |
User response | Use a valid command when running the script |
Problem | 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. |
Problem | 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. |
Problem | The application specified has already been installed. |
User response | No action required. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |