Explanation | The configuration data might be removed or the ID of the configuration is not valid. |
Action | Issue a query command to confirm that this configuration data still exists. |
Explanation | The specified document is not found. It might be removed already, or the document URI is not valid. |
Action | Issue a query command again to make sure that the document URI is the same as the returned query command. |
Explanation | Either the document cannot be retrieved from the configuration repository, or the document is not a valid XMI document. See the nested exception for details. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An inconsistency exists in the document content, or the document cannot be saved in the configuration repository successfully. See the nested exception for details. |
Action | Discard the change and repeat the operation. |
Explanation | The identified attribute name is not valid. |
Action | Get the meta information for the object and verify that the spelling of the attribute name is correct. Note that attribute names are case sensitive. |
Explanation | The identified attribute name path is not valid. |
Action | Get the meta information for the object and verify that the spelling of the attribute name is correct. Note that attribute names are case sensitive. |
Explanation | The identified type is not valid. |
Action | Get the supported data type list and verify the data type name. Note that data type names are case sensitive. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The type of the supplied attribute value does not match the attribute type. |
Action | Get the meta information for that attribute and verify that the types match. |
Explanation | The type of the supplied attribute value does not match the attribute type. |
Action | Get the meta information for that attribute and verify that the types match. |
Explanation | You cannot modify the identified attribute. |
Action | Do not attempt to modify a read-only attribute, or change attribute permissions. |
Explanation | The attribute path cannot be modified. |
Action | Do not attempt to modify a read-only attribute path, or change attribute path permissions. |
Explanation | An exception occurred while obtaining a validation manager for the session. |
Action | See the nested exception for information. |
Explanation | This error message is generic for validation-related errors. |
Action | See the nested exception for more details. |
Explanation | The node attribute value of the WASQueue instance is not valid. |
Action | Supply a valid node name as the attribute value for the node attribute on the WASQueue object. |
Explanation | More than one JMS server value is defined on the specified node. |
Action | Modify the configuration to remove the invalid JMS server value. |
Explanation | A required attribute is not provided. |
Action | Supply the required attribute. |
Explanation | The template type is different from the object type being created. |
Action | Check the input parameters and verify that the template and object types match. |
Explanation | The serverindex.xml document is not available for update. Some inconsistencies might exist between the serverindex.xml document and the rest of the configuration. |
Action | Manually update the serverindex.xml document to keep it consistent with the configuration. |
Explanation | The operation is not supported. |
Action | Use the AddNode command-line utility to incorporate a node into a cell. |
Explanation | The supplied parameter does not follow the detailed syntax described in the Javadoc documentation. |
Action | Refer to the ConfigService#resolve method document for the syntax of a containment path. |
Explanation | The server created successfully, but the SERVER_LOG_ROOT variable map creation under the newly created server scope failed. |
Action | Manually define the VariableMap SERVER_LOG_ROOT value as ${LOG_ROOT}/serverName under the server scope in the variables.xml file. |
Explanation | When a new cluster member is added to a server cluster, the applications that are deployed on the clusters are automatically deployed on the new cluster member. In this case, the definition of an existing cluster member cannot be found, so the application deployment information cannot update correctly for the new cluster member. |
Action | Check the server cluster configuration for inconsistencies or errors. |
Explanation | An inconsistency exists between the server configuration and its serverindex.xml document. |
Action | Manually edit the server index document to keep it consistent with the server configuration. |
Explanation | The cluster member is removed from a server cluster, but the server definition of the cluster member cannot be removed. |
Action | Manually remove the server definition from the cluster configuration. |
Explanation | A server can not be converted to a server cluster if it is part of an existing cluster. |
Action | No user action is required. |
Explanation | If a user ID is specified, a password must be specified when the defaultPrincipalMapping value is defined. |
Action | Supply a password for the specified user ID. |
Explanation | If the user ID and password pair is not supplied in a defaultPrincipalMapping for a J2CConnectionFactory, use of an existing JAASAuthData entry is assumed. |
Action | Supply a user ID and password pair, or use an alias matching an existing JAASAuthData entry. |
Explanation | If a user ID and password are specified, a JAASAuthData entry is automatically created when a defaultPrincipalMapping value is defined. The creation of a JAASAuthData entry failed because an alias with the specified name already exists. |
Action | Omit the user ID and password to use an existing JAASAuthData entry, or use a different alias to create a new JAASAuthData entry. |
Explanation | If a server is deleted before the installed applications are uninstalled, those applications fall into an inconsistent state and might not run normally. |
Action | Uninstall the applications on the server before deleting the server. |
Explanation | The input parameter value is not a valid node name. Note that node names are case sensitive. |
Action | Correct the input value. |
Explanation | The administrator role is required to modify the specified attribute. |
Action | Log in as a user who has an administrator role and try the command again. |
Explanation | This operation is not supported when the wsadmin tool or the configuration service runs in local mode without connecting to the server. |
Action | Start the server and repeat the command in remote mode. |
Explanation | Certain types of configuration objects require that one of their attributes has a unique value. For example, the value of the name attribute of the VirtualHost configuration object must be unique. |
Action | Specify a different attribute value to satisfy the uniqueness requirement. |
Explanation | This J2CResourceAdapter object is defined in the resource.xml file of an administrative layer higher than the specified layer. Consequently, removal of the object at the specified level destroys consistency across the entire defined administrative area. |
Action | Uninstall the J2CResourceAdapter from the higher administrative layer to maintain consistency across the entire administrative area. |
Explanation | An unexpected error occurred while retrieving the specified attribute of the specified J2CResourceAdapter object. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The $AdminConfig uninstallJ2CResourceAdapter command accepts the node level J2CResourceAdapter only. |
Action | Specify the node level J2CResourceAdapter for the $AdminConfig uninstallResourceAdapter command. Remove the cell level or server level J2CResourceAdapter with the $AdminConfig remove command. |
Explanation | The system continues to create the new server. While creating the server, the server cannot be added to the specfied core group. |
Action | Check the configuration to determine if the core group exists. |
Explanation | The specified core group cannot be found. The system continues with the configuration operation. |
Action | Check the configuration to determine if the core group exists. |
Explanation | The node cannot be found in the configuration on this server. The system continues the configuration operation. |
Action | Check the configuration to determine if a node might be inadvertently deleted. |
Explanation | While deleting the specified server, the system attempted to remove the server from its core group, but an exception occurred. |
Action | The system continues the operation to delete the server. Evaluate the exception to determine the cause of the problem. Check the configuration to determine if a core group is inadvertently deleted. |
Explanation | The system cannot find the core group while performing a delete operation. The system continued the delete operation. |
Action | Check the configuration to determine if a core group is inadvertently deleted. |
Explanation | The cluster member can be identified either by specifying the member's object ID, or by specifying the member's name, node name and cluster name. |
Action | Specifying a cluster object ID for the command's target object, without the clusterName, memberNode and memberName parameters. Or specify all three of these parameters without specifying the target object ID. |
Explanation | The given ConfigService attribute is valid starting at version. |
Action | Nothing, this is informational. |
Explanation | The given ConfigService attribute was deprecated at the given version. |
Action | This attribute is valid, but may not be in the future. |
Explanation | The given ConfigService attribute has been removed at this version. |
Action | This attribute is not valid at the given version. |
Explanation | MBean request to install resource adapter had failed. Please make sure if the version of the target Node matches with the resource adapter. |
Action | Make sure if the version of the Node matches with the version of resource adapter. V1.5 rar file can not be installed on WebSphere V5 or earlier. |
Explanation | The specified node group is a distributed node group. |
Action | Choose another node or node group and retry the operation. |
Explanation | The specified node group is a sysplex node group in a different sysplex. |
Action | Choose another node or node group and retry the operation. |
Explanation | The specified node does not belong to any node groups. |
Action | Choose another node or node group and retry the operation. |
Explanation | The specified node does not belong to any node groups. |
Action | Choose another node or add the node to the node group and try the operation again. |
Explanation | A node cannot be removed from a node group because it contains cluster members in that node group. |
Action | Add the node that has cluster members to another node group before removing that node from the original node group. |
Explanation | A node cannot be removed from a node group. A node must always be a member of at least one node group. |
Action | Ensure that a node group contains at least one member. |
Explanation | The specified node group cannot be found in the configuration repository. |
Action | Determine if the specified node group exists, and if the correct node group name is specified. Specify a valid node group name and try the operation again. |
Explanation | The node member cannot be added to the node group because a member with that name already exists in the node group. |
Action | Determine if the specified node is already in the node group, or if the correct node name is specified. Specify a valid node name and the operation again. |
Explanation | The specified node group is a z/OS or sysplex node group. |
Action | Choose another node or node group and retry the operation. |
Explanation | A node group cannot be removed if it contains members. |
Action | Remove the node group members first and try the operation again. |
Explanation | Default node group is required by WebSphere for node group administration. |
Action | Do not attempt to delete the default node group |
Explanation | A node group property with the specified name is already created. |
Action | Choose another name for the node group property, and try the operation again. |
Explanation | Nodes that belong to a sysplex node group must remain because sysplex node group membership is required. |
Action | Use the addNodeGroupMember command to move a node to a different sysplex node group. |
Explanation | The short name must be unique within the same sysplex. |
Action | Verify that the short name is unique within the same sysplex. |
Explanation | The node is not eligible to be a member of the sysplex node group because Version 5 z/OS nodes can be a member of the default sysplex node group only. |
Action | Do not attempt to add Version 5 z/OS nodes to a sysplex node group. |
Explanation | The specified node group is not a sysplex node group. |
Action | Choose another node or node group and retry the operation. |
Explanation | A node group should only contain managed nodes. |
Action | Determine if the specified node is a managed node or if the correct node name was specified. Choose a managed node and retry the operation. |
Explanation | The specified node group already exits in the configuration repository. |
Action | Determine if the node group name already exists in the config. Specify a different node group name and try the operation again. |
Explanation | Cluster scoped resource or variable configurations are introduced at Version 6. |
Action | Configure the resource or variable at the server or node scope to achieve the same effect. |
Explanation | Application scoped resource or variable configurations are introduced at Version 6. |
Action | Configure the resource or variable at the server or node scope to achieve the same effect. |
Explanation | There can be only one VariableMap object under a specific scope. |
Action | Do not attempt to create more than one VariableMap per scope. Configure variables under just one VariableMap object for each scope. |
Explanation | There should be atleast one cluster member of the same version as that of the new cluster member being created in the cluster. |
Action | For example, to get a 6.X cluster member in cluster with all 5.X cluster members, migrate one of the nodes with 5.X cluster member to 6.X. That will convert the 5.X cluster member to 6.X cluster member. Now another new cluster member of version 6.X can be created. |
Explanation | The node operating system is not set for this node. This may be a V5 node in the mixed cell environment and this node was never started. |
Action | Start the nodeagent for this node first and make sure the dmgr is also running. And then create the server template using a server in this node. |
Explanation | The current user does not have access to perform the intended operation on this config data. |
Action | Login as a different user who has access to this config data. |
Explanation | The configuration change being made exceeds the license retrictions in effect, for example, the maximum number of clusters or members in a cluster. |
Action | Make configuration changes within the license restrictions. |
Explanation | An error occurred while checking the configuration change being processed against any license restrictions in effect. It is possible that license restriction data has become corrupted. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A cluster with the specified name is already configured. |
Action | Choose another name for the cluster, and retry the operation. |
Explanation | A replication domain with the name of the specified cluster is already configured. |
Action | If the named replication domain is no longer needed, delete it from the configuration. Otherwise, choose another name for the cluster. Then retry the operation. |
Explanation | A server with the specified name is not configured on the specified node. |
Action | Determine if the names of the server and node are correct. Specify the correct server and node names for a configured server. Then retry the operation. |
Explanation | The server is already a member of the specified cluster. It cannot be a member of another cluster. |
Action | Choose another server to include in the cluster, or do not include a server in the cluster. Then retry the operation. |
Explanation | To convert an existing server to be the first member of cluster, both the name of the server and name of the node where the server resides must be specified. |
Action | Specify both parameters, and retry the operation. |
Explanation | The weight of the cluster member was not valid. It must be a value in the range specified in the message. |
Action | Specify a valid value for the cluster member weight, and retry the operation. |
Explanation | When creating a cluster, the cluster member weight can be specified only when converting an existing server to be the first member of the cluster. |
Action | When you create a server cluster, do not specify the memberWeight parameter if you do not want to convert an existing server. Or, specify the serverNode and serverName parameters to convert an existing server. Then retry the operation. |
Explanation | When creating a cluster, a member replicator entry can be created only when converting an existing server to be the first member of the clsuter. |
Action | When you create a server cluster, do not specify the replicatorEntry parameter if you do not want to convert an existing server. Or, specify the serverNode and serverName parameters to convert an existing server. Then retry the operation. |
Explanation | When converting a server to be the first member of a cluster, a replicator entry can be created only if a replication domain for the cluster is also created. |
Action | If you execute the convertServer step of createCluster command, do not specify the replicatorEntry parameter unless you also execute the replicatorDomain command step. |
Explanation | While validating the command, an exception was caught. |
Action | Evaluate the exception specified in the message to determine the problem. Then retry the operation. |
Explanation | The command was not executed becaused it failed validation. |
Action | Evaluate the reason specified in the message to determine the problem. This is usually a problem with the command parameters. Correct the problem, and retry the operation. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | While executing the command, an exception was caught. |
Action | Evaluate the exception specified in the message to determine the problem. Configuration changes may not have been committed. To be safe, discard any configuration changes made in this session. Then retry the operation. |
Explanation | Either a configuration object ID or a name can be used to identify a cluster, but not both. |
Action | Specifying a cluster object ID for the command's target object, or by specifying a cluster name for the command's clusterName parameter. Then retry the operation. |
Explanation | The configuration object represented by the specified object ID could not be found in the configuration repository, or is not the object ID of a cluster. |
Action | Investigate the object ID, and how it was obtained, to determine if it represents a valid cluster object in the configuration repository. Specify a valid cluster object ID and retry the operation. |
Explanation | A cluster must be identified using either a configuration object ID or a name. |
Action | Specify a cluster object ID for the command's target object, or by specify a cluster name for the command's clusterName parameter. Then retry the operation. |
Explanation | The specified cluster could not be found in the configuration repository. |
Action | Determine if the specified cluster was created, or if the correct cluster name was specified. Specify a valid cluster name and retry the operation. |
Explanation | A cluster member cannot be created because a server with the specified name is already configured on the specified node. |
Action | Determine if the name of the cluster member and member's node were specified correctly. Specify a different name or node, and retry the operation. |
Explanation | The specified node could not be found in the configuration repository. |
Action | Determine if the specified node was created, or if the correct node name was specified. Specify a valid node name and retry the operation. |
Explanation | To create the first member of the cluster, either a template name must be specified, or the name and node of an existing server to use as the template must be specified. |
Action | Specify either the templateName paramater, or both the templateServerNode and templateServerName parameters, and retry the operation. |
Explanation | To create the first member of the cluster, a template name must be specified, or the name and node of an existing server to use as the template must be specified, but not both. |
Action | Specify either the templateName paramater, or both the templateServerNode and templateServerName parameters, and retry the operation. |
Explanation | To use an existing server as a template for create the first member of a cluster, both the name and node of the server must be specified. |
Action | Specify both the templateServerNode and templateServerName parameters, and retry the operation. |
Explanation | The firstMember command step can only be execute when creating the first member of a cluster. When creating additional cluster members the information specified in this step is not valid. |
Action | Check the cluster name and verify you are creating the cluster member in the intended cluster. If so, retry the operation without specifying the firstMember command step and any of its parameters. |
Explanation | The specified template could not be found in the configuration repository. |
Action | Verify the template name was specified correctly, the template exists, and the template is for a server type of configuration object. Specify a valid server template and retry the operation. |
Explanation | The first cluster member's server, which is used as the template when creating additional cluster members, cannot be found. |
Action | Verify the first cluster member has already been created and saved in the configuration repository. The first cluster member must be created before creating additional cluster members. Specify a a template name, or template server and node, to create the first cluster member. |
Explanation | A replicator entry cannot be created for the new cluster member because no replication domain can be found which has the name of the specified cluster. |
Action | Verify a replication domain has already been created for the cluster. If not, create the replication domain and retry the operation. Or, specify a value of false for the replicatorEntry parameter to skip the creation of a replication entry for the cluster member. |
Explanation | A replicator entry cannot be created for the new cluster member because an existing replicator entry with the same name was already found in the replication domain. |
Action | Verify the replicator entry to determine if the replicator entry is for another cluster member. If so, choose another name for the new cluster member. Or, do not request the creation of a replicator entry for the cluster member. |
Explanation | The replication domain for the specified cluster cannot be deleted because no replication domain having this cluster name can be found in the configuration repository. |
Action | Verify the correct cluster name was specified, and that a replication domain exists for this cluster. If no replication domain exists. If no domain exists, specify a value of false for the deleteRepDomain parameter to skip the deletion of the replication domain. |
Explanation | The specified cluster was successfully deleted from the configuration repository. |
Action | None. |
Explanation | A cluster member must be identified by specifying either a configuration object ID, or the names of the member, the node where the member resides, and the cluster to which the member belongs. |
Action | Specify a cluster member object ID for the command's target object, or by specify the valid names for the command's clusterName memberNode and memberName parameters. Then retry the operation. |
Explanation | While validating the cluster member object ID, the member's name and node could not be obtained. |
Action | Verify the object ID is a valid ID for a cluster member, and not another type of configuration object. Then retry the operation. |
Explanation | The parent cluster object of the specified cluster member could not be found in the configuration repository. |
Action | Verify the correct cluster member was specified, and the cluster itself was not previously deleted. Then retry the operation. |
Explanation | While validating the cluster member object ID, the cluster name of the member's parent cluster could not be obtained.. |
Action | Verify the cluster member was not previously deleted. Then retry the operation. |
Explanation | To identify a cluster member, the member's name, node name and cluster name must all be specified. |
Action | Specify all three of the clusterName memberNode and memberName parameters, and retry the operation. |
Explanation | The specified cluster member could not be found in the configuration repository. |
Action | Verify the cluster's member name and node name are specified correctly and represent and existing cluster member. Verify the member belongs to the specified cluster. If not, specify the correct values and retry the operation. |
Explanation | The server for the specified cluster member could not be found in the configuration repository. |
Action | Verify the server was not deleted without removing the cluster member. Then retry the operation. |
Explanation | The replicator entry for the specified cluster could not be found because there is no replication domain for the specified cluster. |
Action | Verify a replication domain exists for the specified cluster. A replicator entry cannot exist without a replication domain. If deleting a cluster member which has no replicator entry, specify a value of false for the deleteRepEntry parameter. |
Explanation | The replicator entry for the specified cluster member could not be found in the configuration repository. |
Action | Verify the cluster member's name and node are specified correctly, and a replicator entry was created for the cluster member. If deleting a cluster member which has not replicator entry, specify a value of false for the deleteRepEntry parameter. |
Explanation | The cluster member was deleted from the cluster. |
Action | None. |
Explanation | While obtaining an instance of AppManagement to manage J2EE applications, an exception was encountered. |
Action | Evaluate the exception to determine the cause of the problem. |
Explanation | The node where the specified server resides could not be found in the configuration repository. |
Action | Verify the server, or the node on which it resides, was not deleted. |
Explanation | While converting the existing server to be a member of the new cluster, an exception was caught. |
Action | Evaluate the exception to determine the cause of the problem. |
Explanation | While creating the server for a new cluster member, an exception was caught. |
Action | Evaluate the exception to determine the cause of the problem. |
Explanation | The DNS hostname of the specified node could not be found. |
Action | Verify the IP network configuration of the system on which the node is defined, and the node where this operation was invoked. Verify the correct node name was specfied, and the node was not deleted from the configuration. |
Explanation | While creating a new replicator entry for the cluster member in the cluster's replication domain, an exception was caught. |
Action | Evaluate the exception to determine the cause of the problem. |
Explanation | While performing a series of checks to determine if the cluster member can belong to the specified cluster, an unexpected exception was caught. |
Action | Evaluate the exception to determine the cause of the problem. |
Explanation | Different product versions are installed on the node and the Deployment Manager. |
Action | Verify the correct product version are installed on the node and the Deployment Manager. The product installed on the node may need to be upgraded to a newer version. Consult the document to determine the supported configurations and operations of a cell which has nodes installed with different product versions. |
Explanation | The product version installed on the node is not compatible with the product version installed on the DeploymentManager node or the nodes of other cluster members. |
Action | Evaluate problem text specified in the message. Verify the correct product versios are installed on this, the Deployment Manager node, and other nodes containing member of the cluster. The product installed on the node may need to be upgraded to a newer version. Consult the documentation to determine the supported configurations and operations of a cell which has nodes installed with different product versions. |
Explanation | While validating the command, an exception was caught. |
Action | Evaluate the exception specified in the message to determine the problem. Then retry the operation. |
Explanation | The command step was not executed becaused it failed validation. |
Action | Evaluate the reason specified in the message to determine the problem. This is usually a problem with the command parameters. Correct the problem, and retry the operation. |
Explanation | Because the value of the command step target is "false", the step will not be executed. However, step parameters were specified, which indicate an intent to execute the step. |
Action | If you want to execute the command step, specify "true" for the command step target, or specify no command step target. |
Explanation | The information specified in the firstMember command step is required when creating the first cluster member. The command step must be executed. |
Action | Check the cluster name and verify you are creating the cluster member in the intended cluster. If so, retry the operation and specify the firstMember command step along with its requirement parameters |
Explanation | Cannot create new cluster members on a heterogeneous cluster. |
Action | Verify the correct product version are installed on all the nodes and the Deployment Manager. The product installed on the node may need to be upgraded to a newer version. Consult the document to determine the supported configurations and operations of a cell which has nodes installed with different product versions. |