Hi Tesleem,
I agree with Lynn, many customers have been affected by the Multiple Domains (Forest) feature being enabled. If that is your case, you should disable it.
http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec1870648.aspx
Make sure to restart the EEM and APM EM services
To restart EEM In Windows:
net stop igateway
start: net start igateway
In Linux:
from the iTechnology folder...
./S99igateway stop
./S99igateway start
You can also try to login directly to the EEM UI with your ID/user account. This will help you confirm if the problem is related to EEM only.
If the problem persists,
1) Go to the EEM Server:
Enabling TRACE logging for ipoz:
a) Go to $EIAM_HOME/config/logger
b) In the sever.xml file replace info or error with trace as shown below:
<logger name="eiam.server.ipoz" additivity="false">
<level value="trace"/>
<appender-ref ref="ipoz" />
</logger>
<logger name="eiam.server.ldap" additivity="false">
<level value="trace"/>
<appender-ref ref="ldap" />
</logger>
<logger name="eiam.server.performance" additivity="false">
<level value="trace"/>
<appender-ref ref="performance" />
</logger>
c) Save the changes.
2) Go to the Introscope EM server,
Add the below lines to the IntroscopeEntrerpriseManager.properties file:
log4j.logger.Manager.EemRealm=DEBUG
log4j.logger.additivity.Manager.EemRealm=false
Save and close the file
3) Reproduce the issue
-login to the EEM UI with your ID . Note the time
-login to the APM Client (Workstation, Webview or CEM console) with your ID. Note the time
4) Once this is done, reverse the above steps in order to set the logging back to their defaults.
5) Open a support case and attach:
- *.logs and *.conf under %EIAM_HOME% folder from the EEM server
- <EM_HOME>\logs , <EM_HOME>\config\realms and <EM_HOME>\config\domains.xml from the APM EM server.
Regards,
Sergio