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. |
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. |
Problem | The application name cannot be found. |
User response | Provide the correct application name. |
Problem | The module cannot be found in the application package. |
User response | Provide the correct module name for the application package. |
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. |
Problem | The specified logical endpoint cannot be found in the serivce. |
User response | Provide a logical endpoint name. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |