WebSphere Management SubsystemADMS0001I: Setting automatic synchronization interval to {0} minutes.
Explanation
This is an informational message.
User Response:
No action is necessary.
ADMS0002W: Cannot set automatic synchronization interval to 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.
User Response:
Retry the operation with a valid interval value.
ADMS0003I: Configuration synchronization completed successfully.
Explanation
Any new and modified configuration files were successfully moved from the deployment manager to the node.
User Response:
No action is necessary
ADMS0005E: Unable to generate synchronization request: {0}.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMS0009W: Data in synchronization element is not valid: {0}.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMS0012E: Unable to create administrative client connection: {0}.
Explanation
The node agent was unable to connect to the deployment manager during a synchronization.
User Response:
This is likely the result of the deployment manager being stopped. It may also be caused by a network error. Restart the deployment manager or correct the network error.
ADMS0013I: There are {0} CellSync objects.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMS0014W: Unable to send synchronization completion notification: {0}.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMS0015E: The synchronization request can not be completed because the node agent can not communicate with the deployment manager.
Explanation
The node agent is unable to establish a connection to the deployment manager. The deployment manager's process is probably not running.
User Response:
Check the state of the deployment manager's process. Restart the deployment manager.
ADMS0016I: Configuration synchronization failed.
Explanation
Configuration files could not be synchronized between the deployment manager and the node.
User Response:
Look at the other log entries to get information on the specific error. One common reason is that the deployment manager is unreachable.
ADMS0017I: An unexpected error occurred while trying to initiate automatic synchronization.
Explanation
Automatic synchronization is not being started successfully. Manual synchronization can be used to move configuration files to the node.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMS0018I: Automatic synchronization mode is enabled.
Explanation
This is an informational message indicating a change in the synchronization mode.
User Response:
No action is necessary.
ADMS0019I: Automatic synchronization mode is disabled.
Explanation
This is an informational message indicating a change in the synchronization mode.
User Response:
No action is necessary.
ADMS0020E: A synchronization operation received an exception from the repository while updating document {0}. {1}
Explanation
The synchronization operation will continue but the repository update for the indicated document was not made.
User Response:
The situation may correct itself on the next synchronization. If not, examine the repository exception and take appropriate action.
ADMS0021I: There are {0} cell repository objects.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMS0022W: Unable to send synchronization initiation notification: {0}.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMS0023I: A synchronization operation reached the iteration limit.
Explanation
If the cell repository is updated during a synchronization the operation iterates in order 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.
User Response:
If automatic synchronization mode is in effect, do nothing; the next synchronization will pick up any remaining updates that may have been missed. If automatic synchronization is disabled, invoke another synchronization.
ADMS0100E: Error activating MBean: {0}.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMS0101E: Unable to get a configuration repository client.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMS0104I: Unable to invoke synchronization request on node {0}. {1}
Explanation
The system was unable to send the synchronization request to the indicated node. This is most likely because the node agent is not running.
User Response:
Start the node agent.
ADMS0107E: Exception while finding target synchronization object for node {0}. {1}
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMS0109I: There are {0} node synchronization objects for node {1}.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMS0110E: An exception occurred getting the security credentials. {0}
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
ADMS0111I: Unable to find target synchronization object for node {1}.
Explanation
The system was unable to locate the NodeSync MBean for the indicated node. This is most likely because the node agent is not running.
User Response:
Start the node agent.