Corba User Exception Is Included In The Portal Server Log When Creating Situations; Stopping Or Starting The Ewas Subcomponent Of The Portal Server - IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual

Corba user exception is included in the portal server log when
creating situations
When a user creates a new situation, the situation name must be unique. To verify
that the new name is unique, the software attempts to access a situation by the
new name. If the situation is found, then the name is already used and the user
must select a new name. If the request fails, then the name is not already used.
The failure to find the situation name is reflected in the log as the CORBA
exception. The CORBA user exception indicates that the name is unique.

Stopping or starting the eWAS subcomponent of the portal server

The eWAS subcomponent of the Tivoli Enterprise Portal Server (TEPS), named
Tivoli Enterprise Portal Server extension server (TEPS/e) is installed automatically
with the portal server. If you need to start or stop the application server instance of
eWAS on which the portal server is running, you must do it by starting or
stopping the portal server. You cannot use the eWAS start and stop commands to
control eWAS. Using the eWAS start and stop commands results in an internal
error, indicated by KFWITM392E Internal error occurred during login. If you
have already used the eWAS commands, see "Starting and stopping eWAS" in the
IBM Tivoli Monitoring Administrator's Guide for recovery instructions.
152
IBM Tivoli Monitoring: Troubleshooting Guide