IBM Tivoli Monitoring, Version 6.3

Diagnosing that the portal server does not start or stops responding

You can diagnose that the Tivoli® Enterprise Portal Server does not start or stops responding by running the Tivoli Enterprise Portal Server Analysis ITMSUPER tool.

About this task

To diagnose that the portal server does not start or stops responding, perform the following steps:

Procedure

Preliminary diagnostics

For more information about any messages received, see the IBM Tivoli Monitoring Messages reference guide. Operator responses and general information are provided for each message.
Allow the portal client enough time to establish a connection with the portal server.
Is DB2® running?
- Yes: See step 4.
- No: See Resolving database problems - instance not started.
Collect the portal server log or the operations log and look for the following text strings:
- KFWDBVER, version not found
- TEPS database not found
- user ID or password invalid
- DB2 instance not started
Run the Tivoli Enterprise Portal Server Analysis ITMSUPER tool.

What to do next

For more information on actions that relate to these diagnostics, see the problem resolution tasks.

Feedback