CWUDG

CWUDG0001I: {0} starting initialization.

Explanation

The user console control servlet is starting.

Action

No action is required.

CWUDG0002I: {0} finished initialization.

Explanation

The user console control servlet has completed startup successfully.

Action

No action is required.

CWUDG0003I: Reading init parameters.

Explanation

The user console control servlet has started reading external parameters during initialization.

Action

No action is required.

CWUDG0004I: Finished reading init parameters.

Explanation

The user console control servlet has finished reading external parameters during initialization. The user console is ready to accept client requests.

Action

No action is required.

CWUDG0005E: A serious error has occurred. error message: <{0}> error: {1} More information: {2}

Explanation

An unexpected error has occurred. Examine the error message, error type, and additional information to help to resolve the problem.

Action

If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J .

CWUDG0006E: A persistence error has occurred. error message: <{0}> error: {1} More information: {2}

Explanation

An error occurred while performing a database operation. Examine the error message, error type, and additional information to help to resolve the problem.

Action

Check the database connections.

CWUDG0007E: A User mismatch error has occurred. error message: <{0}> error: {1} More information: {2}

Explanation

The user id provided does not match the user id required or expected while performing an operation that requires authentication. Examine the error message, error type, and additional information to help to resolve the problem.

Action

Check that the user has authority for the operation that was requested.

CWUDG0008E: An invalid key was passed. error message: <{0}> error: {1} More information: {2}

Explanation

The requested operation is trying to retrieve information about an entity with a key that is not valid. This might occur if the entity has been deleted by another session. Examine the error message, error type, and additional information to help to resolve the problem.

Action

Ask the client to close existing sessions and attempt the operation in a new browser session.

CWUDG0009E: An invalid value was supplied. error message: <{0}> error: {1} More information: {2}

Explanation

A value that was passed to an API call was not valid. Examine the error message, error type, and additional information to help to resolve the problem.

Action

CWUDG0010E: Failed to introspect ActionForm fields. Exception: {0}

Explanation

The contents of a form object cannot be checked for characters that are not valid.

Action

CWUDG0011E: Failed to invoke reflected methods in ActionForm. Exception: {0}

Explanation

The contents of a form object cannot be checked for characters that are not valid.

Action

CWUDG0012E: User console initialisation failed to connect to UDDI database. Exception: {0}

Explanation

During user console initialization, connection to the database failed, and threw the exception specified.

Action

Check the connection to the UDDI database. Examine the exception message to help to resolve the problem.

CWUDG0013E: User console initialisation failed to initialize tModels. Exception: {0}

Explanation

An error has occurred during initialization of ActionServlet, specifically when reading tModels (invoking the init method in class TModelNames).

Action

Check the state of the UDDI database. Check that the TMODEL table is populated with valid data. Examine the exception message to help resolve the problem.

CWUDG0014E: User console initialization failed to initialize taxonomies. Exception: {0}

Explanation

An error has occurred during initialization of ActionServlet, specifically when reading taxonomy data (invoking the init method of CategoryTaxonomyTree).

Action

Check the state of the UDDI database. Examine the exception message to help to resolve the problem.