WebSphere Process Server messages     Operating Systems: All supported

ADMS

ADMS0001I: The system is setting automatic synchronization interval to {0} minutes.
Problem This informational message indicates that the requested automatic synchronization interval is being set.
User response 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.
Problem 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: The configuration synchronization completed successfully.
Problem Any new and modified configuration files are successfully moved from the deployment manager to the node.
User response No user action is required.
ADMS0005E: The system is unable to generate synchronization request: {0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
ADMS0009W: The data in the synchronization element is not valid: {0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
ADMS0012E: The system is unable to create an administrative client connection: {0}.
Problem The node agent cannot connect to the deployment manager during a synchronization. This error can result from the deployment manager being stopped, or can result from a network error.
User response Restart the deployment manager or correct the network error.
ADMS0013I: The system detects {0} CellSync objects.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
ADMS0014W: The system is unable to send synchronization completion notification: {0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
ADMS0015E: The synchronization request cannot be completed because the node agent cannot communicate with the deployment manager.
Problem The node agent cannot establish a connection to the deployment manager. The deployment manager process is probably not running.
User response Check the state of the deployment manager process. Restart the deployment manager.
ADMS0017I: An unexpected error occurred while trying to initiate automatic synchronization.
Problem Automatic synchronization is not starting successfully. You can use manual synchronization to move configuration files to the node.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
ADMS0018I: The automatic synchronization mode is enabled.
Problem This informational message indicates a change in the synchronization mode.
User response No user action is required.
ADMS0019I: Automatic synchronization mode is disabled.
Problem This informational message indicates a change in the synchronization mode.
User response No user action is required.
ADMS0020E: A synchronization operation received an exception from the repository while updating document {0}. {1}
Problem The synchronization operation can continue, but the repository update for the indicated document is not made.
User response 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.
Problem None
User response None
ADMS0022W: The system is unable to send synchronization initiation notification: {0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
ADMS0023I: A synchronization operation reached the iteration limit.
Problem 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.
User response 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}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
ADMS0025W: An Unexpected exception occurred in onChangeStart processing: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
ADMS0026E: An unexpected exception occurred in onChangeCompletion processing: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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.
Problem The exception message might detail a probable cause.
User response 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.
Problem The exception message might detail a probable cause.
User response 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.
Problem The specified resource file failed to load. This problem is due to an internal error.
User response Turn on the debug trace to get more information about the exception.
ADMS0030E: An unexpected exception occurred in postProcess processing ID={1}: {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
ADMS0031E: An exception {0} occurred when deleting directory {1}
Problem The exception message might detail probable cause.
User response Delete the directory manually.
ADMS0036E: The configuration synchronization failed.
Problem Configuration files cannot be synchronized between the deployment manager and the node.
User response Look at the other log entries to get information on the specific error. The deployment manager might be unreachable.
ADMS0100E: An error occurred when activating MBean: {0}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
ADMS0101E: The system is unable to get a configuration repository client.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
ADMS0104I: The system is unable to invoke a synchronization request on node {0}. {1}
Problem The system cannot send the synchronization request to the indicated node. This problem most likely occurred because the node agent is not running.
User response Start the node agent.
ADMS0107E: An exception occurred while finding the target synchronization object for node {0}. {1}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
ADMS0109I: The system detects {0} node synchronization objects for node {1}.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
ADMS0110E: An exception occurred getting the security credentials. {0}
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
ADMS0111I: The system is unable to find the target synchronization object for node {1}.
Problem The system cannot locate the NodeSync MBean for the indicated node. This problem most likely occurred because the node agent is not running.
User response Start the node agent.
ADMS0200I: The configuration synchronization started for cell.
Problem The sync operation across all the active nodes has begun.
User response None
ADMS0201I: The configuration synchronization started for node: {0}.
Problem Config Synchronization hsa being for the stated node.
User response None
ADMS0202I: Automatic synchronization mode is disabled for node: {0}.
Problem During the course of this sync event, Auto Synchronization is disabled, it will be re-enabled later.
User response None
ADMS0203I: The automatic synchronization mode is enabled for node: {0}.
Problem During the course of this sync, Auto Synchronization was disabled, it is now re-enabled
User response None
ADMS0204E: The system is unable to generate synchronization request for node: {0}.
Problem The deployment manager was unable to generate a request to the nodeagent residing on the stated node.
User response Check the logs in deployment manager and nodeagent
ADMS0205I: The configuration synchronization completed successfully for node: {0}.
Problem Config synchronization is complete for the stated node.
User response None
ADMS0206I: The configuration synchronization failed for node: {0}
Problem Config synchronization failed for the stated node.
User response Check the logs in deployment manager and nodeagent
ADMS0207I: Node Synchronization state for node: {0} - {1}
Problem This is current state of the synchronization in process
User response None
ADMS0208I: The configuration synchronization complete for cell.
Problem This is the final event that will appear, the synchronization for all active nodes is complete
User response None
ADMS0209W: The configuration synchronization complete for cell, errors occurred.
Problem This is the final event that will appear, the synchronization for all active nodes is complete. Some errors did occur.
User response Check the logs and previous events
ADMS0210E: Unable to check Node Synchronization state for node: {0} declaring failed.
Problem An error occurred when checking the synchronization state, the synchronization to that node has been declared failed.
User response Check the logs and previous events
ADMS0211I: Re-enabling automatic synchronization mode after successful sync operation
Problem Auto-sync is enabled again when sync can be carried out successfully
User response None
ADMS0212I: Disabling automatic synchronization mode after 5 consecutive failures to synchronize
Problem Auto-sync is disabled due to continued sync failures
User response Check for system anomalis that caused the sync failures and correct the condition
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.management.resources.sync.html

© Copyright IBM Corporation 2006, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)