WebSphere Management Subsystem messages |
ADMR0000E: A document named {0} already exists.
Explanation:
The document cannot be created because it already exists.
User Response:
Choose a different name for the document or edit the existing document.
ADMR0001E: The system is unable to locate the root directory of the repository.
Explanation:
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/.
ADMR0006E: An error occurred activating MBean: {0}.
Explanation:
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/.
ADMR0007I: The repository is locked: {0}.
Explanation:
This informational message indicates that the configuration repository is locked.
User Response:
No user action is required.
ADMR0008I: The repository is unlocked: {0}.
Explanation:
This informational message indicates that the configuration repository is unlocked.
User Response:
No user action is required.
ADMR0009I: Document {0} is created.
Explanation:
This informational message indicates that a document is created.
User Response:
No user action is required.
ADMR0010I: Document {0} is modified.
Explanation:
This informational message indicates that a document is modified.
User Response:
No user action is required.
ADMR0011I: Document {0} is deleted.
Explanation:
This informational message indicates that a document is deleted.
User Response:
No user action is required.
ADMR0012I: The repository epoch is refreshed.
Explanation:
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.
ADMR0013W: The backup directory {0} is not valid. The default location is used instead.
Explanation:
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.
ADMR0014W: The temporary directory {0} is not valid. The default location is used instead.
Explanation:
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.
ADMR0015I: User {1} created document {0}.
Explanation:
This informational message indicates that the specified user created a document.
User Response:
No user action is required.
ADMR0016I: User {1} modified document {0}.
Explanation:
This informational message indicates that the specified user modified a document.
User Response:
No user action is required.
ADMR0017I: User {1} deleted document {0}.
Explanation:
This informational message indicates that the specified user deleted a document.
User Response:
No user action is required.
ADMR0018I: The configuration repository directory is {0}.
Explanation:
This informational message indicates the name of the configuration repository directory.
User Response:
No user action is required.
ADMR0019I: The temporary directory of the configuration repository is {0}.
Explanation:
This informational message indicates the name of the configuration repository temporary directory.
User Response:
No user action is required.
ADMR0020I: The backup directory of the configuration repository is {0}.
Explanation:
This informational message indicates the name of the configuration repository backup directory.
User Response:
No user action is required.
ADMR0021E: User {0} does not have the required role for accessing a restricted document {1}.
Explanation:
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.
ADMR0022W: The document overwrite feature may not be disabled in the node agent process.
Explanation:
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.
ADMR0100E: An error occurred when creating document {0}: {1}
Explanation:
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/.
ADMR0103E: The system is unable to create a download input stream for document {0}: {1}.
Explanation:
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/.
ADMR0104E: The system is unable to read document {0}: {1}.
Explanation:
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/.
ADMR0105E: The system is unable to write document {0}: {1}.
Explanation:
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/.
ADMR0106E: An error occurred locking document {0}: {1}.
Explanation:
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/.
ADMR0107E: An error occurred unlocking document {0}: {1}.
Explanation:
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/.
ADMR0108E: An error occurred backing up document {0}: {1}.
Explanation:
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/.
ADMR0109E: An error occurred restoring document {0}: {1}.
Explanation:
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/.
ADMR0110W: The system is unable to clean up the backup for document {0}. {1}
Explanation:
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/.
ADMR0111E: The system is unable to delete document {0}.
Explanation:
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.
ADMR0113E: The system is unable to delete document {0} after a failure: {1}
Explanation:
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.
ADMR0114W: The system is overwriting document {0} by request.
Explanation:
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.
ADMR0115E: The system is unable to register the AppBinaryProcessor application as a repository event listener. {0}
Explanation:
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/.
ADMR0200E: An I/O error occurred when reading the given input stream: {0}.
Explanation:
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.
ADMR0201E: The digest algorithm is unavailable.
Explanation:
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/.