The FIM console crashes after entering the Administrator credentials
The following error message is displayed in the standard output for the FIM managed server:
Sep 28, 2010 1:33:51 PM org.apache.struts.actions.DispatchAction dispatchMethod
SEVERE: Dispatch[/Dashboard] to method nvPreView returned an exception
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:280)
at com.rsa.ui.common.struts.action.RSABaseDispatchAction.execute(RSABaseDispatchAction.java:200)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
The description in the fim.properties file for configuring the JNDI URL for SSL is incorrect. The fim.properties file contains two parameters, one for non SSL and one for SSL:
jndi.url=t3://localhost:7001
jndi.ssl.url=t3s://localhost:7002
The parameter jndi.ssl.url is not used by FIM and is not read when parsing the FIM properties file. Only the jndi.url parameter is used.
If you wish to use SSL for the JNDI URL specifiy a t3s URL for the jndi.url parameter as in this example:
jndi.url=t3s://localhost:7002
The documentation in the fim.properties file will be changed in a future version to reflect the correct configuration.
Related Articles
AFX Server fails to start in a WebSphere deployment after upgrading to 7.0.x or higher of RSA Identity Governance & Lifecycle 388Number of Views RSA Via Lifecycle and Governance/Aveksa server will not start after environment customization 227Number of Views Tables embedded in workflow email nodes are malformed after upgrading to version 7.1.1 of RSA Identity Governance & Lifecycle 88Number of Views RSA SecurID Access identity router will not start after reboot on Microsoft Hyper-V 60Number of Views RSA RADIUS Service stopped after upgrading to AM 8.6 258Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows RSA Authentication Manager 8.9 Patches and Hotfixes Readme Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide