Unable to login to Ebase Designer after upgrading

[Sarah]

I have upgraded from Ebase 3.2.1 to 3.3.0 and am unable to login to the Ebase Designer. When I enter my login details I get the following error:

java.lang.SecurityException: Unable to locate a login configuration

I'm assuming this is referring to the ebaselogin.config file? I've double-checked my java.security file and my line reads as follows:

login.config.url.1=file:C:/Ufs/UfsSever/conf/ebaselogin.config

The path specified is where the file is located.

[Sarah]

This problem is caused when:

1. The ebaselogin.config file is not in the specified location,
2. The path in the java.security file is wrong or
3. The wrong java.security file has been modified.

The most common cause is point 3.

You need to establish which instance of Java (especially if more than one is installed) Tomcat is using in order to determine which java.security file is being used.

You can use the following document to help determine which Java Tomcat is using. Please note these are just guidelines and not definitive instructions.

http://www.ebaseftp.com/download/forum/ ... _Notes.doc

[SimonC]

I also suffered from this problem when upgrading our Ebase installation, and traced the problem back to a missing environmental variable.

I can't remember whether it was JAVA_HOME or TOMCAT_HOME being missing that caused the problem, but adding it in solved the problem.

[Joost]

login.config.url.1=file:C:/Ufs/UfsSever/conf/ebaselogin.config

Instead of relying on automatic getting the right java version, it is also possible to use a commandline option:

-Djava.security.auth.login.config=C:/Ufs/UfsSever/conf/ebaselogin.config

For our Windows tomcat service I used TomcatW.exe //ES//Ebase to amend the service configuration. The Tomcat service is named Ebase.

More info:
http://publib.boulder.ibm.com/infocente ... vref23.htm