Problem | This informational message indicates that the requested automatic synchronization interval is being set. |
User response | No action is required. |
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. |
Problem | Any new and modified configuration files are successfully moved from the deployment manager to the node. |
User response | No user action is required. |
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/. |
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/. |
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. |
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/. |
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/. |
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. |
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/. |
Problem | This informational message indicates a change in the synchronization mode. |
User response | No user action is required. |
Problem | This informational message indicates a change in the synchronization mode. |
User response | No user action is required. |
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. |
Problem | None |
User response | None |
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/. |
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. |
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/. |
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/. |
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/. |
Problem | The exception message might detail a probable cause. |
User response | Remove the RAR binary manually. |
Problem | The exception message might detail a probable cause. |
User response | Delete the uninstalled resource adapter archive (RAR) file manually. |
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. |
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/. |
Problem | The exception message might detail probable cause. |
User response | Delete the directory manually. |
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. |
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/. |
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/. |
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. |
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/. |
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/. |
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/. |
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. |
Problem | The sync operation across all the active nodes has begun. |
User response | None |
Problem | Config Synchronization hsa being for the stated node. |
User response | None |
Problem | During the course of this sync event, Auto Synchronization is disabled, it will be re-enabled later. |
User response | None |
Problem | During the course of this sync, Auto Synchronization was disabled, it is now re-enabled |
User response | None |
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 |
Problem | Config synchronization is complete for the stated node. |
User response | None |
Problem | Config synchronization failed for the stated node. |
User response | Check the logs in deployment manager and nodeagent |
Problem | This is current state of the synchronization in process |
User response | None |
Problem | This is the final event that will appear, the synchronization for all active nodes is complete |
User response | None |
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 |
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 |
Problem | Auto-sync is enabled again when sync can be carried out successfully |
User response | None |
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 |