Problem | The document cannot be created because it already exists. |
User response | Choose a different name for the document or edit the existing document. |
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 informational message indicates that the configuration repository is locked. |
User response | No user action is required. |
Problem | This informational message indicates that the configuration repository is unlocked. |
User response | No user action is required. |
Problem | This informational message indicates that a document is created. |
User response | No user action is required. |
Problem | This informational message indicates that a document is modified. |
User response | No user action is required. |
Problem | This informational message indicates that a document is deleted. |
User response | No user action is required. |
Problem | This informational message indicates that a user refreshed the repository epoch value. This refresh typically occurs after a configuration document is manually edited to inform the system that the configuration changed. |
User response | No user action is required. |
Problem | If the backup directory is explicitly set, it must be an accessible directory that is located outside of the repository root directory. |
User response | Use the default location or choose an accessible location outside of the configuration repository directory tree. |
Problem | If the temporary directory is explicitly set, it must be an accessible directory that is located outside of the repository root directory. |
User response | Use the default location or choose an accessible location outside of the configuration repository directory tree. |
Problem | This informational message indicates that the specified user created a document. |
User response | No user action is required. |
Problem | This informational message indicates that the specified user modified a document. |
User response | No user action is required. |
Problem | This informational message indicates that the specified user deleted a document. |
User response | No user action is required. |
Problem | This informational message indicates the name of the configuration repository directory. |
User response | No user action is required. |
Problem | This informational message indicates the name of the configuration repository temporary directory. |
User response | No user action is required. |
Problem | This informational message indicates the name of the configuration repository backup directory. |
User response | No user action is required. |
Problem | Access to the indicated document requires the user to have the administrator role. |
User response | Grant the user the administrator role to access the document. |
Problem | The system property allowConfigOverwrites was set to false for the node agent process. The document overwrite feature may not be disabled in the node agent process. |
User response | No action is necessary. To avoid seeing this message remove the node agent system property setting for allowConfigOverwrites. |
Problem | Files older than a certain age are periodically cleaned out from the configuration repository temporary file area. This operation is normal. |
User response | No action is necessary. To change the frequency with which files are cleaned up, set the com.ibm.ws.management.repository.tempFileSweepIntervalMinutes Java system property. To change the age after which files are deleted, set the com.ibm.ws.management.repository.tempFileKeepTimeMinutes Java system property. |
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 | 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 | 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 delete the document. Another process might have the document open. |
User response | Retry the operation when no other processes are using the document. |
Problem | While recovering from an error, the configuration repository was unable to delete a newly created document. |
User response | Delete document {0}, if it is present after the process stops. |
Problem | A document in the repository was updated and one or more previous updates to the document are overwritten. These actions are performed at the request of the caller. |
User response | No user action is required, but be aware that overwriting configuration documents can cause inconsistencies in the configuration. |
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 | When trying to read from a document file to calculate the digest, the referenced exception occurred. This exception might result from concurrent read and delete operations on the document. |
User response | Verify that the document still exists and repeat the operation. |
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/. |