Explanation | The HA Manager communication transport has been started |
Action | None. Informational entry. |
Explanation | This server is not a member of the core group. If this server should be a member of a core group, repair the configuration document. |
Action | An informational message. |
Explanation | The indicated service could not be exported. Recovery was not possible. |
Action | Look for previous messages in the log related to initialization failure and analyze them first. If the problem cannot be determined, contact IBM Service |
Explanation | A Management Bean failed to start. |
Action | Contact IBM Service. |
Explanation | The HA Manager communication transport has been started |
Action | None. Informational entry. |
Explanation | The HA Manager communication transport is starting. |
Action | None. Informational entry. |
Explanation | A Management Bean failed to start. |
Action | Contact IBM Service. |
Explanation | The configuration xml file could not be found, is corrupted or there is a problem with the repository service. |
Action | Contact IBM service. |
Explanation | The core group configuration document is corrupt or contains a syntax error. |
Action | Contact IBM Service. |
Explanation | An invalid configuration state was encountered. An attribute could not be read. |
Action | Correct the configuration state. |
Explanation | An invalid configuration state was encountered. An attribute could not be read. |
Action | Correct the configuration state. |
Explanation | Unable to resolve the IP address for the indicated host. Either the host is unknown or has mappings only to duplicate IP addresses. |
Action | See the exception for more detail. Correct the host name lookup problem and retry. |
Explanation | An invalid value for an attribute was detected. A default value has been assigned. |
Action | Correct the attributes value and retry. |
Explanation | An invalid value for an attribute was detected. A default value has been assigned. |
Action | Correct the attributes value and retry. |
Explanation | An IP Address that maps to multiple hosts is unusual. The duplicate mapping may be intentional and required to support another product such as the IBM Edge load balancer. |
Action | If the duplicate mapping is unintentional, fix it. If the mapping is intentional, configure the DCS_UNICAST_ADDRESS endpoints for all processes in the core group to use a specific, unique IP Address. |
Explanation | Multiple processes on the same host cannot be configured to use the same port. |
Action | Correct the problem by changing the port assignment for one of the members. |
Explanation | The configuration xml file could not be found, is corrupted or there is a problem with the repository service. |
Action | Contact IBM service. |
Explanation | The core group for this server did not contain any HA Policies when read. |
Action | An informational message. If no policies are assigned for the core group, no action is required. |
Explanation | All HA Policies must have a unique name. |
Action | Correct the problem by assigning a name for the policy. |
Explanation | An invalid configuration state was encountered. An HA Manager policy could not be read. |
Action | Correct the configuration state. |
Explanation | HA Policies were located in the core group but none were successfully parsed.. |
Action | Correct the configuration state. |
Explanation | See the exception for more information about the root cause of the problem. |
Action | Correct the cause of the problem or contact IBM Service. |
Explanation | The server list for the policy is empty. |
Action | Correct the configuration state. |
Explanation | The name of the Policy Factory specified in the configuration data is incorrect. |
Action | Enter a valid PolicyFactory class name. |
Explanation | The name of the Policy Factory specified in the configuration data is incorrect. |
Action | Either the Policy Factory name is entered incorrectly or the Policy Factory class is not available on this server. Determine which situation has occurred and correct it. |
Explanation | An internal initialization error occurred. |
Action | Contact IBM service. |
Explanation | Two policy definitions with the same name were found. This is not allowed. |
Action | Assign unique names to the policies. |
Explanation | The serverindex.xml file for the specified node appears to be out of date. |
Action | If the problem does not resolve itself, perform a full resynchronize from the master repository. |
Explanation | An incorrect server entry exists in the coregroup configuration document. |
Action | See the exception message for more details regarding the source of the error and correct if possible. Otherwise contact IBM Service. |
Explanation | This end point is required and should be allocated when the process is created. |
Action | Contact IBM Service. |
Explanation | A null or empty String was found. Valid values include the host name, a textual IP address or *. |
Action | Enter the proper host name in this field. |
Explanation | There may be a problem with the host name or DNS resolution. Under normal circumstances, a non-loopback address is expected. |
Action | Fix the host name or DNS problem. |
Explanation | The hamanagerservice configuration document is corrupt or contains a syntax error. |
Action | Contact IBM Service. |
Explanation | The coreGroupName must be set to the core group this server is associated with. Null is not allowed. |
Action | Contact IBM Service. |
Explanation | An unknown problem exists with the ConfigRepository. |
Action | Contact IBM Service. |
Explanation | An unknown problem exists with a configuration document. |
Action | Scan the log for error messages relating to failures in loading the same document and diagnose them. |
Explanation | The core group configuration document is corrupt or contains a syntax error. |
Action | Contact IBM Service. |
Explanation | The core group document is already in use. |
Action | An informational message. |
Explanation | The core group document is being updated. |
Action | An informational message. |
Explanation | Unrecoverable error while updating the core group. |
Action | Synchronize the configuration to the node in question, then restart the server. If this does not solve the problem contact IBM Support. |
Explanation | Policy errors are tolerated when the configuration is read, but prevent policy information from being updated. |
Action | Scan the log for information related to the parsing errors and correct them. |
Explanation | The core group configuration could not be updated correctly. |
Action | Contact IBM Service. |
Explanation | The core group configuration could not be updated correctly. |
Action | Manually synchronize the configuration from the master repository on the Deployment Manager. Application servers on the affected node may need to be recycled. |
Explanation | The core group configuration may not have been updated correctly. |
Action | An informational message. |
Explanation | An activate or deactivate message was received but there are no local members in the group to take action on. This can happen under normal conditions depending on the timing of messages. For example when members are leaving a group, one of them could receive an activate message that was sent just before the member left. |
Action | An informational message only. |
Explanation | An inconsistent internal state was detected. |
Action | No known user actions. The root cause of the problem appears to be an internal error. Contact IBM service. |
Explanation | An inconsistent internal state was detected. |
Action | No known user actions. The root cause of the problem appears to be an internal error. Contact IBM service. |
Explanation | An inconsistent internal state was detected. |
Action | No known user actions. The root cause of the problem appears to be an internal error. Contact IBM service. |
Explanation | An problem occurred while processing an application callback. |
Action | Most likely this is caused by a programming error by the HAManager user. Use the information in the message to find and fix the root cause of the problem. If the root cause cannot be determined, contact IBM service. |
Explanation | An unexpected internal error occurred. See the included exception for more information. |
Action | Examine the stack trace to determine the cause of the exception. If the root cause of the problem cannot be determined, contact IBM service. |
Explanation | An unexpected internal error occurred. See the included exception for more information. |
Action | Examine the stack trace to determine the cause of the exception. If the root cause of the problem cannot be determined, contact IBM service. |
Explanation | A message could not be sent due to a failure in the communication stack. |
Action | Examine the stack trace to determine the cause of the exception. If the root cause of the problem cannot be determined, contact IBM service. |
Explanation | A message could not be sent due to an unrecoverable error. |
Action | Examine the stack trace to determine the cause of the exception. If the root cause of the problem cannot be determined, contact IBM service. |
Explanation | A cluster member which contained quorum sensitive groups has lost quorum but has active members. The process must be terminated. |
Action | Restart the failed servers or fix the network partition. |
Explanation | The GMS service requested termination. The GMS should have logged the reason. |
Action | None. Informational message. |
Explanation | An unexpected error occurred. See the exception stack trace for more detail. |
Action | If the root cause cannot be determined and corrected, contact IBM Service. |
Explanation | An unexpected error occurred. See the exception stack trace for more detail. |
Action | If the root cause cannot be determined and corrected, contact IBM Service. |
Explanation | An unexpected error occurred. See the exception stack trace for more detail. |
Action | If the root cause cannot be determined and corrected, contact IBM Service. |
Explanation | An unusual situation has occured. This may be due to message latency. |
Action | None. An informational message only. |
Explanation | A group member failed to perform the requested action. The group member will be disabled. |
Action | None. An informational message only. |
Explanation | A group member failed to perform the requested action. The group member will be disabled. |
Action | None. An informational message only. |
Explanation | An unusual condition was detected. This condition may be the result of a programming error. |
Action | None An informational message. |
Explanation | The policy for the group initiated a request to activate the group member. The request found that the member is disabled. |
Action | None An informational message. |
Explanation | A programming error was detected. |
Action | None An informational message. |
Explanation | A user-requested activity has been performed. |
Action | None An informational message. |
Explanation | A local group has requested process termination. |
Action | None An informational message. |
Explanation | A local group member appears to be hung. |
Action | None An informational message. |
Explanation | A local group member appears to be incoherent. |
Action | None An informational message. |
Explanation | Quorum is enabled for unknown cluster. |
Action | Contact IBM. |
Explanation | The cluster has services which cannot activate without the cluster having quorum. Normally, each server has a single votes and the majority of the servers must be online for quorum. If the number of servers is even then the first server has 2 votes. |
Action | Start more cluster members to achieve quorum or use wsadmin to force quorum. |
Explanation | This cluster has quorum. |
Action | No action is needed. |
Explanation | This happens because if a cluster is added then its definition is pushed asynchronously to all nodes. Some nodes may not know about a cluster when other do as a result. This will fix itself in seconds. |
Action | If this persists do a manual nodesync on the problem nodes, if this fails then contact IBM. |
Explanation | The default core stack for a process may only be terminated by the High Availability Manager. |
Action | An informational message. |
Explanation | The core stack associated with a Gateway has terminated. |
Action | An informational message. |
Explanation | The core stack received an event not designated for it. The event is ignored. |
Action | An informational message. |
Explanation | The core group membership could not be updated correctly. |
Action | Synchronize the configuration to the node in question, then restart the server. If this does not solve the problem contact IBM Support. |
Explanation | The group state could not be synchronized correctly. |
Action | If the problem does not resolve by itself, stop and start the server. If this does not solve the problem contact IBM Support. |
Explanation | The called component did not detect that an error occurred. |
Action | Determine the failing component from the stack trace and perform diagnostics for that component, or contact IBM Support. |
Explanation | An unrecoverable thread dispatch error has occurred. |
Action | Contact IBM Support. |
Explanation | This server is hosting a member of a critical cluster and was detected as failed. It is being powered down to allow safe failover. |
Action | Check the machine to determine why it failed and if the cause can be remedied then power it back on so it can rejoin the cluster. |
Explanation | This cluster is currently online but the loss of one more cluster member will cause it to panic. |
Action | Bring the other cluster members online or remove the offline cluster members from the cluster administratively to make the cluster non critical. |
Explanation | An internal inconsistency was detected. The inconsistency may affect failover for the indicated group. |
Action | Contact IBM Support. |
Explanation | An error was encountered and group liveness checking cannot continue. Without liveness checking failover may not function properly. |
Action | Contact IBM Support. |
Explanation | The High Availability Manager is running with a secure channel chain. |
Action | None An informational message. |
Explanation | The High Availability Manager has rejected a connection attempt. |
Action | Ensure that global security is either enabled on both processes or disabled on both processes. Ensure that both the sending and receiving processes are members of the same core group. |
Explanation | An unexpected internal error has occurred. |
Action | Contact IBM support. |
Explanation | The core group member list could not be dynamically updated. |
Action | If the problem persists, contact IBM Support. |
Explanation | There are too many runnable threads on the machine. Threads are not being dispatched in a timely manner. This will affect system stability. |
Action | Remove load from the machine until this message disappears. |
Explanation | The channel chain has failed to start. Most likely the necessary port is not available. This can happen if the process was previously terminated abnormally. |
Action | Check the log for other channel related messages. Wait for the operating system to release the port and restart the process. |
Explanation | This server is hosting a member of a critical cluster and was detected as failed. An attempt to power it down to allow safe failover has failed. |
Action | Check the machine to determine why it failed and if the cause can be remedied then power it back on so it can rejoin the cluster. |
Explanation | The group member is not currently in the disabled state. |
Action | Check the current state of the group member. |
Explanation | The group member is in an unknown state. |
Action | Contact IBM Support. |
Explanation | An internal logic error has been detected. |
Action | Contact IBM service. |
Explanation | An internal logic error has been detected. |
Action | Contact IBM service. |
Explanation | An internal logic error has been detected. |
Action | Contact IBM service. |
Explanation | An internal logic error has been detected. |
Action | Contact IBM service. |
Explanation | An internal logic error has been detected. |
Action | Contact IBM service. |
Explanation | An internal logic error has been detected. |
Action | Contact IBM service. |
Explanation | An internal logic error has been detected. |
Action | Contact IBM service. |
Explanation | An internal logic error has been detected. |
Action | Contact IBM service. |
Explanation | An internal logic error has been detected. |
Action | Contact IBM service. |
Explanation | An attempt to send a message failed with a exception in the communication stack. See the included exception for more information. |
Action | Examine the stack trace to determine the cause of the exception. Ensure that all network communications are operating properly. If the root cause of the problem cannot be determined, contact IBM service. |
Explanation | An internal logic error has been detected. |
Action | Contact IBM service. |
Explanation | An internal logic error has been detected. |
Action | Contact IBM service. |
Explanation | An internal logic error has been detected. |
Action | Contact IBM service. |
Explanation | The coordinator in this process has been elected as an active coordinator. |
Action | none. An informational message. |
Explanation | The coordinator in this process is no longer an active coordinator. |
Action | none. An informational message. |
Explanation | An internal logic error has been detected. |
Action | Contact IBM service. |
Explanation | An internal logic error has been detected. |
Action | Contact IBM service. |
Explanation | A change in group state occurred that triggered the application of the policy. The group currently has no members. The group may have been deleted. |
Action | None. An informational message. |
Explanation | The policy for the specified group cannot be found on the server. However, it was available on the server where the join was done. |
Action | None. An informational message. |
Explanation | An internal inconsistency was detected. The message is logged for informational purposes only. |
Action | None. An informational message. Processing will continue. |
Explanation | An internal inconsistency was detected. The message is logged for informational purposes only. |
Action | Contact IBM Service |
Explanation | Processes have been added or removed from the existing view. |
Action | None. An informational message only. |
Explanation | The type of the event is not recognized. The HA Manager does not know how to respond to the event. |
Action | Contact IBM Service. |
Explanation | One of the requested members is not currently a member of the group. |
Action | Select a member in the group and retry the operation. |
Explanation | The member selected as the source is currently not active. |
Action | Select the active member of the group and retry the operation. |
Explanation | The group is currently undergoing a state transition that cannot be interrupted. |
Action | Wait for the transition to complete and retry the operation. |
Explanation | An error was received from the DCS Transport. |
Action | If the error does not resolve itself, contact IBM Service. |
Explanation | The specified value is not legal. |
Action | Consult product documentation to determine legal values for the property. |
Explanation | The specified value is not legal. |
Action | Correct the custom property and retry the operation. |
Explanation | The default value has been overriden by using a custom property. |
Action | An informational message. No action required. |
Explanation | A Core Group Bridge cannot be created on a server that is not part of a network deployment. |
Action | Create the Core Group Bridge on an eligible server. |
Explanation | The coordinator in this process is not an active coordinator. |
Action | none. An informational message. |
Explanation | Processes have been added or removed from the existing view. |
Action | None. An informational message only. |
Explanation | An internal inconsistency was detected. |
Action | Contact IBM Service. |
Explanation | This is an indication of internal state mismatch between coregroup members and should not frequently occur, the message is ignored by the active coordinator. |
Action | Contact IBM service. |
Explanation | An internal inconsistency was detected. The active coordinator ignores the incoming message. |
Action | Contact IBM service. |
Explanation | An internal inconsistency was detected. The active coordinator ignores the incoming message. |
Action | Contact IBM service. |
Explanation | All groups must have exactly one policy rule that matches with it. |
Action | Make sure a policy exists for the group. Create it if it does not. |
Explanation | All groups must have exactly one policy rule that matches with it. |
Action | Make the matchsets for the other policies more specific or remove them so only one policy matches this group. |
Explanation | An unexpected error occurred while creating the data stack. |
Action | Contact IBM Service and provide the appropriate logs. |
Explanation | An unexpected error occurred attempting to send a data stack message. |
Action | Contact IBM Service and provide the appropriate logs. |
Explanation | The data stack implementation detected a failure invoking a method on the registered call back class. |
Action | Use the associated exception's name, message and stack trace to determine the root cause of the failure. If the root cause is due to application error, correct the cause of the failure and retry the operation. If the root cause is due to an internal error, contact IBM service. |
Explanation | A problem occurred trying to process a received data stack message. |
Action | Contact IBM service. |
Explanation | A unknown data stack event was encountered. No harm is caused by this condition, but it is unexpected. |
Action | Contact IBM service. |
Explanation | An unexpected data stack exception occurred. |
Action | Contact IBM service. |
Explanation | An unexpected error occurred attempting to peform a synchronous request for data. |
Action | Contact IBM Service and provide the appropriate logs. |
Explanation | An unexpected synchronous data stack exception occurred. |
Action | Contact IBM service. |
Explanation | The internal data stack of the view synchronous high-availability manager group encountered an unexpected termination event. See the exception stack trace for more detail. |
Action | If the root cause cannot be determined and corrected, contact IBM Service. |
Explanation | Encountered an error while using the internal data stack of the view synchronous high-availability manager group. See the exception stack trace for more detail. |
Action | If the root cause cannot be determined and corrected, contact IBM Service. |
Explanation | The message path of the internal data stack of the view synchronous high-availability manager group has reached its upper congestion limit. |
Action | None. An informational message. |
Explanation | This failure may occur for multiple reasons, including application errors, configuration problems and internal errors. See the associated exception and exception message text. |
Action | Use the associated exception's name, message and stack trace to determine the root cause of the failure. If the root cause is due to application error or configuration error, correct the cause of the failure and retry the operation. If the root cause is due to an internal error, contact IBM service. |
Explanation | This failure is unexpected. Secondary agents may not have been created or destroyed, as expected. |
Action | Contact IBM service. |
Explanation | An internal inconsistency has been detected. |
Action | Contact IBM Service and provide the appropriate logs. |
Explanation | An internal inconsistency has been detected. |
Action | Contact IBM Service and provide the appropriate logs. |
Explanation | An internal inconsistency has been detected. |
Action | Contact IBM Service and provide the appropriate logs. |
Explanation | An internal problem has been detected. |
Action | Contact IBM Service and provide the appropriate logs. |
Explanation | A communication problem was encountered. The message will be retried. |
Action | Ensure that all network paths are operating properly. |
Explanation | An unknown or unexpected problem was encountered. |
Action | Examine the stack trace to determine the root cause of the problem and correct it. If the root cause cannot be determined or is due to an internal error, contact IBM service. |
Explanation | This failure may occur for multiple reasons, including application errors, configuration problems and internal errors. See the associated exception and exception message text. |
Action | Use the associated exception's name, message and stack trace to determine the root cause of the failure. If the root cause is due to application error or configuration error, correct the cause of the failure and retry the operation. If the root cause is due to an internal error, contact IBM service. |
Explanation | When a primary agent is destroyed, the secondary agents associated with the primary are also destroyed. There are multiple reasons that destroy of a secondary may fail including application errors, configuration problems and internal errors. See the associated exception and exception message text. |
Action | Use the associated exception's name, message and stack trace to determine the root cause of the failure. If the root cause is due to application error or configuration error, correct the cause of the failure and retry the operation. If the root cause is due to an internal error, contact IBM service. |
Explanation | This failure may occur for multiple reasons, including application errors, configuration problems and internal errors. See the associated exception and exception message text. |
Action | Use the associated exception's name, message and stack trace to determine the root cause of the failure. If the root cause is due to application error or configuration error, correct the cause of the failure and retry the operation. If the root cause is due to an internal error, contact IBM service. |
Explanation | This failure may occur for multiple reasons., including application errors, configuration problems and internal errors. See the associated exception and exception message text. |
Action | Use the associated exception's name, message and stack trace to determine the root cause of the failure. If the root cause is due to application error or configuration error, correct the cause of the failure and retry the operation. If the root cause is due to an internal error, contact IBM service. |
Explanation | This failure may occur for multiple reasons., including application errors, configuration problems and internal errors. See the associated exception and exception message text. |
Action | Use the associated exception's name, message and stack trace to determine the root cause of the failure. If the root cause is due to application error or configuration error, correct the cause of the failure and retry the operation. If the root cause is due to an internal error, contact IBM service. |
Explanation | This is an internal failure. |
Action | Contact IBM service. |
Explanation | This is an internal failure. |
Action | Contact IBM service. |
Explanation | A communication problem was encountered. The message will be retried. |
Action | Ensure that all network paths are operating properly. |
Explanation | An internal inconsistency has been detected. |
Action | None. Informational only. |
Explanation | A message was sent via the high availability manager Agent framework and received by this member. However, the channel name included in the message does not match any existing AgentClass or Agent channel name. It is possible for this to occur if the receiving component associated with the channel name in the message was destroyed while the message was in flight. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | While performing policy processing, it was discovered that more members of the group are active then should be. |
Action | No action is required. If problem continues, check previous messages for the original source of the problem. |
Explanation | While performing policy processing, it was discovered that the group is not consistent with the policy and corrective actions were unable to make the group consistent with the policy at this time. |
Action | No action is required. If problem continues, check previous messages for the original source of the problem. |
Explanation | While performing policy processing, it was discovered that the group is not consistent with the policy and corrective actions were unable to make the group consistent with the policy at this time. |
Action | This is probably a transient condition that will be resolved when current group members reach a stable state. If problem persists, check for problems with the component corresponding to the group name. |
Explanation | While performing policy processing, it was discovered that the group is not consistent with the policy and corrective actions were unable to make the group consistent with the policy at this time. |
Action | This is probably a transient condition that will be resolved when current group members reach a stable state. If problem persists, check for problems with the component corresponding to the group name. |
Explanation | An HA Manager administrative action was requested and has been logged for informational purposes only. |
Action | None. An informational message. |
Explanation | An HA Manager administrative action was requested and has been logged for informational purposes only. |
Action | None. An informational message. |
Explanation | An HA Manager administrative action was requested and has been logged for informational purposes only. |
Action | None. An informational message. |
Explanation | An HA Manager administrative action was requested and has been logged for informational purposes only. |
Action | None. An informational message. |
Explanation | An asynchronous administrative operation was requested, and during background processing the specified group could not be found. Thus, no action was taken. |
Action | Retry the failing command with a valid GroupName parameter. |
Explanation | An asynchronous administrative operation was requested, and during background processing the specified member could not be found. Thus, no action was taken. |
Action | Retry the failing command with valid Node Name and Server Name parameters. |
Explanation | An asynchronous administrative operation was requested, and during background processing it was determined that the core group membership is changing. Thus, no action was taken. |
Action | Due to the timing of asynchronous operations, it is possible to encounter this situation. Wait for servers in this core group to enter a steady state (e.g. started or stopped) and retry the failing command. |
Explanation | An asynchronous administrative operation was requested, and during background processing it was determined that the specified member or group is not in the correct state for the requested action. Thus, no action was taken. |
Action | Due to the timing of asynchronous operations, it is possible to encounter this situation. Verify the current state of the member or group. If necessary, retry the failing command. |
Explanation | The intended partitioned-manager-group receiver member, may have already left the high-availability manager group. |
Action | None. An informational message. |
Explanation | An unexpected error occurred. See the exception stack trace for more detail. |
Action | If the root cause cannot be determined and corrected, contact IBM Service. |
Explanation | A partitioned manager event handling method passed an unhandled exception to partitioned manager group. See the exception stack trace for more detail. |
Action | If you want this instance of partitioned manager group to be functional, recreate it. |
Explanation | Partitioned manager group received an inbound state-distribution or application message with invalid header. |
Action | If the root cause cannot be determined and corrected, contact IBM Service. |
Explanation | Partitioned manager group received an inbound state-distribution or application message associated with an unexpected header. |
Action | If the root cause cannot be determined and corrected, contact IBM Service. |
Explanation | The partitioned manager group event handler application has requested process termination. |
Action | None. An informational message. |
Explanation | See the exception stack trace for information as to why the action failed. |
Action | Correct the root cause of the problem and retry the operation. If the root cause cannot be determined, contact IBM Service. |
Explanation | See the exception stack trace for information as to why the action failed. |
Action | Correct the root cause of the problem and retry the operation. If the root cause cannot be determined, contact IBM Service. |
Explanation | HA Manager detected that the JVM property ha.workqueue.threshold is configured for this process. |
Action | An informational message. No action required. |
Explanation | HA Manager detected that the work queue dump threshold changed. |
Action | An informational message. No action required. |
Explanation | An inconsistent internal state was detected. Processing cannot continue. |
Action | Contact IBM service. |
Explanation | An inconsistent internal state was detected. Processing cannot continue. |
Action | Contact IBM service. |
Explanation | An internal inconsistency was detected. No recovery was possible. |
Action | Contact IBM Service |
Explanation | An internal inconsistency was detected. No recovery was possible. |
Action | Contact IBM Service. |
Explanation | An inconsistent internal state was detected. Processing should not continue. |
Action | Contact IBM service. |
Explanation | An inconsistent internal state was detected. Processing should not continue. |
Action | Contact IBM service. |
Explanation | A DCS operation was requested, but the DCS provider has not been initialized. |
Action | Contact IBM service. |
Explanation | A DCS operation was requested, but the caller has no identity. |
Action | Contact IBM service. |
Explanation | A bulletin board operation failed. |
Action | Contact IBM service. |
Explanation | A configuration update operation failed. |
Action | Contact IBM service. |
Explanation | A streaming operation failed. |
Action | Contact IBM service. |
Explanation | An initialization operation failed. |
Action | Contact IBM service. |
Explanation | An internal inconsistency was detected. No recovery was possible. |
Action | Contact IBM Service. |
Explanation | An unexpected condition occurred. |
Action | Check the stack trace for a message that may help indicate the cause of the problem. If the problem cannot be solved, contact IBM Service. |
Explanation | An inconsistent internal state has been detected. |
Action | Contact IBM Support. |
Explanation | An unrecoverable error has been detected. |
Action | Contact IBM Support. |
Explanation | An unrecoverable error has been detected. |
Action | Contact IBM Support. |