DA, RMA authentication error

I can log in to the repository using the same username/password. But when I try to log in to RMA or DA, I am getting an authentication error. Looking at Tomcat log I saw:

com.documentum.web.common.Trace - Encountered error in error message component jsp

java.lang.NullPointerException

at com.documentum.web.formext.config.ConfigThemeResolver.getTheme(ConfigThemeResolver.java:167)

at com.documentum.web.formext.config.ConfigThemeResolver.getStylesheets(ConfigThemeResolver.java:207)

...

Any idea what's going on? Thanks!

Find more posts tagged with

Comments

DCTM_Guru

What are you using when you log into successfully (eg Webtop, Desktop, or custom app)?

dctmhack

I logged in to the repository using idql successfully.

After restarting tomcat, I don't see any errors in Tomcat anymore. But strangely on the server $DOCUMENTUM/logs/log4j.log, there are errors [DFC_PREFERENCE_BAD_VALUE] Bad value for preference "dfc.security.keystore.file"

....

caused by java.io.IOException:Integer exceeds maximum valid value

And this log4j error didn't appear right away after I tried log in to da and rma.

I have my server and tomcat on the same windows box. I searched the entire computer on dfc.properties and they all have the same value for the dfc.security.keystore.file

P.S. Thanks Johnny for replying. I have worked with you and Eric before. Glad to catch up with you on this online forum.

DCTM_Guru

Who are you? There isnt anything on your profile.

Try deleting the aek file. This sometimes gets out of sync with the server and screws things up.

dctmhack

After deleting the aek file, the docbase won't start. So I have to put back the aek file. It is annoying that now tomcat log and server log are not putting out anything. All I got is "we are sorry, authentication failed." on the screen.

DCTM_Guru

Is DA/RMA running on the same server as content server or on different servers? We encountered an issue if the server clock on the RMA app server gets out of sync with the content server clock (>5 sec), we start getting stranged errors.

dctmhack

They are on the same Windows virtual machine. The Oracle database is on a different UNIX box.

XdctmX

Make sure that the "dfc.security.keystore.file" exists. Normally you should find it here - C\:/Documentum/config/dfc.keystore.

if the path is correct and the file exists, try renaming the dfc.keystore to something else and restart the DocBase.

dctmhack

I had thought that I had a wrong dfc.keystore file. So I regenerated dfc.keystore by commenting out the line of dfc.secure.keystore.file in dfc.properties for the server (in c:\documentum\config). It created a new dfc.keystore file under the same dir. c:\documentum\config. I have since uncommented that line to point to the same location. The aek.key file is still the old one generated during the content server installation.

I have tried commented out and uncommented that line in the dfc.properties file for my DA and RMA. But it doesn't make a difference.