WebSphere Process Server messages     Operating Systems: All supported

CWSAD

CWSAD0001E: The ServiceIndexReader class created an IOException or a SAXException error when it read the {0} file.
Problem An IOException or SAXException error is created when the file is read.
User response Ensure that the file exists and that it is usable.
CWSAD0002E: The ServiceIndexWriter class created an IOException when it writes to the {0} file.
Problem An IOException is created when ServiceIndexWriter class writes to the file.
User response Ensure that the hard disk is not full and you have the writable permission.
CWSAD0003E: The administrative command cannot find {0} application.
Problem The application name cannot be found.
User response Provide the correct application name.
CWSAD0004E: The administrative command cannot find {0} module.
Problem The module cannot be found in the application package.
User response Provide the correct module name for the application package.
CWSAD0005E: The administrative command cannot find {0} Web service.
Problem The Web services cannot be found in the module.
User response Ensure that the module has a Web service and that the service name is correct.
CWSAD0006E: The administrative command cannot find {0} logical endpoint.
Problem The specified logical endpoint cannot be found in the serivce.
User response Provide a logical endpoint name.
CWSAD0008E: The administrative command found multiple services index files for {0} application and {1} module.
Problem Multiple services index files were found when only one service index file is expected.
User response This is an internal error, no user action is required.
CWSAD0009E: There is no Web service in the {0} services index file.
Problem The services index file has no entry for a Web service. The file might not be usable.
User response If the file was manually modified, uninstall and reinstall the application. If this was an internal error, check the servicesIndex.xml and follow the usual steps of debugging errors with the product.
CWSAD0010E: There is no logical endpoint in {0} service.
Problem The services index file has no entry for a logical endpoint. The file might not be usable.
User response If the file was manually modified, uninstall and reinstall the application. If this was an internal error, check the servicesIndex.xml and follow the usual steps of debugging errors with the product.
CWSAD0011E: There is no operation for the {0} logical endpoint.
Problem The services index file has no operation for the endpoint. The file might not be usable.
User response If the file was manually modified, uninstall and reinstall the application. If this was an internal error, check the servicesIndex.xml and follow the usual steps of debugging errors with the product.
CWSAD0012E: The {0} file name that is provided cannot be used.
Problem The file name must not contain slashes, directory or path name.
User response Provide the correct file name without the slashes, directory or path name.
CWSAD0013E: The specified {0} file name cannot be found.
Problem The specified file name cannot be located in the configuration repository.
User response Provide the correct file name that can be found in the repository.
CWSAD0014E: The node has not been added because the version of the Feature Pack for Web Services that is installed on the {0} deployment manager is earlier than the version that is installed on {1} node.
Problem The version of the Feature Pack for Web Services that is installed on the deployment manager node must be at the same level or higher than the version that is installed on the node.
User response Install the same version or a higher version of the Feature Pack for Web Services on the deployment manager node before running the addNode command.
CWSAD0015E: The node has not been added because the Feature Pack for Web Services is installed on the {0} node and not on the deployment manager node.
Problem The Feature Pack for Web Services is not installed on the deployment manager node but has been installed on the managed node.
User response Install the same level or a higher version of the Feature Pack for Web Services on the deployment manager node before attempting to add the managed node.
CWSAD0016W: The target {0} module on {1} node cannot be reached because the module and the node require the Feature Pack for Web Services.
Problem The module contains JAXWS Web Services that is required for the Feature Pack for Web Services.
User response Install the Feature Pack for Web Services on the target node.
CWSAD0017E: The node has not been added because the Feature Pack for Web Services is installed on the deployment manager node and the {0} node is prior to the WAS 6.1 level.
Problem The Feature Pack for Web Services is installed on the deployment manager node but the managed node is prior to the WAS 6.1 level.
User response Install the same level of the Feature Pack for Web Services on the managed node or upgrade it to the WAS 6.1 level before attempting to add the managed node.
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.webservices.admin.resources.websvcsAdmin.html

© Copyright IBM Corporation 2006, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)