AgileTrack
Put your development on the AgileTrack

First Login Problem and agiletrack 1.1.2

Hi.
I have a problem with first login
I installed agileTrack Client and I selected HSQLDB in connection property. Then I use
user:admin
password:admin
and click the login button.
I get this error:
Login Cannot be performed. Trouble connecting to AgileTrack Server.
Table not found in statement [SELECT schema_version FROM agiletrack_config]

—Posted by Marco on Oct 6, 2007


	Forum AgileTrack Client


	Reply

Sorry this has taken a while to reply. I've not heard of this problem before with a clean database and I haven't been able to reproduce it.

If you're using Windows, I recommend launching AgileTrack using the agiletrack.bat file so you can see any console output. Perhaps an exception is occurring that you could send. Also, you can check the .log files in the installation directory. If you find any errors, please post them here and we should be able to figure out the problem. Thanks.

—Posted by Adam Lane on Oct 20, 2007 at 11:20:06 AM

hello…

I also try to use HSQLB in the connection. However, there is one more column ask me to put the database name. Since I am trying this product in the local pc, what database name I should put it there? If I don't, I got some error as the following
"login cannot be performed. Trouble connecting to the AgileTrack Server.
java.sql.SQLException:SOO10 Invalid argument in JDBC call"

—Posted by tryagiletrack on Oct 26, 2007 at 8:35:00 AM

I've seen the S0010 error if no hsql database name is specified. To select a name, open the settings dialog and just type in a simple database name, like "agiletrack". The name can be anything you want, but needs to be a simple string—e.g. no spaces or punctuation (underscores are probably allowed).

—Posted by Adam Lane on Nov 6, 2007 at 7:29:17 AM

I have the same problem with agiletrack 1.1.3 build 20071027

—Posted by nicola on Nov 9, 2007 at 10:59:51 AM

The suspicion is that this login problem is being caused by a localization problem when parsing an error response from the HSQL driver. A solution is in the works and will be released early this week.

—Posted by Adam Lane on Nov 18, 2007 at 9:44:08 PM