Page 1 of 1

"Authentication Error"

PostPosted:Thu Aug 23, 2012 10:41 am
by manasj
I have followed each and every steps mentioned in the WIKI documentation and reloaded the OpenKM DMS with desired settings. It was working perfectly for 2 days. But from the last Tuesday I am facing the same problem again. "Authentication error" . Can you please guide me how to detect and solve the problem. I will be highly obliged.

Note: I have again reloaded the entire system with the settings as specified in the documentation. It was working perfectly last day again today morning the system got crashed. I would like to mention that its showing an error

OKM 019024:(GetUserHome) database Error
No row with the given identifier exists:
com.openkm.dao.bean.profile#1

Regards
Manas

Re: "Authentication Error"

PostPosted:Fri Aug 24, 2012 4:23 pm
by jllort
About which openkm version are we talking about ?

Have you configured other DBMS or which comes by default with openkm ?
Have you changed OpenKM.cfg hibernate.hbm2ddl=none after first start up ?

Re: "Authentication Error"

PostPosted:Sat Aug 25, 2012 6:36 am
by manasj
Dear Sir,

I am using OpenKM Version 5.1.10 and default DBMS which has come included.

This is what i have done.

Installed Java jdk1.6.0_31

Downloaded OpenKM 5.1.10 + JBoss 4.2.3.GA bundle and uncompressed on c:\.

Configuration

Opened C:\jboss-4.2.3.GA\bin folder. Edit run.bat file

Set JAVA_HOME=C:\Program Files\Java\jdk1.6.0_31 in the following line
• :FOUND_RUN_JAR
• set JAVA_HOME=C:\Program Files\Java\jdk1.6.0_31
• if not "%JAVA_HOME%" == "C:Program Files" goto ADD_TOOLS

added -b 0.0.0.0 parameter as shown below for remote login facility
Code: Select all
:RESTART
"%JAVA%" %JAVA_OPTS% ^
-Djava.endorsed.dirs="%JBOSS_ENDORSED_DIRS%" ^
-classpath "%JBOSS_CLASSPATH%" ^
org.jboss.Main %* -b 0.0.0.0

Java Out Of memory Error: rem JVM memory allocation pool parameters. Modified as appropriate. set JAVA_OPTS=%JAVA_OPTS% -Xms256m -Xmx1024m -XX:PermSize=64m -XX:MaxPermSize=128m

Changed repository.home location to the appropriate folder
Changed system.imagemagick.convert location to the appropriate folder
Changed system.ocr location to the appropriate folder
Changed system.swftools.pdf2swf location to the appropriate folder
Changed system.openoffice.path location to the appropriate folder

Once the configuration are done , I have changed the hibernate.hbm2ddl property from create to none.

started the run.bat file and it was working perfectly on first run or 2-3 times. but while i am starting it on next day at the login it shows an error
Code: Select all
OKM 019024:(GetUserHome) database Error
No row with the given identifier exists:
com.openkm.dao.bean.profile#1
If i am trying to restart the jboss server and logging again it is showing authentication error. Please help.

Re: "Authentication Error"

PostPosted:Sat Aug 25, 2012 9:24 am
by jllort
Do you have information in the repository or can be restarted all the repository. If is the second case I suggest:
1- Stop openkm
2- Delete repository folder
3- set OpenKM.cfg to create
4- Delete /server/default/data/hypersonic/ all contents into
5- start openkm

Re: "Authentication Error"

PostPosted:Tue Aug 28, 2012 5:26 am
by manasj
Dear Sir,

I have done exactly the things you have advised.

1- Stopped openkm
2- Deleted repository folder
3- set OpenKM.cfg to create
4- Opened /server/default/data/hypersonic/ and deleted all contents in it
5- started openkm

Things were working fine last day but today again the same error.

One thing i would like to mention

Yesterday i have tested the OpenKM functionality with stopping and restarting the JBoss Service. There was no problem. But while the server is being restarted today morning the problem has happened.

Regards
Manas

Re: "Authentication Error"

PostPosted:Tue Aug 28, 2012 6:40 pm
by jllort
I suggest you try in other server, in this you have got something strange, and I can not image what could be. To understand what's happening we should take a look directly on your sever and this kind of support is only available to our customers. Sincerally we could take a look on your server.log error etc.. but I think without more closer aproximation to your server we will be losing time. My suggestion is try in other server ( if you're using virtualization I suggest to not try in other virtualized with same configuration, probably you'll get same error, I suggest you try in other server configuration ).