WebSphere Management Subsystem messages

ADMR0000E: A document named {0} already exists.
Explanation: The document cannot be created since it already exists.
User Response: Choose a different name for the document or edit the existing one.

ADMR0001E: Unable to locate repository root directory
Explanation: This is an unexpected exception. The cause can not be immediately determined.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

ADMR0006E: 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 the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

ADMR0007I: Repository locked: {0}.
Explanation: This is an informational message indicating that the configuration repository is locked.
User Response: No action is necessary.

ADMR0008I: Repository unlocked: {0}.
Explanation: This is an informational message indicating that the configuration repository is unlocked.
User Response: No action is necessary.

ADMR0009I: Document {0} was created.
Explanation: This is an informational message indicating that a document was created.
User Response: No action is necessary.

ADMR0010I: Document {0} was modified.
Explanation: This is an informational message indicating that a document was modified.
User Response: No action is necessary.

ADMR0011I: Document {0} was deleted.
Explanation: This is an informational message indicating that a document was deleted.
User Response: No action is necessary.

ADMR0012I: The repository epoch was refreshed.
Explanation: This is an informational message indicating that a user has refreshed the repository epoch value. This is done typically after a confguration document is manually edited to inform the system that the configuration was altered.
User Response: No action is necessary.

ADMR0013W: The backup directory {0} is not valid. The default location will be used instead.
Explanation: If the backup directory is explicitly set, it must be an accessible directory and not be under 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 will be used instead.
Explanation: If the temporary directory is explicitly set, it must be an accessible directory and not be under the repository root directory.
User Response: Use the default location or choose an accessible location outside of the configuration repository directory tree.

ADMR0015I: Document {0} was created by user {1}.
Explanation: This is an informational message indicating that a document was created by the specified user.
User Response: No action is necessary.

ADMR0016I: Document {0} was modified by user {1}.
Explanation: This is an informational message indicating that a document was modified by the specified user.
User Response: No action is necessary.

ADMR0017I: Document {0} was deleted by user {1}.
Explanation: This is an informational message indicating that a document was deleted by the specified user.
User Response: No action is necessary.

ADMR0018I: Configuration repository directory is {0}.
Explanation: This is an informational message.
User Response: No action is necessary.

ADMR0019I: Configuration repository temporary directory is {0}.
Explanation: This is an informational message.
User Response: No action is necessary.

ADMR0020I: Configuration repository backup directory is {0}.
Explanation: This is an informational message.
User Response: No action is necessary.

ADMR0021E: User {0} does not have the required role for accessing 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 if he is to have access to the document.

ADMR0100E: Error creating document named {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 the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

ADMR0103E: Unable to create download input stream for document named {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 the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

ADMR0104E: Unable to read document named {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 the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

ADMR0105E: Unable to write document named {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 the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

ADMR0106E: Error locking document named {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 the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

ADMR0107E: Error unlocking document named {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 the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

ADMR0108E: Error backing up document named {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 the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

ADMR0109E: Error restoring document named {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 the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

ADMR0110W: Unable to clean up backup for {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 the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

ADMR0111E: Unable to delete document named {0}.
Explanation: A document was unable to be deleted. The most common reason for this is that another process has the document open.
User Response: Retry the operation when no other processes are using the document.

ADMR0113E: 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 the document file if its presence will cause a problem.

ADMR0114W: Overwriting document {0} by request.
Explanation: A document in the repository was updated and one or more earlier updates to the document were overwritten. This was done at the request of the caller.
User Response: No action is necessary, but be aware that overwriting configuration documents can cause inconsistencies in the configuration.

ADMR0115E: Unable to register the application AppBinaryProcessor as a repository event listener. {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 the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

ADMR0200E: I/O error reading given input stream: {0}.
Explanation: When trying to read from a document file to calculate its digest the referenced exception occurred. This may be due to concurrent read and delete operations on the document.
User Response: Verify the document still exists and repeat the operation.

ADMR0201E: Digest algorithm is unavailable.
Explanation: This is an unexpected exception. The cause can not be immediately determined.
User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.


WebSphere Application Server  Last updated:  Fri Jul 18 16:46:33 EDT 2003
Library | Support | Trademarks | Feedback