CWSAD

CWSAD0001E: The ServiceIndexReader class created an IOException or a SAXException error when it read the {0} file.
Explanation An IOException or SAXException error is created when the file is read.
Action Ensure that the file exists and that it is usable.
CWSAD0002E: The ServiceIndexWriter class created an IOException when it writes to the {0} file.
Explanation An IOException is created when ServiceIndexWriter class writes to the file.
Action Ensure that the hard disk is not full and you have the writable permission.
CWSAD0003E: The administrative command cannot find {0} application.
Explanation The application name cannot be found.
Action Provide the correct application name.
CWSAD0004E: The administrative command cannot find {0} module.
Explanation The module cannot be found in the application package.
Action Provide the correct module name for the application package.
CWSAD0005E: The administrative command cannot find {0} Web service.
Explanation The Web services cannot be found in the module.
Action Ensure that the module has a Web service and that the service name is correct.
CWSAD0006E: The administrative command cannot find {0} logical endpoint.
Explanation The specified logical endpoint cannot be found in the serivce.
Action Provide a logical endpoint name.
CWSAD0008E: The administrative command found multiple services index files for {0} application and {1} module.
Explanation Multiple services index files were found when only one service index file is expected.
Action This is an internal error, no user action is required.
CWSAD0009E: There is no Web service in the {0} services index file.
Explanation The services index file has no entry for a Web service. The file might not be usable.
Action 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.
Explanation The services index file has no entry for a logical endpoint. The file might not be usable.
Action 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.
Explanation The services index file has no operation for the endpoint. The file might not be usable.
Action 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.
Explanation The file name must not contain slashes, directory or path name.
Action Provide the correct file name without the slashes, directory or path name.
CWSAD0013E: The specified {0} file name cannot be found.
Explanation The specified file name cannot be located in the configuration repository.
Action 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.
Explanation 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.
Action 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.
Explanation The Feature Pack for Web Services is not installed on the deployment manager node but has been installed on the managed node.
Action 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.
Explanation The module contains JAX-WS Web Services and requires the Feature Pack for Web Services. To map a Web module from an application that requires feature pack functionality even though the Web server does not have feature pack functionality, define the Web server on a node with feature pack augmentation.
Action 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.
Explanation 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.
Action 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 and conditions for information centers | Feedback

Last updated: Jun 13, 2012 3:34:38 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, 2011. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)