WebSphere Process Server messages     Operating Systems: All supported

CWUDD

CWUDD0001I: Attempting to deploy UDDI Registry application.
Problem The UDDI deployment process is starting.
User response None.
CWUDD0002W: Failed to discard unsaved changes caught exception Exc. Value is:
Problem This warning message indicates that changes in the wsadmin session previous to running the uddiDeploy.jacl script can not be discarded. The <Exception Message> describes the error that occurred.
User response None.
CWUDD0003I: Application Manager found.
Problem An active Application Manager can be used to stop and start UDDI on the deployment server.
User response None.
CWUDD0004I: Application Manager unavailable, application will not be started/stopped.
Problem No active Application Manager can be found so there is no need to stop and start UDDI on the deployment server.
User response None.
CWUDD0005I: ApplicationManager not running, application will not be started/stopped.
Problem Application Manager has been found, but is not running so there is no need to stop and start UDDI on the deployment server.
User response None.
CWUDD0006I: Checking for installed UDDI Registry application of name appname. Value is:
Problem The deployment script is checking for deployed UDDI applications.
User response None.
CWUDD0007I: Stopping application of name appname. Value is:
Problem Attempting to stop a deployed UDDI application.
User response None.
CWUDD0008W: Stopping application appname caught exception Exc. Application might not have been running on this server. Values are:
Problem The UDDI application stop request failed.
User response Attempt to stop the UDDI application via the Administration Console and rerun the uddiDeploy.jacl script.
CWUDD0009I: Application appname stopped successfully. Value is:
Problem The UDDI application has stopped executing.
User response None.
CWUDD0010I: Removing application appname. Value is:
Problem The deployment script is attempting to remove an existing UDDI application.
User response None.
CWUDD0011I: Application appname removed successfully. Value is:
Problem The UDDI application has been removed from the configuration.
User response None.
CWUDD0012I: Attempting to create default UDDI datasource.
Problem A default UDDI deployment has been requested and therefore a Derby datasource will be created.
User response None.
CWUDD0013I: Multiple Derby JDBC Providers found. Using first in list.
Problem The deployment script has detected a number of suitable Derby JDBC providers and will use the first.
User response None.
CWUDD0014I: UDDI Datasource name successfully created. Value is:
Problem A Derby datasource has been created for the default UDDI deployment.
User response None.
CWUDD0015I: Setting application classloader mode.
Problem The UDDI application requires PARENT_LAST class loading.
User response None.
CWUDD0016I: Altered classloader mode of application appname from oldmode to newmode. Values are:
Problem The UDDI application class loader mode has been successfully changed.
User response None.
CWUDD0017I: Setting classloader mode for application modules.
Problem The UDDI application web modules require PARENT_LAST class loading.
User response None.
CWUDD0018I: Altered classloader mode of module modname in application appname from oldmode to newmode. Values are:
Problem The UDDI Web modules class loader mode has been successfully changed.
User response None.
CWUDD0019I: UDDI successfully deployed.
Problem UDDI has been successfully deployed.
User response None.
CWUDD0020I: Attempting to save new configuration.
Problem Attempting to save the configuration after removing any existing UDDI application.
User response None.
CWUDD0021I: Changes saved successfully.
Problem Attempting to save the configuration after removing any existing UDDI application.
User response None.
CWUDD0022I: Attempting to save new configuration.
Problem Attempting to save the configuration after installing the UDDI application ear.
User response None.
CWUDD0023I: Changes saved successfully.
Problem The configuration changes have been successfully saved.
User response None.
CWUDD0024I: Attempting to save new configuration.
Problem Attempting to save the configuration after changing the class loader modes.
User response None.
CWUDD0025I: Changes saved successfully.
Problem The configuration changes have been successfully saved.
User response None.
CWUDD1001W: Failed to discard unsaved changes caught exception Exc. Value is:
Problem This warning message indicates that changes in the wsadmin session previous to running the uddiDeploy.jacl script can not be discarded. The <Exception Message&gt describes the error that occurred.
User response None.
CWUDD1002I: Application Manager found.
Problem An active Application Manager can be used to stop and start UDDI on the deployment server.
User response None.
CWUDD1003I: Application Manager unavailable, application will not be started/stopped.
Problem No active Application Manager can be found so there is no need to stop and start UDDI on the deployment server.
User response None.
CWUDD1004I: ApplicationManager not running, application will not be started/stopped.
Problem Application Manager has been found, but is not running so there is no need to stop and start UDDI on the deployment server.
User response None.
CWUDD1005I: Stopping application of name appname. Value is:
Problem Attempting to stop a deployed UDDI application.
User response None.
CWUDD1006W: Stopping application appname caught exception Exc. Application might not have been running on this server. Values are:
Problem The UDDI application stop request failed.
User response Attempt to stop the UDDI application via the Administration Console and rerun the uddiDeploy.jacl script.
CWUDD1007I: Application appname stopped successfully. Value is:
Problem The UDDI application has stopped executing.
User response None.
CWUDD1008I: Removing application appname. Value is:
Problem The removal script is attempting to remove the UDDI application.
User response None.
CWUDD1009I: Attempting to remove UDDI Registry application.
Problem The UDDI removal process is starting.
User response None.
CWUDD1010I: Application appname removed successfully. Value is:
Problem The UDDI application has been removed from the configuration.
User response None.
CWUDD1011I: Attempting to remove the default UDDI datasource.
Problem A default UDDI removal has been requested and therefore the Derby datasource used for UDDI will be removed.
User response None.
CWUDD1012I: UDDI Datasource name successfully removed. Value is:
Problem The UDDI Derby datasource has been removed from the configuration.
User response None.
CWUDD1013I: UDDI Datasource name does not exist. No action required. Value is:
Problem The default UDDI Derby datasource does not exist in this configuration and therefore does not need to be removed.
User response None.
CWUDD1014I: UDDI Registry application and default UDDI datasource removed successfully.
Problem UDDI has been successfully removed from the configuration.
User response None.
CWUDD1015I: Attempting to save new configuration.
Problem Attempting to save the configuration after removing the UDDI application.
User response None.
CWUDD1016I: Changes saved successfully.
Problem The configuration changes have been successfully saved.
User response None.
CWUDD1017I: UDDI Registry application removed successfully.
Problem UDDI has been successfully removed from the configuration.
User response None.
CWUDD1018W: Application appname is not installed. Value is:
Problem The UDDI application has not been deployed and therefore the application can not be removed.
User response None.
CWUDD6001E: Incorrect number of arguments passed to script.
Problem The wrong number of arguments were passed to the script. Arguments are Node Name, Server Name, and optionally the <b>default keyword.
User response Retry with the correct arguments.
CWUDD6002E: Usage is:
Problem The deployment script has not been called with the correct arguments.
User response Retry with the correct arguments
CWUDD6003E: Failed to determine server ID caught exception Exc. Value is:
Problem An Exception occurred whilst trying to determine the Server ID.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6004E: Failed to determine server ID, possibly due to invalid nodename or servername (check case).
Problem The Server ID could not be located for the given node name and server name.
User response Check the node name and server name are correct and are in the correct case.
CWUDD6005E: Failed to determine the list of JDBC providers caught exception Exc. Value is:
Problem The deployment script was unable to determine the list of JDBC providers.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6006E: Failed to get JDBC provider name from id caught exception Exc. Value is:
Problem An Exception occurred whilst trying to determine the list of JDBC providers for the server.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6007E: Attempt to create a Derby JDBC provider caught exception Exc. Value is:
Problem A Derby JDBC provider is required for the default deployment of UDDI and an Exception occurred whilst trying to create this JDBC provider.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6008E: Failed to create datasource caught exception Exc. Value is:
Problem An Exception occurred whilst trying to create the UDDI Derby datasource.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6009E: Failed to create resource property set caught exception Exc. Value is:
Problem An Exception occurred whilst trying to create J2EEResourcePropertySet.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6010E: Failed to create 'databaseName' resource property caught exception Exc. Value is:
Problem An Exception occurred whilst trying to create the J2EE Resource Property 'databaseName'
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6011E: Failed to create 'shutdownDatabase' resource property caught exception Exc. Value is:
Problem An Exception occurred whilst trying to create the J2EE Resource Property 'shutdownDatabase'
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6012E: Failed to create 'dataSourceName' resource property caught exception Exc. Value is:
Problem An Exception occurred whilst trying to create the J2EE Resource Property 'dataSourceName'
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6013E: Failed to create 'description' resource property caught exception Exc. Value is:
Problem An Exception occurred whilst trying to create the J2EE Resource Property 'description'
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6014E: Failed to create 'connectionAttributes' resource property caught exception Exc. Value is:
Problem An Exception occurred whilst trying to create the J2EE Resource Property 'connectionAttributes'
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6015E: Failed to create 'createDatabase' resource property caught exception Exc. Value is:
Problem An Exception occurred whilst trying to create the J2EE Resource Property 'createDatabase'
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6016E: Attempt to locate the WebSphere Installation Directory failed.
Problem The installation directory of WebSphere Application Server could not be determined.
User response Verify that WebSphere Application Server has been correctly installed and that the <b>WAS_INSTALL_ROOT WebSphere environment variable exists in the configuration.
CWUDD6017E: Uninstall of application appname caught exception Exc. Values are:
Problem An Exception occurred whilst trying to uninstall an existing UDDI application.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6018E: Install of UDDI application caught exception Exc. Value is:
Problem An Exception occurred whilst trying to install the UDDI application.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6019E: Attempt to find application classloader failed with exception Exc. Value is:
Problem An Exception occurred whilst trying to locate the classloader for the UDDI application.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6020E: Attempt to read current classloader mode failed with exception Exc. Value is:
Problem An Exception occurred whilst trying to determine the classloader mode of the UDDI application.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6021E: Attempt to modify classloader mode to newmode failed with exception Exc. Values are:
Problem An Exception occurred whilst trying to change the classloader mode of the UDDI application.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6022E: Attempt to read new classloader mode failed with exception Exc. Value is:
Problem An Exception occurred whilst trying to verify the new classloader mode of he UDDI application.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6023E: Attempt to read module list from application failed with exception Exc. Value is:
Problem An Exception occurred whilst trying to determine the list of modules held in the UDDI application.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6024E: Attempt to locate URI attribute on module failed with exception Exc. Value is:
Problem An Exception occurred whilst trying to determine the URI attribute of the application module.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6025E: Attempt to read current classloader mode from module failed with exception Exc. Value is:
Problem An Exception occurred whilst trying to determine the classloader mode of a UDDI module.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6026E: Attempt to modify module classloader mode to newmode failed with exception Exc. Values are:
Problem An Exception occurred whilst trying to change the classloader mode of a UDDI module.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6027E: Attempt to read new module classloader mode failed with exception Exc. Value is:
Problem An Exception occurred whilst trying to verify the new classloader mode of a UDDI module.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6028E: Attempt to create the default UDDI Registry Derby database failed with exception Exc. Value is:
Problem An Exception occurred whilst trying to create the default Derby database.
User response Refer to messages displayed during creation to determine cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6029E: Attempt to locate the Nodes Variable Map failed with exception Exc. Value is:
Problem An Exception occurred whilst trying to locate the configurations Variable Map for the given node.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6030E: Error saving configuration, changes not saved due to exception Exc. Value is:
Problem An Exception occurred whilst trying to to save the configuration after creating default datasource and removing an existing UDDI application.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6031E: Error saving configuration, changes not saved due to exception Exc. Value is:
Problem An Exception occurred whilst trying to to save the configuration after installing the UDDI application.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6032E: Error saving configuration, changes not saved due to exception Exc. Value is:
Problem An Exception occurred whilst trying to to save the final configuration.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6033E: Incorrect argument passed to script.
Problem The wrong argument was passed to the script. Arguments are Node Name, Server Name, and optionally the <b>default keyword.
User response Retry with the correct arguments.
CWUDD6034E: 'default' keyword is not allowed in a WebSphere Application Server Network Deployment configuration.
Problem A default Derby UDDI Registry is not permitted in a WebSphere Application Server Network Deployment configuration. Please follow the UDDI Installation instructions on how to create a non default UDDI Registry database.
User response Retry with the correct arguments.
CWUDD6035E: Cluster names are only allowed in a WebSphere Application Server Network Deployment configuration.
Problem UDDI can only be deployed to a Cluster in a Network Deployment configuration.
User response Deploy UDDI using the arguments Node and Server.
CWUDD6036E: Failed to determine cluster ID caught exception Exc. Value is:
Problem An Exception occurred whilst trying to determine the Cluster ID.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD6037E: Failed to determine cluster ID, possibly due to invalid clusterName (check case).
Problem The Cluster ID could not be located for the given cluster name.
User response Check the cluster name are correct and are in the correct case.
CWUDD7001E: Incorrect number of arguments passed to script.
Problem The wrong number of arguments were passed to the script. Arguments are Node Name, Server Name, and optionally the <b>default keyword.
User response Retry with the correct arguments.
CWUDD7002E: Usage is:
Problem The removal script has not been called with the correct arguments.
User response Retry with the correct arguments
CWUDD7003E: Failed to determine server ID caught exception Exc. Value is:
Problem An Exception occurred whilst trying to determine the Server ID.
User response Retry the removal of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, then contact the IBM Customer Service Center.
CWUDD7004E: Failed to determine server ID, possibly due to invalid nodename or servername (check case).
Problem The Server ID could not be located for the given node name or server name.
User response Check the node name or server name are correct and are in the correct case.
CWUDD7005E: Uninstall of application appname caught exception Exc. Values are:
Problem An Exception occurred whilst trying to uninstall the UDDI application.
User response Retry the removal of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD7006E: Failed to remove default UDDI datasource caught exception Exc. Value is:
Problem An Exception occurred whilst trying to remove the UDDI Derby datasource.
User response Retry the removal of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD7007E: Error saving configuration, changes not saved due to exception Exc. Value is:
Problem An Exception occurred whilst trying to to save the final configuration.
User response Retry the removal of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD7008E: Incorrect argument passed to script.
Problem The wrong argument was passed to the script. Arguments are Node Name, Server Name, and optionally the <b>default keyword.
User response Retry with the correct arguments.
CWUDD7009E: 'default' keyword is not allowed in a WebSphere Application Server Network Deployment configuration.
Problem A default Derby UDDI Registry is not permitted in a WebSphere Application Server Network Deployment configuration. Therefore there is no default Derby UDDI datasource to remove.
User response Retry with the correct arguments.
CWUDD7010E: Cluster names are only allowed in a WebSphere Application Server Network Deployment configuration.
Problem UDDI can only be removed from a Cluster in a Network Deployment configuration.
User response Remove UDDI using the arguments Node and Server.
CWUDD7011E: Failed to determine cluster ID caught exception Exc. Value is:
Problem An Exception occurred whilst trying to determine the Cluster ID.
User response Retry the deployment of UDDI. If the error persists, examine the Exception information on its cause. If the problem cannot be resolved, contact the IBM Customer Service Center.
CWUDD7012E: Failed to determine cluster ID, possibly due to invalid clusterName (check case).
Problem The Cluster ID could not be located for the given cluster name.
User response Check the cluster name are correct and are in the correct case.
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.uddi.install.SetupUDDIMessages.html

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