Problem |
The AdminTask object encountered an exception while processing the administrative command. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
The specified administrative command requires one or parameters that were not supplied. |
User response |
Run the command again with the correct syntax. |
Problem |
The AdminTask command parameters do not represent a single target object instance. This might happen if objects with the same configuration path exist at more than one scope (server or cluster). |
User response |
Run the command again with the correct parameters, specifying the scope if necessary. |
Problem |
The administrative command parameters do not represent a target object instance at the specified scope. |
User response |
Run the command again with the correct parameters. |
Problem |
The AdminTask administrative command encountered an exception while identifying a target object for the administrative command. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
The AdminTask administrative command encountered an exception while retrieving one or more attributes. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
The AdminTask administrative command encountered an exception while querying the configuration repository. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
The AdminTask administrative command encountered an exception while retrieving the parent of an object. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
The AdminTask administrative command encountered an exception while deleting an object. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
The AdminTask administrative command encountered an exception while creating an object. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
The AdminTask administrative command encountered an exception while setting a list of attribute name and value pairs. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
The AdminTask administrative command encountered an exception while retrieving a template object. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
The event service administrative must be able to make changes to the system configuration. In a federated node, this requires a connection to the deployment manager. |
User response |
Run the command again with the appropriate connection parameters. |
Problem |
The AdminTask object encountered an exception while creating an instance of the specified AdminTask administrative command. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
The AdminTask administrative command could not find a template with the specified name in the configuration respository. |
User response |
Run the command again with the correct template name. |
Problem |
The deployEventService administrative command could not complete the creation of the event service resources because one or more of the default JNDI names is already in use by an existing resource in the configuration repository. |
User response |
Make sure the existing resource is using the correct JNDI name. Remove the partial event service configuration using the removeEventService administrative command, and then run the deployEventService administrative command again. |
Problem |
The event service AdminTask administrative commands do not support cluster members as target objects. |
User response |
Run the command again, specifying a target server that is not a cluster member. |
Problem |
The AdminTask administrative command encountered an exception while installing the specified application. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
The AdminTask administrative command encountered an exception while removing the application. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
The AdminTask administrative command encountered an exception while attempting to verifying whether the specified application is installed. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
The administrative command encountered an exception while registering or unregistering the notification listener for the AppManagement object. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
A node or server name cannot be specified with a cluster name. Specify one of the following: |
User response |
Run the command again with the correct parameters. |
Problem |
The administrative command encountered an exception during execution of the specified step. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
You are configuring the event service at cluster scope, but no data source is available at this scope. In order to function, the event service require a data source. |
User response |
Use the appropriate administrative command to create the data source for the event database, and then use the enableEventService administrative command to enable the event service. |
Problem |
The event service has detected a JDBC provider for the event database, but the provider is of a type that is not supported by the event service. The event service will use the default event database instead. |
User response |
Use the appropriate administrative commands to update the JDBC Provider. |
Problem |
The AdminTask administrative command could not find the specified JMS configuration object in the configuration repository at the specified scope. |
User response |
Run the command again with the correct parameters. Specify a valid listener port, or a valid activation specification and connection factory. |
Problem |
The specified connection factory JNDI name does not match the connection factory JNDI name configured for the specified listener port. If you specify the a connection factory along with a listener port, the JNDI name of the connection factory must be the same name configured for the listener port. |
User response |
Run the command again, specifying the correct connection factory JNDI name or omitting the connection factory JNDI name. If you do not specify a connection factory, the JNDI name configured for the listener port is used. |
Problem |
In order to create the default emitter factory and JMS transmission configuration resources for the deployed event service application, you must specify the required parameters. |
User response |
Run the command again with the correct parameters. |
Problem |
The administrative command could not enable the event service because the specified data source configuration objects do not exist at the specified scope or its parents. The event service cannot be enabled without these resources. |
User response |
Redeploy the event service application or reconfigure the event database so that the data source configuration objects are available at the correct scope. Then enable the event service. |
Problem |
The AdminTask object encountered an exception while retrieving the node version information in the node metadata properties file. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
The AdminTask object encountered an exception while updating the event service feature information in the node metadata properties file. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
The event service administrative commands do not support targets using previous versions of WebSphere Application Server. |
User response |
Specify a different target for the command, or migrate the target system to a supported version of WebSphere Application Server. |
Problem |
The specified administrative command requires a command step that was not supplied. |
User response |
Run the command again with the correct syntax. |
Problem |
The administrative command cannot be executed because the event service has not been deployed at the specified scope. |
User response |
Use the deployEventService administrative command to deploy the event service at the specified scope and then run the command again. |
Problem |
The event service administrative commands do not support the specified server target type. |
User response |
Run the command again with the appropriate parameters. |
Problem |
The specified parameters cannot have empty values. |
Problem |
The administrative command encountered an exception while attempting to creating the AppDeploymentController instance for the event service EAR file. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
The AdminTask object encountered an exception while retrieving the task data information for the specified administrative command. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
The AdminTask object could not retrieve data information for the specified task. |
User response |
Verify that the installation process completed without errors. |
Problem |
The AdminTask object encountered an exception while saving the data information for the specified task. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
The AdminTask object encountered an exception while listing the application installed on the system. |
User response |
See the exception message for additional information about the cause of the problem. |
Problem |
The binding information of an application is stored at cell scope and must be the same for all application targets. |
User response |
Verify the application name and binding information, and run the command again with the correct parameters. |