-OR-

KFWITM215E: Unable to process 
logon request

• Ensure the user ID and password are correct.
• Verify that the monitoring server has started.
• Define the user in the portal server.
• Configure the TEPS or TEPS2 data sources.
• If security validation is active on the hub monitoring server, make sure the user ID is defined to the security system.

  For more information on security validation see the IBM® Tivoli® Monitoring Installation and Setup Guide or OMEGAMON® XE and Tivoli Management Services on z/OS®: Common Planning and Configuration Guide.

KFWITM010I: Tivoli Enterprise 
Portal Server not ready.

-OR-

KFWITM402E: Communication with the 
Tivoli Enterprise Server could not 
be established.

• Wait for the portal server to establish connection.

  To determine whether or not the portal server is ready for portal client logon, search the portal server trace log for this text string: Waiting for requests. If that string is not found, the portal server has not completed initialization. Portal server initialization can take as long as 20 minutes.

  To view the trace log, open Manage Tivoli Monitoring Services, right-click the portal server, and select Advanced > View trace log.

• Recycle the portal server.

For more information see Tivoli Enterprise Portal Server does not start or stops responding.

-OR-

The message
TEP has lost communication with TEMS
displays continuously.

-OR-

KFWITM008W The Tivoli Enterprise Portal Server has lost contact with the Tivoli Enterprise Monitoring Server.

-OR-

KFWITM392E: Internal error 
occurred during logon.

For environments with multiple interfaces reconfigure the portal server to specify a specific interface by following the instruction below.

• On Windows®:

  Use ipconfig /all to verify the current network interface configuration. Start the Manage Tivoli Monitoring Services and right-click the TEPS entry, and choose Advanced > Set network interface. Enter the correct IP address here.

• On UNIX® or Linux®:

  Use ifconfig -a to verify the current network interface configuration. Edit the agent *.ini file and add KDEB_INTERFACELIST=IP_address, where IP_address is the correct address.

For more information see "Configuring port number assignments for the portal server" in the IBM Tivoli Monitoring Installation and Setup Guide.

-OR-

KFWITM009I: The Tivoli Enterprise 
Portal Server is still being 
initialized and is not ready for 
communications.

If you receive message KFWITM009I you can look at the most recent trace log to verify that the portal server is initialized by searching for the text string Waiting for requests. Startup completed.

Re-establish the connection to LDAP. As soon as the portal server to LDAP connection is re-established, you can log in to the Tivoli Enterprise Portal.

If there is still a problem connecting with LDAP, de-configure LDAP authentication.

If the LDAP connection is broken and the normal procedure to switch off LDAP-based authentication does not work, the following steps need to be performed:

1. For AIX® and Linux systems, stop the portal server with the ./itmcmd agent stop cq command invoked from the installation directory.
2. Run the ./disableLDAPRepository.sh script from candle_home/arch/iw/scripts, where arch is the machine architecture, for example "li6263" or "aix533."
3. Reconfigure the portal server and disable LDAP authentication using the ./itmcmd config -A cq command invoked from the installation directory.
4. Start the portal server with the ./itmcmd agent start cq command invoked from installation directory. The portal server authentication through the monitoring server is now enabled.
5. If the monitoring server was also configured to use LDAP and the reason for this procedure being applied is LDAP being out of service, ensure you also change the monitoring server configuration to not authenticate through LDAP, following steps from the monitoring server configuration help.

1. For Windows systems, stop the portal server service using the Manage Tivoli Enterprise Monitoring Services application. \
2. Run the disableLDAPRepository.bat script from candle_home\CNPSJ\scripts.
3. Reconfigure the portal server using the Manage Tivoli Enterprise Monitoring Services application and disable the "Validate User with LDAP" option.
4. Start the portal server service using the Manage Tivoli Enterprise Monitoring Services application. The portal server authentication through the monitoring server is now enabled.
5. If the monitoring server was also configured to use LDAP and the reason for this procedure being applied is LDAP being out of service, ensure you also change the monitoring server configuration to not authenticate through LDAP, following the steps from the monitoring server configuration help.