CHKW (V6.0.x servers)

Express (Distributed operating systems), v8.0 > Reference > Messages

CHKW (V6.0.x servers)

CHKW7200I: IBM WebSphere Validation.

Explanation No additional information is available.
Action No action is required.

CHKW7201I: CoreGroup Validation.

Explanation No additional information is available.
Action No action is required

CHKW7202E: The name of the core group stored in {0} is missing.

Explanation The product configuration document does not include the name of the core group stored in the specified location.
Action Add the name of this core group to the product configuration document.

CHKW7203E: The core group name {0} is not valid.

Explanation The core group name must follow the product's managed object naming conventions. The specified core group name does not follow these conventions.
Action Specify a valid name for this core group.

CHKW7204E: The lower limit of the range of IP addresses for multicast in core group named {0} is missing.

Explanation If a core group is going to use a multicast transport, the transport settings must include a value for the Multicast group IP start property. This value should be the the lowest IP address in the range of IP addresses that are available for the core group to use. The multicast transport configuration for the specified core group does not include a value for the Multicast group IP start property.
Action Specify a value for the Multicast group IP start property.

CHKW7205E: The upper limit of the range of IP addresses for multicast in core group named {0} is missing.

Explanation If a core group is going to use a multicast transport, the transport settings must include a value for the Multicast group IP end property. This value should be the the highest IP address in the range of IP addresses that are available for the core group to use. The multicast transport configuration for the specified core group does not include a value for the Multicast group IP end property.
Action Specify a value for the Multicast group IP end property.

CHKW7206E: The {0} transport type specified for core group named {1} is not valid.

Explanation The only transport types that can be specified for a core group are CHANNEL_FRAMEWORK, UNICAST, or MULITICAST.
Action Select either CHANNEL_FRAMEWORK, UNICAST, or MULITICAST for the core group's Transport type setting.

CHKW7207E: The "is-alive" timer value, {0}, measured in seconds, for the high-availability manager policy named {1}, is too low. The timer value must be at least {2}.

Explanation The configuration settings for the specified high availability manager policy does not include a valid value for the Is alive timer property .
Action Update the configuration settings for the specified high availability manager policy to include a valid value for the Is alive timer property.

CHKW7208E: The name of the policy factory for the {0} high-availability manager policy is missing.

Explanation A high availability manager policy must have an appropriate policy factory.
Action Provide an appropriate policy factory name for the specified high availability manager policy.

CHKW7212E: The name of a high-availability manager policy associated with core group named {0} is missing.

Explanation All high availability manager policies that are attached to a core group must have valid and unique names.
Action Make sure that all of the policies associated with a valid and unique name for the high availability policy of concern.

CHKW7213E: The high-availability manager policy name {0} associated with core group named {1} is not valid.

Explanation The name of a high availability manager policy must follow the Application Server managed object naming conventions.
Action Make sure that valid and unique names have been given to all of the policies associated with the specified core group.

CHKW7214E: The name component of the match criteria having {0} as the value component, and associated with the high-availability manager policy named {1} is missing.

Explanation The match criteria for a policy consists of a name-value pairing that matches one of the name-value attributes that form the name of the high availability group that is associated with this policy. The match criteria for the specified policy does not include the name portion of the pairing.
Action Specify a valid string for the match criteria's Name property such that the combination of the values specified for the Name and Value properties match one of the name-value attributes that form the name of the high availability group that is associated with this policy.

CHKW7215E: The name component of the match criteria having {0} as the value component, and associated with the high-availability manager policy named {1} is not valid.

Explanation The match criteria for a policy consists of a name-value pairing that matches one of the name-value attributes that form the name of the high availability group that is associated with this policy. The name portion of the match criteria for the specified policy is not valid.
Action Specify a valid string for the match criteria's Name property such that the combination of the values specified for the Name and Value properties match one of the name-value attributes that form the name of the high availability group that is associated with this policy.

CHKW7216E: The value component of the match criteria having {0} as the name component, and associated with the {1} high-availability manager policy is missing.

Explanation The match criteria for a policy consists of a name-value pairing that matches one of the name-value attributes that form the name of the high availability group that is associated with this policy. The match criteria for the specified policy does not include the value portion of the pairing.
Action Specify a valid string for the match criteria's Value property such that the combination of the values specified for the Name and Value properties match one of the name-value attributes that form the name of the high availability group that is associated with this policy.

CHKW7217E: The value component of the match criteria having {0} as the name component, and associated with the high-availability manager policy named {1} is not valid.

Explanation The match criteria for a policy consists of a name-value pairing that matches one of the name-value attributes that form the name of the high availability group that is associated with this policy. The value portion of the match criteria for the specified policy is not a valid value for the specified policy.
Action Specify a valid string for the match criteria's Value property such that the combination of the values specified for the Name and Value properties match one of the name-value attributes that form the name of the high availability group that is associated with this policy.

CHKW7219E: The node name of a core group server having {0} as the server name is missing.

Explanation The configuration settings for the specified core group server do not include a value for the Node property .
Action Specify a valid node name for the core group server Node property.

CHKW7220E: The node name {0} of a core group server having {1} as the server name is not valid.

Explanation The Node propery setting for The configuration settings for the specified core group server do not include a valid node name for the Node property. The node name must follow the Application Server managed object naming conventions.
Action Specify a valid node name for the Node property for this core group server.

CHKW7221E: The server name of a core group server having {0} as the node name is missing.

Explanation The configuration settings for a core group server do not include a value for the Server property.
Action Use the administrative console to identify the core group server for which a server name was not specified and specify a server name for the Server property for that core group server.

CHKW7222E: The server name {0} of a core group server having {1} as the node name is not valid.

Explanation he configuration settings for a core group server do not include a valid value for the Server property. The server name must follow the Application Server managed object naming conventions.
Action Specify a valid server name for the Server property for this core group server.

CHKW7223I: No core group servers are associated with the core group {0}.

Explanation For a core group to be usable, at least one core group server must be defined for the core group.
Action You should define one or more servers as belonging to this core group.

CHKW7224I: No preferred coordinator servers are associated with core group {0}.

Explanation Before coordinator execution can occur in designated servers, at least one preferred coordinator server must be defined for this core group.
Action To run coordinators in designated servers, you should designate at least one core group server as a preferred coordinator server.

CHKW7225I: No high-availability manager policies are associated with the core group {0}.

Explanation Before a core group can be usable, it must be associated with at least one high availability manager policy.
Action Associate at least one high availability manager policy with the specified core group.

CHKW7226I: No preferred servers are associated with the preferred server policy {0}.

Explanation No preferred servers are defined for the specified policy.
Action If you want the applications that are running under the specified policy to run on a specific set of servers, designate these servers as preferred servers for the specified policy.

CHKW7227E: No servers are associated with the static policy {0}.

Explanation Before an application can run under the static policy, at least one server must be specified as a preferred server for the static policy.
Action Designate at least one server as a preferred server for the specified static policy.

CHKW7228I: No match criteria is associated with the high-availability manager policy {0}.

Explanation Before a high availability manager policy can be used, at least one match criteria must be set for that policy. No match criteria has been set for the specified policy.
Action Specify one or more valid match criteria for the specified policy. A valid match criteria for a policy consists of a name-value pairing that matches one of the name-value attributes that form the name of the high availability group that is associated with this policy.

CHKW7229I: No useful match criteria is associated with the high-availability manager policy {0}.

Explanation A valid match criteria must be defined for a policy before the high availability manager can use that policy to govern the associated core group.
Action Specify one or more valid match criteria for the specified policy.

CHKW7230E: The high-availability manager policies {0} and {1} are considered the same. Both have the same set of match criteria.

Explanation Each high availability manager policy that is associated with the same core group must must be defined with a unique match criteria.
Action Change the match criteria for one of the specified policies, such that each policy within the scope of the core group is associated with a unique match critera.

CHKW7231E: More than one high-availability manager policy having the same name {0}, is associated with the core group named {1}.

Explanation Each high availability manager policy that is associated with the same core group, must have a unique name.
Action Change the name of one of the policies that currently have duplicate names, such that each policy within the scope of the core group has a unique name.

CHKW7232E: More then one match criteria having the same name {0}, is associated with the high-availability manager policy named {1}.

Explanation Each match criteria within the scope of a high availability manager policy must be assigned a unique name .
Action Change the name of one of the match criterium that currently have duplicate names, such that each match criteria within the scope of the high availability manager has a unique name.

CHKW7233E: More than one core group server associated with the core group named {2}, has the same node name {0}, and server name {1}.

Explanation The combined node name and server name specified for a core group member must be unqiue within that core group.
Action Change the name of one of the servers that currently have duplicate server names such that the new name is unique within the node, or move one of these servers to a different node. If you move one of the servers to a different node, make sure that the name of that server is unique on the new node.

CHKW7234E: More than one preferred coordinator server associated with the core group named {2}, has the same node name {0}, and server name {1}.

Explanation The combined node name and server name specified for a preferred coordinator server must be unique within a core group.
Action Change the name of one of the preferred coordinators that currently have duplicate server names, such that the new name is unique within the node, or move one of these preferred coordinators to a different node. If you move one of the preferred coordinators to a different node, make sure that the name of that server is unique on the new node.

CHKW7235E: More than one preferred server associated with the preferred server.policy named {2}, has the same node name {0}, and server name {1}.

Explanation The combined node name and server name specified for a preferred server must be unique within the scope of a preferred server.policy.
Action Change the name of one of the preferred servers that currently have duplicate server names, such that the new name is unique within the node, or move one of these preferred servers to a different node. If you move one of the preferred servers to a different node, make sure that the name of that server is unique on the new node.

CHKW7236E: More than one server associated with the static policy named {2}, has the same node name {0}, and server name {1}.

Explanation The combined node name and server name specified for each of the servers attached to a static policy must be unique.
Action Change the name of one of the servers that currently have duplicate server names, such that the new name is unique within the node, or move one of these servers to a different node. If you move one of the preferred servers to a different node, make sure that the name of that server is unique on the new node.

CHKW7237I: The value {0} specified for the number of coordinators for the core group named {1} is not within a supported range.

Explanation The value specified for the core group property Number of coordinators must be at least 1 and cannot exceed the number of servers that are defined as members of the specified core group.
Action Change the value specified for the Number of coordinators property to a valid number.

CHKW7238I: The value {0} specified for the number of active servers for the MOfN policy named {1} is not within a supported range.

Explanation The value specified for the Active servers property for an M of N policy that is associated with a core group must be at least 1 and cannot exceed the number of servers that are defined as members of the specified core group
Action Change the value specified for the Active servers property to a valid number.

CHKW7239E: The multicast port value {0}, specified for the core group named {1}, is too low. The value must be at least {2}.

Explanation The value specified for the Multicast port property for the specified core group must be the number of an available port.
Action Change the value specified for the Multicast port property to a valid port number.

CHKW7240E: The policy factory name {0} specified for the high-availability manager policy named {1} is not valid. The policy factory name must be {2}.

Explanation Each category of high availability policy has a corresponding policy factory.
Action Change the policy factory name that is associated with the specified policy to the suggested policy factory name.

CHKW7241E: The preferred coordinator server having node name {0}, and server name {1} that is associated with core group named {2}, is not a core group server.

Explanation The set of preferred coordinator servers must be a subset of of the servers that are defined as members of this core group. The specified preferred coordinatior is not a member of this core group.
Action Make sure that all of the servers specified as preferred coordinator servers, are members of this core group.

CHKW7242E: The preferred server with node name {0} and server name {1} that is associated with the preferred server.policy named {2}, is not a core group server.

Explanation The set of preferred servers, that are associated with the specified preferred server policy, must be a subset of of the servers that are defined as members of this core group. The specified preferred server is not a member of this core group.
Action Make sure that all of the preferred servers, that are associated with the specified preferred server policy, are members of this core group.

CHKW7243E: The server with node name {0}, and server name {1} that is associated with the static policy named {2}, is not a core group server.

Explanation The set of servers, that are associated with the specified static policy, must be a subset of of the servers that are defined as members of this core group. The specified preferred server is not a member of this core group.
Action Make sure that all of the servers, that are associated with the specified static policy, are members of this core group

CHKW7244E: The custom property name {0}, beneath {1}, is duplicated.

Explanation The indicated list of custom properties includes two properties that have the same name. All of the custom properties, that are within a list of custom properties, must have unique names.
Action Either change the name of one of the duplicate custom properties, or remove one of the duplicate properties from the list of custom.

CHKW7245E: The name of a custom property beneath {0} is missing.

Explanation A custom property was defined, but no value was specified for the Name property.
Action Specify a name for the custom property.

CHKW7246E: The custom property name {0}, beneath a core group server is duplicated.

Explanation The list of custom properties for a core group server includes two properties that have the same name. All of the custom properties, that are within a list of custom properties, must have unique names.
Action Either change the name of one of the duplicate custom properties, or remove one of the duplicate properties from the list of custom.

CHKW7247E: The name of a custom property beneath a core group server is missing.

Explanation A custom property was defined for a core group server, but no value was specified for the Name property.
Action Specify a name for the custom property.

CHKW7248E: The name of the channnel-chain in core group named {0} is missing.

Explanation If Channel framework is selected as the transport type for a core group, a transport channel must be selected from the list of available transport channels.
Action Use the administrative console to select a transport channel from the list of transport channels that are available for this core group to use.

CHKW7271E: The core group server with node name {0} and server name {1} that is associated with core group named {2}, does not exist.

Explanation A server must be defined as part of a cell before it can be with a core group that resides within that cell.
Action Select a server, that is defined as part of the cell in which the core group reside, to associate with this core group.

+
Search Tips | Advanced Search

Explanation	No additional information is available.
Action	No action is required.

Explanation	The product configuration document does not include the name of the core group stored in the specified location.
Action	Add the name of this core group to the product configuration document.

Explanation	The core group name must follow the product's managed object naming conventions. The specified core group name does not follow these conventions.
Action	Specify a valid name for this core group.

Explanation	If a core group is going to use a multicast transport, the transport settings must include a value for the Multicast group IP start property. This value should be the the lowest IP address in the range of IP addresses that are available for the core group to use. The multicast transport configuration for the specified core group does not include a value for the Multicast group IP start property.
Action	Specify a value for the Multicast group IP start property.

Explanation	The only transport types that can be specified for a core group are CHANNEL_FRAMEWORK, UNICAST, or MULITICAST.
Action	Select either CHANNEL_FRAMEWORK, UNICAST, or MULITICAST for the core group's Transport type setting.

Explanation	The configuration settings for the specified high availability manager policy does not include a valid value for the Is alive timer property .
Action	Update the configuration settings for the specified high availability manager policy to include a valid value for the Is alive timer property.

Explanation	A high availability manager policy must have an appropriate policy factory.
Action	Provide an appropriate policy factory name for the specified high availability manager policy.

Explanation	All high availability manager policies that are attached to a core group must have valid and unique names.
Action	Make sure that all of the policies associated with a valid and unique name for the high availability policy of concern.

Explanation	The name of a high availability manager policy must follow the Application Server managed object naming conventions.
Action	Make sure that valid and unique names have been given to all of the policies associated with the specified core group.

Explanation	The match criteria for a policy consists of a name-value pairing that matches one of the name-value attributes that form the name of the high availability group that is associated with this policy. The match criteria for the specified policy does not include the name portion of the pairing.
Action	Specify a valid string for the match criteria's Name property such that the combination of the values specified for the Name and Value properties match one of the name-value attributes that form the name of the high availability group that is associated with this policy.

Explanation	The Node propery setting for The configuration settings for the specified core group server do not include a valid node name for the Node property. The node name must follow the Application Server managed object naming conventions.
Action	Specify a valid node name for the Node property for this core group server.

Explanation	The configuration settings for a core group server do not include a value for the Server property.
Action	Use the administrative console to identify the core group server for which a server name was not specified and specify a server name for the Server property for that core group server.

Explanation	he configuration settings for a core group server do not include a valid value for the Server property. The server name must follow the Application Server managed object naming conventions.
Action	Specify a valid server name for the Server property for this core group server.

Explanation	For a core group to be usable, at least one core group server must be defined for the core group.
Action	You should define one or more servers as belonging to this core group.

Explanation	Before coordinator execution can occur in designated servers, at least one preferred coordinator server must be defined for this core group.
Action	To run coordinators in designated servers, you should designate at least one core group server as a preferred coordinator server.

Explanation	Before a core group can be usable, it must be associated with at least one high availability manager policy.
Action	Associate at least one high availability manager policy with the specified core group.

Explanation	No preferred servers are defined for the specified policy.
Action	If you want the applications that are running under the specified policy to run on a specific set of servers, designate these servers as preferred servers for the specified policy.

Explanation	Before an application can run under the static policy, at least one server must be specified as a preferred server for the static policy.
Action	Designate at least one server as a preferred server for the specified static policy.

Explanation	Before a high availability manager policy can be used, at least one match criteria must be set for that policy. No match criteria has been set for the specified policy.
Action	Specify one or more valid match criteria for the specified policy. A valid match criteria for a policy consists of a name-value pairing that matches one of the name-value attributes that form the name of the high availability group that is associated with this policy.

Explanation	A valid match criteria must be defined for a policy before the high availability manager can use that policy to govern the associated core group.
Action	Specify one or more valid match criteria for the specified policy.

Explanation	Each high availability manager policy that is associated with the same core group must must be defined with a unique match criteria.
Action	Change the match criteria for one of the specified policies, such that each policy within the scope of the core group is associated with a unique match critera.

Explanation	Each match criteria within the scope of a high availability manager policy must be assigned a unique name .
Action	Change the name of one of the match criterium that currently have duplicate names, such that each match criteria within the scope of the high availability manager has a unique name.

Explanation	The combined node name and server name specified for a core group member must be unqiue within that core group.
Action	Change the name of one of the servers that currently have duplicate server names such that the new name is unique within the node, or move one of these servers to a different node. If you move one of the servers to a different node, make sure that the name of that server is unique on the new node.

Explanation	The value specified for the core group property Number of coordinators must be at least 1 and cannot exceed the number of servers that are defined as members of the specified core group.
Action	Change the value specified for the Number of coordinators property to a valid number.

Explanation	The value specified for the Active servers property for an M of N policy that is associated with a core group must be at least 1 and cannot exceed the number of servers that are defined as members of the specified core group
Action	Change the value specified for the Active servers property to a valid number.

Explanation	The value specified for the Multicast port property for the specified core group must be the number of an available port.
Action	Change the value specified for the Multicast port property to a valid port number.

Explanation	Each category of high availability policy has a corresponding policy factory.
Action	Change the policy factory name that is associated with the specified policy to the suggested policy factory name.

Explanation	The set of preferred coordinator servers must be a subset of of the servers that are defined as members of this core group. The specified preferred coordinatior is not a member of this core group.
Action	Make sure that all of the servers specified as preferred coordinator servers, are members of this core group.

Explanation	The set of preferred servers, that are associated with the specified preferred server policy, must be a subset of of the servers that are defined as members of this core group. The specified preferred server is not a member of this core group.
Action	Make sure that all of the preferred servers, that are associated with the specified preferred server policy, are members of this core group.

Explanation	The set of servers, that are associated with the specified static policy, must be a subset of of the servers that are defined as members of this core group. The specified preferred server is not a member of this core group.
Action	Make sure that all of the servers, that are associated with the specified static policy, are members of this core group