Procedure
1. Check the status of the instance in theDB2 Control Panel.
2. Recycle the portal server and resolve any issues reported.
3. Ensure that the user ID and password are correct.
Diagnosing that portal server logon fails
Logging on to the Tivoli Enterprise Portal Server fails when a user ID is locked,
disabled, or an internal error occurs during logon. Examine the portal server or
portal client logs for more information.
The logon failure might cause one or more of the following messages to display:
v KFWITM392E: Internal error occurred during logon.
v KFWITM009I: The Tivoli Enterprise Portal Server is still being
initialized and is not ready for communications.
v KFWITM010I: Tivoli Enterprise Portal Server not ready.
v KFWITM395E: User ID has been locked or disabled.
v KFWITM396E: User ID has been locked or disabled by Tivoli Enterprise
Portal Server.
About this task
To diagnose that the portal server logon Tivoli Enterprise Portal Logon fails,
perform the following steps:
Procedure
Preliminary diagnostics
1. For a guide to the messages and operator responses, refer to IBM Tivoli
Monitoring: Messages (http://publib.boulder.ibm.com/infocenter/tivihelp/
v15r1/topic/com.ibm.itm.doc_6.2.3fp1/itm623_messages.htm).
2. Look in the portal server or portal client logs for more information concerning
the message.
The portal client does not respond
You can encounter a problem that the Tivoli Enterprise Portal does not respond or
stops running.
Diagnosing that the portal client does not respond
You can diagnose that the Tivoli Enterprise Portal does not respond by verifying
that a Tivoli Enterprise Monitoring Server is started or the selected workspace is
returning data.
About this task
To diagnose that the Tivoli Enterprise Portal does not respond, perform the
following steps:
Procedure
Preliminary diagnostics
1. Verify that the monitoring server is started.
18 IBM Tivoli Monitoring: Troubleshooting Guide
To Next Page
Loading...
Need help?
General
