Express (Distributed operating systems), v8.0 > Reference > Messages
ADMG
ADMG0001E: Configuration data {1} is not found in document {0}.
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.
ADMG0002E: Document {0} is not found.
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.
ADMG0003E: The system failed to load document {0}.
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 WAS Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/.
ADMG0004E: The system failed to save document {0}.
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.
ADMG0005E: The attribute name {0} is not valid.
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.
ADMG0006E: The attribute name path {0} is not valid.
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.
ADMG0007E: The configuration data type {0} is not valid.
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.
ADMG0011E: An unexpected exception occurred {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
ADMG0012E: The attribute value for attribute {0} is not valid.
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.
ADMG0013E: The attribute value for attribute path {0} is not valid.
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.
ADMG0014E: Attribute {0} is a read-only attribute.
Explanation We cannot modify the identified attribute. Action Do not attempt to modify a read-only attribute, or change attribute permissions.
ADMG0015E: Attribute path {0} is read only and not modifiable.
Explanation The attribute path cannot be modified. Action Do not attempt to modify a read-only attribute path, or change attribute path permissions.
ADMG0016E: The system is unable to get a validation manager for session {0}.
Explanation An exception occurred while obtaining a validation manager for the session. Action See the nested exception for information.
ADMG0017E: The validate operation failed for session {0} and scope {1}.
Explanation The validate operation failed for the specified session and specified scope. Action See the nested exception for more details.
ADMG0018E: The system is unable to locate the node {0} for the WASQueue object {1}.
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.
ADMG0019E: The system is unable to locate the unique JMS server value on node {0}.
Explanation More than one JMS server value is defined on the specified node. Action Modify the configuration to remove the invalid JMS server value.
ADMG0020E: The required attribute {0} is not found.
Explanation A required attribute is not provided. Action Supply the required attribute.
ADMG0021E: The system expected template type {0}, but the supplied template type is {1}.
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.
ADMG0022W: The system is unable to update the serverindex.xml document for server {0}: {1}.
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.
ADMG0023W: Node creation is an invalid operation. Use the AddNode command-line utility instead.
Explanation The operation is not supported. Action Use the AddNode command-line utility to incorporate a node into a cell.
ADMG0024W: Segment {1} of the containment path {0} is not correct.
Explanation The supplied parameter does not follow the detailed syntax described in the API documentation. Action Refer to the ConfigService#resolve method document for the syntax of a containment path.
ADMG0025W: The system is unable to define the SERVER_LOG_ROOT variable map for server {0}:{1}
Explanation The server was 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.
ADMG0026E: The system is unable to find the server definition for cluster member {0} of cluster {1}.
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 be updated correctly for the new cluster member. Action Check the server cluster configuration for inconsistencies or errors.
ADMG0027E: The system is unable to find the ServerEntry value for server {0}.
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.
ADMG0028W: The system is unable to delete the server definition for cluster member {0}.
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.
ADMG0029W: Server {0} is a cluster member of cluster {1}.
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.
ADMG0030E: The password for user ID {0} is not specified.
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.
ADMG0031E: The user ID and password pair is not supplied, and no JAASAuthData entry matches the specified alias {0}.
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.
ADMG0032E: An existing JAASAuthData entry matches alias {0}, so a JAASAuthData entry cannot be created for user ID {1}.
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.
ADMG0033E: Server {0} cannot be deleted because applications {1} are installed on it.
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.
ADMG0034E: The specified node name {0} is not a valid node name.
Explanation The input parameter value is not a valid node name. Note that node names are case sensitive. Action Correct the input value.
ADMG0035E: The user does not have sufficient privilege to modify attribute {0} of object type {1} in document {2}.
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.
ADMG0036E: Operation {0} is not supported in local mode.
Explanation This operation is not supported when wsadmin.sh or the configuration service runs in local mode without connecting to the server. Action Start the server and repeat the command in remote mode.
ADMG0037E: A new instance of the {0} object cannot be created because the {1} attribute of an existing {0} object has the same value as {2}.
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.
ADMG0038W: The specified resourceAdapter object is defined at a higher administrative level.({0})
Explanation This J2CResourceAdapter object is defined in the resources.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.
ADMG0039W: An unexpected error occurred while getting the attribute of {0} for {1}.
Explanation An unexpected error occurred while retrieving the specified attribute of the specified J2CResourceAdapter object. Action More info at:
ADMG0040E: The specified type {0} is not valid for this operation.
Explanation The $AdminConfig uninstallJ2CResourceAdapter command accepts the node level J2CResourceAdapter MBean only. Action Specify the node level J2CResourceAdapter MBean for the $AdminConfig uninstallResourceAdapter command. Remove the cell level or server level J2CResourceAdapter with the $AdminConfig remove command.
ADMG0041E: The specified resourceAdapter object is defined at a higher administrative level.({0})
Explanation This J2CResourceAdapter object is defined in the resources.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.
ADMG0101E: renameCell command can only run in local mode. Stop the application server or dmgr before running this command.
Explanation renameCell command can not be run when administrative client is connected to a running server. This command changes the cell name and hence needs to be run when server is shut down. Action Stop the server by running stopServer or stopManager script before running this command.
ADMG0102E: Invalid character in new cell name {0}.
Explanation The cell name cannot have leading or trailing spaces and cannot contain any of the following characters: \ / , # $ @ : ; " * ? < > | = + & % ' [ ] Action Specify a different cell name that complies with cell name rules.
ADMG0195W: Server {0} on node {1} cannot be added to core group {2}.
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.
ADMG0196W: The system cannot find the {0} core group.
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.
ADMG0197W: The system cannot find the parent node of server {0}.
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.
ADMG0198W: An exception occurred while trying to remove server {0} on node {1} from core group {2}: {3}.
Explanation While deleting the specified server, the system attempted to remove the server from its core group, but an exception occurred. The system continues the operation to delete the server. Action Evaluate the exception to determine the cause of the problem. Check the configuration to determine if a core group is inadvertently deleted.
ADMG0199W: Server {0} on node {1} cannot be found in any core group.
Explanation The system could not 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 was inadvertently deleted.
ADMG0233E: The clusterName memberNode and memberName parameters cannot be specified with the target object ID to identify the cluster member.
Explanation The cluster member can be identified either by specifying the member object ID, or by specifying the member name, node name and cluster name. Action Specify a cluster object ID for the command target object without specifying the clusterName, memberNode, and memberName parameters. Alternatively, specify all three of these parameters without specifying the target object ID.
ADMG0247E: Server Name is required.
Explanation The server name is required for the command. Action Ensure that the server name is specified.
ADMG0248E: {0} exists within node {1}.
Explanation The server name has been used already. The server can not be created. Action Specify a different server name.
ADMG0249E: The server name {0} is invalid.
Explanation The server name is invalid. The server can not be created. Action Specify a valid server name.
ADMG0250E: Node {0} is not a valid node.
Explanation The node is not valid. Either node name is incorrect or the node does not exist in the cell. Action Ensure that the node exists.
ADMG0251E: {0} is not a valid entry.
Explanation The entry is not valid. Action Specify a valid entry.
ADMG0252E: Can not create a server on a V5 Node: {0}
Explanation The server can not be created on a v5 node. Action Ensure that the version of the node is greater than 5.
ADMG0253E: Matching template {0} could not be found or is not valid for this server.
Explanation Can not find a matching server template with the template name. Action Ensure that the template name is correct.
ADMG0254E: Could not validate Create Server command {0}.
Explanation The createServer command can not be validated. Action No action is required.
ADMG0255E: Template Name is required.
Explanation The template name is required for the command. Action Ensure that the template name is specified.
ADMG0256E: {0} does not exist within node {1}.
Explanation The server does not exist within node. Can not create server template. Action Ensure that the server exists in the node.
ADMG0257E: The template name {0} is invalid.
Explanation The template name is invalid. Can not create server template. Action Ensure that the template name is valid.
ADMG0258E: Node {0} is not a valid node.
Explanation Either node name is invalid or node does not exist. Action Ensure that the node exists in the configuration.
ADMG0259E: {0} is not a valid entry.
Explanation The entry is not valid. Action Specify a valid entry.
ADMG0260E: Can not create a template using a V5 Node: {0}
Explanation The template can not be created using a v5 node. Action Ensure that the version of the node is greater than 5.
ADMG0261E: Could not validate Create Server Template command {0}.
Explanation The createServerTemplate command can not be validated. Action No action is required.
ADMG0262E: Template {0} already exists.
Explanation The template already exists. Can not create server template. Action Specify a different template name.
ADMG0300I: The Package/Type/Attribute we have chosen: {0} is valid starting at version: {1}
Explanation The given ConfigService attribute is valid starting at the specified version. Action No user action is required.
ADMG0301W: The Package/Type/Attribute we have chosen: {0} was deprecated at version: {1}
Explanation The given ConfigService attribute was deprecated at the given version. This attribute is valid, but may not be in the future. Action No user action is required.
ADMG0302E: The Package/Type/Attribute we have chosen: {0} was removed at version: {1}
Explanation The given ConfigService attribute has been removed at this version. This attribute is not valid at the given version. Action Use a valid ConfigService attribute. See the API documentation for valid attributes.
ADMG0303E: Request to install resouce adapter failed. Please make sure if the version of the resouce adapter matches with the Node's version.
Explanation The MBean request to install the resource adapter failed. Ensure that the version of the target node matches the version of the resource adapter. Action Ensure that the version of the target node matches the version of the resource adapter. A V1.5 Resource Adapter Archive (RAR) file cannot be installed on WAS V5 or earlier.
ADMG0304E: There is another J2C Resource Adapter with the same archive path that has inconsistent Isolated Class Loader attribute.
Explanation If any J2C Resource Adapter exist to shared the same archive path, isolated Class Loader value should be consistent. Action The inconsistent J2C Resource Adapter can not exist. Delete the old J2C Resource Adapter with different isolatedClassLoader value or create the new one to have the same value.
ADMG0305E: J2C Resource Adapter can not be installed with Isolated Class Loader with non-empty NativePath.
Explanation J2C Resource Adapter can not be created with IsolatedClassLoader value true, if nativePath is not null. Action Do not specify nativapath or set IsolatedClassLoader false.
ADMG0306E: Unexpected exsception occurred. {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
ADMG0420E: Node {0} is not eligible to be a member of node group {1}.
Explanation The specified node cannot be a member of the specified node group because the node group is a node group on the distributed platform. Action Choose another node or node group and retry the operation.
ADMG0421E: Node {0} is not eligible to be a member of node group {1}.
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.
ADMG0446E: The specified node {0} is not a member of node group {1}.
Explanation The specified node does not belong to any node groups. Action Choose another node or node group and retry the operation.
ADMG0447E: The specified node {0} is not a member of any node group.
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.
ADMG0451E: Node {0} cannot be removed from node group {1} because it is part of a cluster in that node group.
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.
ADMG0452E: Node {0} cannot be removed from node group {1}. This node must always be a member of at least one 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 the node group contains at least one member.
ADMG0453E: Cannot find node group {0} in the configuration repository.
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.
ADMG0454E: Node {0} is already a member of node group {1}.
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 try the operation again.
ADMG0455E: Node {0} is not eligible to be a member of node group {1}.
Explanation The specified node is not eligible to be a member of the specified node group because the node group is a sysplex node group, which is unique to the z/OS operating system. Action Choose another node or node group and retry the operation.
ADMG0456E: Node group {0} cannot be removed because it contains members.
Explanation A node group cannot be removed if it contains members. Action Remove the node group members first and try the operation again.
ADMG0457E: The default node group cannot be deleted.
Explanation The default node group cannot be deleted because a default node group is required for node group administration. Action Do not attempt to delete the default node group.
ADMG0458E: Custom property {0} already exists for node group {1}.
Explanation A node group property with the specified name already exists. Action Choose another name for the node group property, and try the operation again.
ADMG0459E: Node {0} cannot be removed from sysplex node group {1} because sysplex node group membership is required.
Explanation Nodes that belong to a sysplex node group must remain in a sysplex node group because sysplex node group membership is required. Action Use the addNodeGroupMember command to move a node to a different sysplex node group.
ADMG0460E: No property named {0} exists for node group {1}.
Explanation The specified property does not exist in the node group. Action Use the listNodeGroupProperties command to find available properties.
ADMG0489E: A sysplex node group with the short name {0} already exists.
Explanation The short name must be unique within the same sysplex. Action Verify that the short name is unique within the same sysplex.
ADMG0490E: Node {0} is not eligible to be a member of sysplex node group {1}.
Explanation The node is not eligible to be a member of the sysplex node group because v5 z/OS nodes can be a member of the default sysplex node group only. Action Do not attempt to add v5 nodes on the z/OS platform to a sysplex node group.
ADMG0491E: Node {0} is not eligible to be a member of node group {1}.
Explanation The specified node group is not a sysplex node group. Action Choose another node or node group and retry the operation.
ADMG0492E: Un-Managed Node {0} can not be added to a node group.
Explanation The unmanaged node cannot be added to the node group because a node group must contain managed nodes only. 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.
ADMG0493E: A node group with the name {0} already exists in the config.
Explanation The specified node group already exits in the configuration repository. Action Specify a different node group name and try the operation again.
ADMG0500E: Cluster scoped resource or variable configurations are not supported as cluster {0} contains one or more v5 members.
Explanation Cluster scope resource or variable configurations are introduced at v6. Action Configure the resource or variable at the server or node scope to achieve the same effect.
ADMG0501E: Application scoped resource or variable configurations are not supported as application {0} contains one or more v5 deployment targets.
Explanation Application scope resource or variable configurations are introduced at v6. Action Configure the resource or variable at the server or node scope to achieve the same effect.
ADMG0502E: A VariableMap object {1} already exists under scope {0}. There can be only one VariableMap object under a specific scope.
Explanation A VariableMap object already exists under the specified scope. Only one VariableMap object can exist under a specific scope. Action Do not attempt to create more than one VariableMap object per scope. Configure variables under just one VariableMap object for each scope.
ADMG0503E: Cannot create a new cluster member of version {0} on cluster which does not have any pre-existing cluster member of the same version.
Explanation The cluster member could not be created for the cluster because no cluster member exists at the product version specified for the new cluster member. Action Create a new cluster member at the same product version as an existing member of the cluster. For example, migrate one of the nodes of an existing cluster member to the same product version as the cluster member you are attempting to create for the cluster. The version of the cluster member changes when you migrate its node to the new version. Then create the new cluster member.
ADMG0504E: Cannot create server template using a server in a node {0} whose operating system is not known.
Explanation A server template cannot be created using a server on the specified node because the operating system is not specified for the node. The node might be a version 5 node in a mixed cell environment, and might not have been started. Action Start the node agent for the specified node. Ensure that the dmgr is running. Then create the server template by using a server in the specified node.
ADMG0505E: Access Denied to access this config data {0}.
Explanation The current user does not have access to perform the intended operation on the specified configuration data. Action Login as a different user who has access to this config data.
ADMG0550E: WAS license restrictions in effect do not allow this configuration change.
Explanation The configuration changes that were attempted exceed the license restrictions, for example, the maximum number of clusters, or members in a cluster. Action Make configuration changes within the license restrictions.
ADMG0551E: An error occurred while checking licensing restrictions.
Explanation The license restrictions could not be verified for the attempted configuration change. The license restriction data might be corrupted. Action More info at:
ADMG0614E: The specified short name {0} is invalid
Explanation The short name is invalid. Action Specify a different short name.
ADMG0620E: Invalid server type {1} passed for command {0}
Explanation The server type specified is invalid. Action Ensure that a valid server type is specified.
ADMG0621E: Server type not provided for command {0}. Server type is required when template names are specified.
Explanation The server type is required for the command. Action Ensure that the server type is specified.
ADMG0622E: Invalid template name {1} specified for command {0}
Explanation The template name is invalid. Action Ensure that a valid template name is specified.
ADMG0623E: Generic exception while validating parameters for command {0}
Explanation The generic exception occurred during the parameters validation. Action Examine the log file to determine the problem.
ADMG0624E: Generic exception while executing command {0}
Explanation The generic exception occurred during the command execution. Action Examine the log file to determine the problem.
ADMG0625E: Invalid node name {1} and/or server name {2} specified for command {0}
Explanation The node name or server name is invalid. Action Ensure that the node name or server name is valid.
ADMG0626E: Invalid feature pack or stack product name {1} specified for command {0}. Trying to add an already existing feature pack or stack product or trying to remove non-existant feature pack or stack product.
Explanation The feature pack or stack product name is invalid. The feature pack or stack product name must exist. Action Ensure that the feature pack or stack product name is valid.
ADMG0627E: Invalid feature pack or stack product name {1} specified for command {0}. Server already contains the feature pack or stack product specified.
Explanation The feature pack or stack product name is invalid. Action Ensure that the feature pack or stack product name is valid.
ADMG0628E: Invalid feature pack or stack product name {1} specified for command {0}. Server does not contain the feature pack or stack product specified.
Explanation The feature pack or stack product name is invalid. Action Ensure that the feature pack or stack product name is valid.
ADMG0629E: Server {0} on node {1} does not have template-metadata.xml
Explanation No template-metadata.xml is found in server or node. Action Ensure that the server or node has template-metadata.xml.
ADMG0630E: The template-metadata.xml not found for feature pack or stack product {0}
Explanation The feature pack or stack product does not have template-metadata.mxl. Action Ensure that the feature pack or stack product has template-metadata.xml.
ADMG0631E: No propertySet found for template {0}
Explanation The propertySet is not found for the template. Action Ensure that the propertySet exists on the template.
ADMG0632E: No template found for server type {0} and template name {1}.
Explanation The template is not found for the specified server type and template name. Action Ensure that the template exists for the template name and server type.
ADMG0650E: User not authorized to extract configuration information {0}
Explanation User does not have the permission to extract WAS configuration information. Action Ensure that user has the permission to extract configuration information.
ADMG0651E: User not authorized to apply configuration {0}
Explanation User does not have the permission to apply WAS configuration. Action Ensure that the user has the permission to apply configuration.
ADMG0652E: User not authorized to delete configuration {0}
Explanation User does not have the permission to delete WAS configuration. Action Ensure that the user has the permission to delete configuration.
ADMG0653E: Configuration property {0} specified in section {1} is invalid
Explanation Invalid configuration property is specified. Action Ensure that the configuration property specified in the section is valid.
ADMG0654E: Configuration data {0} specified is invalid
Explanation Invalid configuration data is specified. Action Ensure that the configuration data is valid.
ADMG0655E: Configuration data {0} specified in properties file {1} is invalid
Explanation Invalid configuration data is specified in property file. Action Ensure that the configuration data specified in the property file is valid.
ADMG0656E: File name {1} specified for command {0} is invalid. It cannot be created or it does not exist.
Explanation Invalid file name is specified. The file can not be created or the file does not exist. Action Ensure that the file name specified for the command is valid.
ADMG0657E: Configuration data {1} specified for command {0} is invalid
Explanation Invalid configuration data is specified in the command. Action Ensure that the configuration data specified for the command is valid.
ADMG0658E: Generic Exception during execution of command {0}
Explanation An exception is thrown during command execution. Action Examine the log file to determine the problem.
ADMG0659E: Generic Exception during execution of command {0}
Explanation An exception is thrown during command execution. Action Examine the log file to determine the problem.
ADMG0660E: Properties File Validation during command {0} failed. See Report file for details.
Explanation The properties file validation failed. Action The properties file validation failed. Examine the report file to determine the problem.
ADMG0661E: Invalid value {0} specified for parameter {1}.
Explanation The parameter value is invalid. Action Ensure that a valid parameter value is specified.
ADMG0662E: Cannot provide both ConfigDataId and configData parameters.
Explanation Can not specify both ConfigDataId and configData parameters. Only one of them can be specified. Action Specify either ConfigDataId or configData parameter.
ADMG0663E: ConfigDataId {0} specified is invalid.
Explanation Invalid ConfigDataId parameter is specified. Action Ensure that the ConfigDataId is valid.
ADMG0700W: As of {0}, the template {1} is deprecated and replaced by the template {2};
Explanation The template used has been deprecated, which still works, but some time in the future, it will no longer be available. Action Begin using the new template replacement as soon as possible.
ADMG0800E: The user does not have sufficient privilege to modify document {0}.
Explanation The user does not have privilege to modify the document. Action Ensure that the user has the sufficient privilege to modify the document.
ADMG0801E: The user does not have sufficient privilege to modify attribute {0} in document {1}.
Explanation The user does not have privilege to modify an attribute in the document. Action Ensure that the user has sufficient privilege to modify the attribute in the document.
ADMG0802E: The user does not have sufficient privilege to modify object {0} in document {1}.
Explanation The user does not have privilege to modify an object in the document. Action Ensure that the user has sufficient privilege to modify the object in the document.
ADMG0803I: No object found for Resource Id {0}. A new object will be created.
Explanation The specified Resource Id object is not found and a new object will be created. Action No action is required.
ADMG0804I: No object found for Resource Id {0} and will not be created because create is disabled for this section.
Explanation The specified Resource Id object can not be created because create is disabled. Action No action is required.
ADMG0805I: No object found for Resource Id {0} because it does not exist or user does not have required role. This object will not be removed.
Explanation The specified Resource Id object can not be removed because either the object does not exist or user does not have required role. Action No action is required.
ADMG0806I: Invalid Resource Id specified {0}.
Explanation The Resource Id is invalid. Action No action is required.
ADMG0807I: Property {0} is readonly. Will not be modified
Explanation Cannot modify property because the property is readonly. Action No action is required.
ADMG0808I: Deleting {0}.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0809I: Attribute type specified in properties file does not match with actual attribute. Section={0} attributeName={1} propertyName={2} propertyType={3} actualPropertyType={4}.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0810I: Not changing value for this property {0}. New value specified is same as current value {1}.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0811I: Changing value for this property {0}. New value specified is {1}. Old value was {2}.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0812I: Not changing value for this property {0}. Reference to ObjectName which does not have display name is not supported.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0813I: Deleting property {0}.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0814I: Deleting all properties of section with Resource Id {0} and attribute name {1}.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0815I: Cannot find property to delete {0}. The corresponding attribute name is {1}.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0816I: Deleted property {0}. The corresponding attribute names is {1}.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0817I: Deleting these properties {0}.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0818I: Processing section {0}.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0819I: End Processing section {0}.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0820I: Start applying properties from file {0}
Explanation This message is for informational purposes only. Action No action is required.
ADMG0821I: End applying properties from file {0}.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0822I: Start deleting properties from file {0}.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0823I: End deleting properties from file {0}.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0824I: Start validating properties from file {0}.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0825I: End validating properties from file {0}.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0826I: Error found in section {0}.
Explanation The properties file section has an error. Action Check generated report file for details about the error.
ADMG0827I: Creating new property name = {0} and value = {1}.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0828I: Removing these properties {0}.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0829I: Cannot find property {0} in the configuration to delete.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0830I: Deleted property {0} in the configuration.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0831I: Value specified for property {0} is not a valid type. Specified value {1}, Required type {2}
Explanation This message is for informational purposes only. Action No action is required.
ADMG0832I: Value specified for property {0} is out of range. Specified Value {1}. Required range {2}
Explanation This message is for informational purposes only. Action No action is required.
ADMG0833I: Syntax error found in this line {0}.
Explanation There is syntax error in the properties file at the specified line. Action Check generated report file for details and fix the syntax error.
ADMG0834I: Property Name specified {0} is not known. Ignoring this property.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0835I: Property {0} is readonly. The new value specified {1} is different from current value {2}. Readonly properties cannot be changed.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0836I: A null value specified for property {0}. Old value for this property is {1}. Null value cannot be applied to the property. To remove property, use deleteConfigProperties command.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0837I: Removing property found on this line {0}. Properties successfully removed {1}.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0838I: Error found in this line {0}. Some or none of the properties were added. New value specified is {1}. Old value was {2}.
Explanation The section of properties was not applied due to error. Action Check the genereated report file for details about the error and fix the error in the properties file.
ADMG0839I: Error found in this line {0}. Some or none of the properties were removed. Properties successfully removed {1}.
Explanation There is an error in the properties file at specified line number. Action Check the generated report file for details.
ADMG0840I: Executing command {0}.
Explanation This message is for informational purposes only. Action No action is required.
ADMG0841I: Error creating config object {0}. Check properties file for any missing properties that is required or invalid value specified for any property.
Explanation The object specified in the properties file section could not be created. Action Check the generated report file for details about the error and fix the error in the properties file.
ADMG0842I: Error deleting config object {0}. Check properties file to make sure object exists and not deleting any required or readonly property.
Explanation The object specified in the properties file section cannot be deleted. Action Check the generated properties file for details about the error and fix the error in the properties file.
ADMG0843I: Error modifying config object {0}. Check properties file for any invalid property value specified.
Explanation The object specified in the properties file section cannot be modified. Action Check the generated report file for details and fix the error in the properties file.
ADMG9200E: Cluster {0} already exists.
Explanation A cluster with the specified name is already configured. Action Choose another name for the cluster, and retry the operation.
ADMG9201E: Replication domain already exists for cluster {0}.
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.
ADMG9202E: Cannot find server {0} on node {1}.
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.
ADMG9203E: Server {0} on node {1} is already a member of cluster {2}.
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.
ADMG9204E: The serverNode and serverName parameters were not both specified.
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.
ADMG9205E: The cluster member weight specified is not a value from {0} to {1}.
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.
ADMG9206E: The memberWeight parameter was specified without also specifying the serverNode and serverName parameters.
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.
ADMG9207E: The replicatorEntry parameter was specified without also specifying the serverNode and serverName parameters.
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.
ADMG9208E: The replicatorEntry parameter was specified but the replicatorDomain command step was not executed.
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 run the convertServer step of the createCluster command, do not specify the replicatorEntry parameter unless you also run the replicatorDomain command step.
ADMG9209E: Exception caught validating {0} command: {1}
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.
ADMG9210E: The {0} command did not validate for the following reason: {1}
Explanation The command did not run because 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.
ADMG9211E: Cannot find the Cell object in the configuration repository.
Explanation The cell object was not found in the configuration repository. Action More info at:
ADMG9212E: Exception caught executing {0} command: {1}
Explanation An exception occurred while running the command. 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.
ADMG9213E: Both a target object ID and the clusterName parameter were specified to identify the cluster, but only one is allowed.
Explanation Either a configuration object ID or a name can be used to identify a cluster, but not both. Action Either specify a cluster object ID for the target object of the command, or specify a cluster name for the clusterName parameter of the command. Retry the operation.
ADMG9214E: The specified target object ID is not a valid cluster object.
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.
ADMG9215E: Neither the target object ID nor the clusterName parameter were specified to identify the cluster.
Explanation A cluster must be identified using either a configuration object ID or a name. Action Either specify a cluster object ID for the target object of the command, or specify a cluster name for the clusterName parameter of the command. Retry the operation.
ADMG9216E: Cannot find cluster {0}.
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.
ADMG9217E: Server {0} already exists on node {1}.
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 node of the member were specified correctly. Specify a different name or node, and retry the operation.
ADMG9218E: Cannot find node {0}.
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.
ADMG9219E: Neither the templateName parameter, nor the templateServerNode and templateServerName parameters, were specified.
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.
ADMG9220E: The templateName parameter cannot be specified with either the templateServerNode and templateServerName parameters.
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.
ADMG9221E: The templateServerNode and templateServerName parameters must both be specified.
Explanation To use an existing server as a template to 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.
ADMG9222E: The firstMember command step and its parameters cannot be specified because one or more cluster members are already configured.
Explanation The firstMember command step can run only when the 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 that you are creating the cluster member in the intended cluster. If you are, retry the operation without specifying the firstMember command step and any of its parameters.
ADMG9223E: Cannot find server template {0}.
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.
ADMG9224E: Cannot find the server for cluster member {0} on node {1} to use as template.
Explanation The server of the first cluster member, 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 template name, or template server and node, to create the first cluster member.
ADMG9225E: Cannot create replicator entry for member because no replication domain was found for cluster {0}.
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 that a replication domain has already been created for the cluster. If no replication domain has been created, create the replication domain and retry the operation. Alternatively, specify a value of false for the replicatorEntry parameter to skip the creation of a replication entry for the cluster member.
ADMG9226E: A replicator entry with the member name {0} already exists.
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 whether the replicator entry exists for another cluster member. If it does, either choose another name for the new cluster member, or do not request the creation of a replicator entry for the cluster member.
ADMG9227E: Cannot find replication domain to delete for cluster {0}.
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 replicaiton domain exists, specify a value of false for the deleteRepDomain parameter to skip the deletion of the replication domain.
ADMG9228I: Cluster {0} deleted.
Explanation The specified cluster was successfully deleted from the configuration repository. Action No action is required.
ADMG9229E: Neither the target object ID, nor the clusterName memberNode and memberName parameters, were specified to identify the cluster member.
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 target object of the command, or by specify the valid names for the clusterName, memberNode, and memberName parameters of the command. Then retry the operation.
ADMG9230E: Cannot obtain the cluster member name and node name.
Explanation While validating the cluster member object ID, the member 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.
ADMG9231E: Cannot find parent cluster of member {0} on node {1}.
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.
ADMG9232E: Cannot obtain the name of the cluster member's parent cluster.
Explanation The cluster name of the parent cluster could not be obtained for the cluster member during validation of the cluster member object ID. Action Verify the cluster member was not previously deleted. Then retry the operation.
ADMG9234E: The clusterName memberNode and memberName parameters were not all specified.
Explanation To identify a cluster member, the member name, node name and cluster name must all be specified. Action Specify the clusterName, memberNode, and memberName parameters. Retry the operation.
ADMG9235E: Cannot find cluster member {0} on node {1} in cluster {2}.
Explanation The specified cluster member could not be found in the configuration repository. Action Verify that the cluster member name and node name are specified correctly, and that they represent an existing cluster member. Verify the member belongs to the specified cluster. If the member does not, specify the correct values and retry the operation.
ADMG9236E: Cannot find server for cluster member {0} on node {1}.
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.
ADMG9237E: Cannot find replicator entry for cluster member {0} because no replication domain exists for cluster {1}.
Explanation The replicator entry for the specified cluster could not be found because there is no replication domain for the specified cluster. Action Verify that a replication domain exists for the specified cluster. A replicator entry cannot exist without a replication domain. If you are deleting a cluster member that has no replicator entry, specify a value of false for the deleteRepEntry parameter.
ADMG9238E: Cannot find replicator entry for cluster member {0} in the replication domain for cluster {1}.
Explanation The replicator entry for the specified cluster member could not be found in the configuration repository. Action Verify that the cluster member name and node are specified correctly, and that a replicator entry was created for the cluster member. If you are deleting a cluster member that has no replicator entry, specify a value of false for the deleteRepEntry parameter.
ADMG9239I: Cluster member {0} on node {1} deleted from cluster {2}.
Explanation The cluster member was deleted from the cluster. Action No action is required.
ADMG9240E: Exception caught trying to obtain an instance of AppManagement: {0}.
Explanation The AppManagement instance, which manages J2EE applications, could not be obtained. Action Evaluate the exception to determine the cause of the problem.
ADMG9241E: Cannot find parent node of server {1}.
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.
ADMG9242E: Exception caught while including server {0} on node {1} as a member of the new cluster {2}: {3}
Explanation The existing server could not be converted to a member of the new cluster. Action Evaluate the exception to determine the cause of the problem.
ADMG9243E: Exception caught while creating the server {0} on node {1} for new member of cluster {2}: {3}
Explanation A server could not be created for a new cluster member. Action Evaluate the exception to determine the cause of the problem.
ADMG9244E: Cannot find hostname of node {0}.
Explanation The domain name server (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.
ADMG9245E: Exception caught while creating new replicator entry for cluster member {0} on node {1}: {2}
Explanation A new replicator entry for the cluster member in the cluster replicator domain could not be created. Action Evaluate the exception to determine the cause of the problem.
ADMG9246E: Exception caught while checking if cluster member {0} on node {1} is compatible with cluster {2}: {3}
Explanation Checks to determine if the cluster member can belong to the specified cluster could not be performed. Action Evaluate the exception to determine the cause of the problem.
ADMG9247E: Product version {0} installed on node {1} is earlier than the product version installed on the Deployment Manager.
Explanation Different product versions are installed on the node and the dmgr. Action Verify the correct product versions 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.
ADMG9248E: A cluster member cannot be created on node {0}. The following problem with installed product versions was found: {1}.
Explanation The product version installed on the node is not compatible with the product version installed on the dmgr node or the nodes of other cluster members. Action Evaluate the problem text specified in the message. Verify that the correct product versions are installed on the dmgr node and other nodes containing members of the cluster. You might need to upgrade the product installed on the node to a newer version. Consult the documentation to determine the supported configurations and operations of a cell that has nodes installed with different product versions.
ADMG9249E: Exception caught validating the {0} step of the {1} task command: {2}
Explanation The specified step of the specified task command could not be validated. Action Evaluate the exception specified in the message to determine the problem. Then retry the operation.
ADMG9250E: The {0} step of the {1} command did not validate for the following reason: {2}
Explanation The specified step of the specified command could not be validated. 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.
ADMG9251E: Parameters are specified on command step {0} but the command step target is set to "false".
Explanation Because the value of the command step target is false, the step did not run. However, step parameters were specified, which indicate an intent to run the step. Action To run the command step, specify true for the command step target. If you do not want to run the command step, do not specify a command step target.
ADMG9252E: The firstMember command step must be specified because this member will be the first in the cluster.
Explanation The information specified in the firstMember command step is required when creating the first cluster member. The command step must be run. Action Check the cluster name and verify you are creating the cluster member in the intended cluster. If you are, retry the operation and specify the firstMember command step along with its required parameters.
ADMG9253E: Cannot create new cluster member because, there is cluster member {0} with product version {1} on node {2}.
Explanation A new cluster member cannot be created because the specified cluster member already exists for the specified version and node. Action Verify that the correct product version is installed on all the nodes and the dmgr. You might need to updgrade the product installed on the node to a newer version. Consult the documentation to determine the supported configurations and operations for a cell that has nodes installed with different product versions.
ADMG9254E: The type of server, {0}, is not appropriate for the specified cluster type, {1}.
Explanation The type of server that is being converted to be the first member of the cluster must be appropriate for the type of cluster that is being created. Only proxy servers can be converted into a proxy server cluster and only application servers can be converted into an application server cluster. Action Change the clusterType parameter of the clusterConfig step, or change the server in the convertServer step to one of appropriate type.
ADMG9255E: replicationDomain step is not valid for clusterType {0}
Explanation A replication domain can only be created for cluster type APPLICATION_SERVER. Action Change the clusterType parameter of the clusterConfig step, or remove the replicationDomain step.