Express (Distributed operating systems), v8.0 > Reference > Messages
ADMS
ADMS0001I: The system is setting automatic synchronization interval to {0} minutes.
Explanation This informational message indicates that the requested automatic synchronization interval is being set. Action No action is required.
ADMS0002W: The system Cannot set the automatic synchronization interval to the requested value. {0} minutes is not a valid interval value.
Explanation An attempt was made to set the automatic synchronization interval to a negative value. The value must be a positive number of minutes. Action Retry the operation with a valid interval value.
ADMS0003I: The configuration synchronization completed successfully.
Explanation Any new and modified configuration files are successfully moved from the dmgr to the node. Action No user action is required.
ADMS0005E: The system is unable to generate synchronization request: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
ADMS0009W: The data in the synchronization element is not valid: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
ADMS0012E: The system is unable to create an administrative client connection: {0}.
Explanation The node agent cannot connect to the dmgr during a synchronization. This error can result from the dmgr being stopped, or can result from a network error. Action Restart the dmgr or correct the network error.
ADMS0013I: The system detects {0} CellSync objects.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
ADMS0014W: The system is unable to send synchronization completion notification: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
ADMS0015E: The synchronization request cannot be completed because the node agent cannot communicate with the dmgr.
Explanation The node agent cannot establish a connection to the dmgr. The dmgr process is probably not running. Action Check the state of the dmgr process. Restart the dmgr.
ADMS0017I: An unexpected error occurred while trying to initiate automatic synchronization.
Explanation Automatic synchronization is not starting successfully. We can use manual synchronization to move configuration files to the node. Action More info at:
ADMS0018I: The automatic synchronization mode is enabled.
Explanation This informational message indicates a change in the synchronization mode. Action No user action is required.
ADMS0019I: Automatic synchronization mode is disabled.
Explanation This informational message indicates a change in the synchronization mode. Action No user action is required.
ADMS0020E: A synchronization operation received an exception from the repository while updating document {0}. {1}
Explanation The synchronization operation can continue, but the repository update for the indicated document is not made. Action The situation might correct itself on the next synchronization. If not, examine the repository exception and take appropriate action.
ADMS0021I: The system detects {0} cell repository objects.
Explanation None Action None
ADMS0022W: The system is unable to send synchronization initiation notification: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
ADMS0023I: A synchronization operation reached the iteration limit.
Explanation If the cell repository is updated during a synchronization, the operation iterates to pick up the new updates. In this case, the repository has been updated multiple times and the synchronization operation has iterated the maximum number of times, possibly without picking up all of the updates. Action If automatic synchronization mode is in effect, do nothing. The next synchronization will pick up any remaining updates that might have been missed. If automatic synchronization is disabled, invoke another synchronization.
ADMS0024W: An unexpected exception occurred when setting up resource. {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
ADMS0025W: An Unexpected exception occurred in onChangeStart processing: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
ADMS0026E: An unexpected exception occurred in onChangeCompletion processing: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
ADMS0027W: An unexpected exception occurred when checking if {0} is a resource adapter archive (RAR) file: {1}. This file might not be synchronized properly. The stand-alone RAR binaries might not be removed correctly.
Explanation The exception message might detail a probable cause. Action Remove the RAR binary manually.
ADMS0028E: An unexpected exception {0} occurred in building the cache for J2CResourceAdapter synchronization from the resources.xml file. The application synchronization logic does not work for deletions or modifications of binaries in this case.
Explanation The exception message might detail a probable cause. Action Delete the uninstalled resource adapter archive (RAR) file manually.
ADMS0029W: An unexpected exception occurred loading resource {0} from the repository. This error causes additional problems in using this resource for synchronization.
Explanation The specified resource file failed to load. This problem is due to an internal error. Action Turn on the debug trace to get more information about the exception.
ADMS0030E: An unexpected exception occurred in postProcess processing ID={1}: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
ADMS0031E: An exception {0} occurred when deleting directory {1}
Explanation The exception message might detail probable cause. Action Delete the directory manually.
ADMS0036E: The configuration synchronization failed.
Explanation Configuration files cannot be synchronized between the dmgr and the node. Action Look at the other log entries to get information on the specific error. The dmgr might be unreachable.
ADMS0100E: An error occurred when activating MBean: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
ADMS0101E: The system is unable to get a configuration repository client.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
ADMS0104I: The system is unable to invoke a synchronization request on node {0}. {1}
Explanation The system cannot send the synchronization request to the indicated node. This problem most likely occurred because the node agent is not running. Action Start the node agent.
ADMS0107E: An exception occurred while finding the target synchronization object for node {0}. {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
ADMS0109I: The system detects {0} node synchronization objects for node {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
ADMS0110E: An exception occurred getting the security credentials. {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
ADMS0111I: The system is unable to find the target synchronization object for node {1}.
Explanation The system cannot locate the NodeSync MBean for the indicated node. This problem most likely occurred because the node agent is not running. Action Start the node agent.
ADMS0200I: The configuration synchronization started for cell.
Explanation The synchronization operation across all the active nodes has begun. Action None
ADMS0201I: The configuration synchronization started for node: {0}.
Explanation Configuration Synchronization hsa being for the stated node. Action None
ADMS0202I: Automatic synchronization mode is disabled for node: {0}.
Explanation During the course of this synchronization event, Auto Synchronization is disabled, it will be re-enabled later. Action None
ADMS0203I: The automatic synchronization mode is enabled for node: {0}.
Explanation During the course of this synchronization, automatic synchronization was disabled, it is now re-enabled Action None
ADMS0204E: The system is unable to generate synchronization request for node: {0}. Another node synchronization operation might be in progress on the same node.
Explanation The dmgr was unable to generate a request to the nodeagent residing on the stated node. Action Check the logs in dmgr and nodeagent
ADMS0205I: The configuration synchronization completed successfully for node: {0}.
Explanation Configuration synchronization is complete for the stated node. Action None
ADMS0206I: The configuration synchronization failed for node: {0}.
Explanation Configuration synchronization failed for the stated node. Action Check the logs in dmgr and nodeagent
ADMS0207I: Node Synchronization state for node: {0} - {1}
Explanation This is current state of the synchronization in process Action None
ADMS0208I: The configuration synchronization complete for cell.
Explanation This is the final event that will appear, the synchronization for all active nodes is complete Action None
ADMS0209W: The configuration synchronization complete for cell, errors occurred.
Explanation This is the final event that will appear, the synchronization for all active nodes is complete. Some errors did occur. Action Check the logs and previous events
ADMS0210E: Unable to check Node Synchronization state for node: {0} declaring failed.
Explanation An error occurred when checking the synchronization state, the synchronization to that node has been declared failed. Action Check the logs and previous events
ADMS0211I: Re-enabling automatic synchronization mode after successful sync operation
Explanation Automatic synchronization is enabled again when synchronization can be carried out successfully Action None
ADMS0212I: Disabling automatic synchronization mode after 5 consecutive failures to synchronize
Explanation Automatic synchronization is disabled due to continued synchronization failures Action Check for system anomalis that caused the synchronization failures and correct the condition
ADMS0213E: The dmgr did not reapply automatic synchronization on the {0} node.
Explanation An error occurred when the dmgr tried to reapply automatic synchronization on the node. Action Using wsadmin tooling, call the setAttribute action and set the autoSyncEnabled attribute to true on the NodeSync MBean for this node.