WebSphere Process Server messages     Operating Systems: All supported
CHKP0023E: {0} is an invalid run-as attribute.
Explanation: A run-as attribute is invalid. If the configuration is not corrected, then the run time will use the default locale of the process. Refer to the Internationalization service documentation.
User Action: A valid run-as attribute, when set to Specified, specifies at least one valid locale and a valid time zone ID. Modify the run-as configuration according to the Internationalization service documentation.

 

CHKP0024I: The enterprise configuration for {0} is being validated.
Explanation: The assembly tool is beginning the process of validating the configuration for the referenced component.
User Action: No user action is required.

 

CHKP1000E: An object of an unrecognized type was encountered while validating {0}. The received object type is {1}.
Explanation: No additional information is available.
User Action: Use either the administration application or the command line scripting tool to update the part of the configuration that is in error.

 

CHKP1001E: No configuration information is present in {0}.
Explanation: No additional information is available.
User Action: Use either the administration application or the command line scripting tool to update the part of the configuration that is in error.

 

CHKP1002E: Multiple roots were found in {0}.
Explanation: No additional information is available.
User Action: Use either the administration application or the command line scripting tool to update the part of the configuration that is in error.

 

CHKP1003E: A root object in {0} is not the correct type. (The root object is type {1}. The expected object type is {2}.)
Explanation: No additional information is available.
User Action: Use either the administration application or the command line scripting tool to update the part of the configuration that is in error.

 

CHKP1004E: A required attribute of {0} is missing. The attribute {1} must have a value.
Explanation: No additional information is available.
User Action: Use either the administration application or the command line scripting tool to update the part of the configuration that is in error.

 

CHKP1005E: A required relationship of {0} is missing. The relationship with role name {1} must have a value.
Explanation: No additional information is available.
User Action: Use either the administration application or the command line scripting tool to update the part of the configuration that is in error.

 

CHKP1006E: An attribute of {0} has an invalid value. {1} should have a value of one of the following: {2}.
Explanation: No additional information is available.
User Action: Use either the administration application or the command line scripting tool to update the part of the configuration that is in error.

 

CHKP1007E: An attribute of {0} is out of range. {1} needs a value between {2} and {3}.
Explanation: No additional information is available.
User Action: Use either the administration application or the command line scripting tool to update the part of the configuration that is in error.

 

CHKP1008E: The alias {0} to the JAASAuthData entry, specified for {1} {2}, matches no configured JAASAuthData entries in the security.xml file.
Explanation: No additional information is available.
User Action: Use either the administration application or the command line scripting tool to update the part of the configuration that is in error.

 

CHKP1009E: Performance Monitoring Infrastructure (PMI) must be enabled on all cluster members and on all nodeagents of the nodes on which the cluster members are located before WebSphereDynamicWeighting can be set for cluster {0}.
Explanation: The WeightAdvisor uses Performance Monitoring Infrastructure (PMI) for determining relative cluster member health and performance. For WebSphereDynamicWeighting to be enabled, the Performance Monitoring Service must be enabled on all nodeagents and cluster members associated with the cluster. See the WebSphere Enterprise Information Center for further details.
User Action: Use either the administration application or the command line scripting tool to set the Performance Monitoring Service to start at startup for all members of cluster {1} and all nodeagents of all the nodes on which the cluster members are located.

 

CHKP1010E: {0} has been configured multiple times with {1}.
Explanation: No additional information is available.
User Action: Use a WebSphere assembly tool to update the configuration.

 

CHKP1011E: A required attribute of {0} is missing. The attribute {1} must have a value.
Explanation: No additional information is available.
User Action: Use a WebSphere assembly tool to update the configuration.

 

CHKP1012E: A configured reference {0} cannot be resolved. The attribute {1} requires a valid reference.
Explanation: No additional information is available.
User Action: Use a WebSphere assembly tool to update the configuration.

 

CHKP1013E: An attribute of {0} is out of range. {1} needs a value between {2} and {3}.
Explanation: No additional information is available.
User Action: Use a WebSphere assembly tool to update the configuration.

 

CHKP1014E: The attribute {0} cannot be configured on {1}.
Explanation: No additional information is available.
User Action: Use a WebSphere assembly tool to update the configuration.

 

CHKP1015E: {0} is not configured with an appropriate container managed policy to support the attribute {1}.
Explanation: No additional information is available.
User Action: Use a WebSphere assembly tool to update the configuration.

 

CHKP1016E: The time zone {0}, {1} is invalid.
Explanation: A specified time zone ID is invalid. If the configuration is not corrected, the runtime will use the default time zone of the process. Refer to the Internationalization service documentation.
User Action: A valid time zone ID identifies any time zone supported by SDK class java.util.TimeZone. Time zone ID can be a custom ID having format GMT[+|-]hh[[:]mm], or any ID returned by method java.util.TimeZone.getAvailableIDs(). Modify the time zone ID according to the documentation for the internationalization service.

 

CHKP1017E: Locale {0}, {1} is invalid.
Explanation: A specified locale is invalid. If the configuration is not corrected, the runtime will use the default locale of the process. Refer to the documentation for the internationalization service.
User Action: A valid locale contains at least a language code or a country code. A language code is preferrably a valid ISO 639 language code, and a country code is preferrably a valid ISO 3166 country code. Modify the locale configuration according to the Internationalization service documentation.

 

CHKP1018I: The default access intent policy named {0} and assigned to the entity {1} was originally configured only for dynamic query.
Explanation: An access intent policy was created in a previous version of WebSphere to act as the the default intent for dynamic queries. This configuration will be treated as the default access intent for all requests upon this entity, including dynamic query.
User Action: Rename the policy to DEFAULT by using the version of the assembly tool that was used to create the access intent policy for the dynamic query.

 

CHKP1019I: {0} is a recursive read ahead hint and might be ignored at run time.
Explanation: No additional information is available.
User Action: No user action is required.

 

CHKP1020I: {0} includes entities using inheritance and might be ignored at runtime.
Explanation: No additional information is available.
User Action: No user action is required.

 

CHKP1021I: {0} includes entities that are configured in an application profile to load with different access intent policies.
Explanation: All entities referenced in a read ahead hint must be configured in an application profile with the same access intent.
User Action: Use a WebSphere assembly tool to configure all entities in the read ahead hint with the same access intent.

 

CHKP1022E: {0} is configured on {1}; it cannot also be configured on {2}.
Explanation: No additional information is available.
User Action: Use a WebSphere assembly tool to update the configuration.

 


Reference topic

Terms of use | Feedback

Timestamp icon Last updated: 9 June 2009