Licensed Materials - Property of IBM (C)Copyright IBM Corporation 2004,2005. All Rights Reserved US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. An unexpected error has occurred while processing the AdminTask command.

The AdminTask object encountered an exception while processing the administrative command.

See the exception message for additional information about the cause of the problem.

 Missing required parameter(s): parameters_name.

The specified administrative command requires one or parameters that were not supplied.

Run the command again with the correct syntax.

 Multiple configuration objects found with same configuration path config_path.

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).

Run the command again with the correct parameters, specifying the scope if necessary.

 No configuration objects found with configuration path config_path.

The administrative command parameters do not represent a target object instance at the specified scope.

Run the command again with the correct parameters.

 An error has occurred resolving the configuration object based on the configuration path config_path.

The AdminTask administrative command encountered an exception while identifying a target object for the administrative command.

See the exception message for additional information about the cause of the problem.

 An error has occurred retrieving the attribute value from configuration object config_obj. The attribute name is attr_name (a null value means the error occurred retrieving all attributes).

The AdminTask administrative command encountered an exception while retrieving one or more attributes.

See the exception message for additional information about the cause of the problem.

 An error has occurred querying configuration data for object type obj_type in scope scope.

The AdminTask administrative command encountered an exception while querying the configuration repository.

See the exception message for additional information about the cause of the problem.

 An error has occurred querying the parent of the object obj.

The AdminTask administrative command encountered an exception while retrieving the parent of an object.

See the exception message for additional information about the cause of the problem.

 An error has occurred deleting the configuration object obj.

The AdminTask administrative command encountered an exception while deleting an object.

See the exception message for additional information about the cause of the problem.

 An error has occurred creating the configuration object name of type/template type_or_template with attributes attrs under configuration object parent.

The AdminTask administrative command encountered an exception while creating an object.

See the exception message for additional information about the cause of the problem.

 An error has occurred setting the attributes attrs of configuration object config_obj.

The AdminTask administrative command encountered an exception while setting a list of attribute name and value pairs.

See the exception message for additional information about the cause of the problem.

 An error has occurred querying template object with type template_type and name template_name.

The AdminTask administrative command encountered an exception while retrieving a template object.

See the exception message for additional information about the cause of the problem.

 The event service administrative commands cannot be executed in a federated node using local mode.

The event service administrative commands must be able to make changes to the system configuration. In a federated node, this requires a connection to the deployment manager.

Run the command again with the appropriate connection parameters.

 An error has occurred while creating the cmd_name administrative command instance.

The AdminTask object encountered an exception while creating an instance of the specified AdminTask administrative command.

See the exception message for additional information about the cause of the problem.

 The template template_name could not be found.

The AdminTask administrative command could not find a template with the specified name in the configuration respository.

Run the command again with the correct template name.

 A object_type configuration object with JNDI name jndi_name already exists in the scope scope and will not be recreated using the default values.

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.

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.

 The server server_name of node node_name is member of cluster cluster_name and cannot be used as target for this administrative command.

The event service AdminTask administrative commands do not support cluster members as target objects.

Run the command again, specifying a target server that is not a cluster member.

 The application application_name could not be installed.

The AdminTask administrative command encountered an exception while installing the specified application.

See the exception message for additional information about the cause of the problem.

 The application application_name could not be removed.

The AdminTask administrative command encountered an exception while removing the application.

See the exception message for additional information about the cause of the problem.

 The administrative command could not verify whether application application_name is installed.

The AdminTask administrative command encountered an exception while attempting to verifying whether the specified application is installed.

See the exception message for additional information about the cause of the problem.

 An error has occurred while registering or unregistering the notification listener for AppManagement object app_mgmt.

The administrative command encountered an exception while registering or unregistering the notification listener for the AppManagement object.

See the exception message for additional information about the cause of the problem.

 The admin_task_name administrative command completed successfully. The specified combination of parameters (clusterName/serverName/nodeName) is not valid.

A node or server name cannot be specified with a cluster name. Specify one of the following:

  • cluster name
  • node name (the default is the node configured by the current profile)
  • node name and server name
  • server name

Run the command again with the correct parameters.

 The admin_task_name administrative command step step_name completed successfully. An error occurred during the step_name step of the admin_task_name administrative command.

The administrative command encountered an exception during execution of the specified step.

See the exception message for additional information about the cause of the problem.

 The cluster cluster_name does not have an event database data source configured at the cluster scope. The event service of this cluster will be disabled.

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.

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.

 The backend ID for the JDBC Provider provider_name, type provider_type, is not valid.

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.

Use the appropriate administrative commands to update the JDBC Provider.

 The administrative command could not find a configuration object of type obj_type with name obj_name in scope scope.

The AdminTask administrative command could not find the specified JMS configuration object in the configuration repository at the specified scope.

Run the command again with the correct parameters. Specify a valid listener port, or a valid activation specification and connection factory.

 The specified JNDI name for a JMS resource does not match the name specified in the obj_type named obj_name.
Configured value: obj_name
Specified value: obj_name

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.

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.

 The administrative command could not create required resources for the deployed event service application app_name because required parameters were not specified for the queue JNDI name and connection factory JNDI name.
Queue JNDI Name: q_jndi_name
Queue Connection Factory JNDI Name: qcf_jndi_name

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.

Run the command again with the correct parameters.

 The event service could not be enabled because the required data source configuration objects were not found.
Event data source JNDI name: event_jndi_name
Catalog data source JNDI Name: catalog_jndi_name
Scope: scope

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.

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.

 An error occurred while retrieving the node metadata property propName for node nodeName.

The AdminTask object encountered an exception while retrieving the node version information in the node metadata properties file.

See the exception message for additional information about the cause of the problem.

 An error occurred while updating the node metadata properties file for node nodeName.

The AdminTask object encountered an exception while updating the event service feature information in the node metadata properties file.

See the exception message for additional information about the cause of the problem.

 Unsupported WebSphere Application Server version detected for node nodeName: version.

The event service administrative commands do not support targets using previous versions of WebSphere Application Server.

Specify a different target for the command, or migrate the target system to a supported version of WebSphere Application Server.

 Missing required command step: cmd_step.

The specified administrative command requires a command step that was not supplied.

Run the command again with the correct syntax.

 The administrative command cmd_name failed because the event service is not deployed at the specified scope.

The administrative command cannot be executed because the event service has not been deployed at the specified scope.

Use the deployEventService administrative command to deploy the event service at the specified scope and then run the command again.

 Unsupported server type detected for server serverName: server_type.

The event service administrative commands do not support the specified server target type.

Run the command again with the appropriate parameters.

 No value was specified for the following parameters: parameter_list.

The specified parameters cannot have empty values.

Run the administrative command again, specifying values for these parameters.

 node_name is not a valid node name. cluster_name is not a valid cluster name. server_name is not a valid server name. The administrative command could not create an AppDeploymentController instance for EAR file ear_file_path.

The administrative command encountered an exception while attempting to creating the AppDeploymentController instance for the event service EAR file.

See the exception message for additional information about the cause of the problem.

 An error occurred while retrieving task data information for the taskName administrative command.

The AdminTask object encountered an exception while retrieving the task data information for the specified administrative command.

See the exception message for additional information about the cause of the problem.

 No data information is available for task taskName.

The AdminTask object could not retrieve data information for the specified task.

Verify that the installation process completed without errors.

 An error occurred while saving task data information for task task_name.

The AdminTask object encountered an exception while saving the data information for the specified task.

See the exception message for additional information about the cause of the problem.

 An error occurred while listing the applications installed on the system.

The AdminTask object encountered an exception while listing the application installed on the system.

See the exception message for additional information about the cause of the problem.

 Unable to deploy application appName with binding: [ListenerPort name = new_listener_port, ActivationSpec JNDI name = new_activation_spec] because this application is already deployed using binding: [ListenerPort name = inst_listener_port, ActivationSpec JNDI name = inst_activation_spec].

The binding information of an application is stored at cell scope and must be the same for all application targets.

Verify the application name and binding information, and run the command again with the correct parameters.