AT client HSQL setup issue -- "an sql error occurred when checking if database is empty"

Hi all,

We're trying to debug an issue with the installation of the AT client (2.0), configured to use the mini internal HyperSQL 2.0 database. The client is installed on Windows 7 (also tested on Windows XP).

When running through the installation steps outlined here:

... we run into a snag on the step at the top of p. 5 ("This selection will populate the other connection setting fields..."), which involves initializing the database. Once hitting the Next button, we get this error:

"an sql error occurred when checking if database is empty"

In looking at the AT user forums, it doesn't look like this has come up before.

Suggestions for troubleshooting, beyond re-installing, etc.? We can attempt to re-initialize the internal database and start fresh with an empty version -- but aren't able to locate the "at_db" folder, per the setup instructions (is the folder information stated in error, and should the "atdbinfo.txt" file instead be deleted?).

Any suggestions or advices appreciated!


-- Adrian

Adrian Turner
California Digital Library
(714) 289-1822

Hi, Adrian, I'll repeat the

Hi, Adrian,

I'll repeat the answer here in case other users need the information.

The "at_db" folder needs to be deleted, then run the AT Maintenance Program to re-initialized the internal database. The "at_db" folder should be in the same folder as the atdbinfo.txt file.

AT client HSQL setup issue -- "an sql error occurred when checki

Thanks, Annie -- removing the "at_db" folder did the trick!

-- Adrian

This bug doesn't go away

I am new to AT and can't get the internal database to work for me. I am not connected to an institution, but I am processing a fairly substantial collection of my family's papers for eventual donation to a large repository. I have the same "an sql error occurred when checking ... " problem that has been discussed in several forums. The solution in this thread -- to remove the "at_db" folder -- won't work for me because the release of AT that I am using already has it removed. I have carefully followed the instructions for initializing a new database, and I have deleted and reloaded AT a couple of times, and nothing seems to help. What am I doing wrong?

Re: This bug doesn't go away

Hi, Frank,
Try editing the system registry (HKEY_CURRENT_USER\Software\JavaSoft\Prefs\org\archiviststoolkit). Click in the start button, then 'Run' then type 'regedit' and enter. That should take you to the registry. Then look for HKEY_CURRENT_USER and expand folder to find the location of AT (HKEY_CURRENT_USER\Software\JavaSoft\Prefs\org\archiviststoolkit)

Make sure you initialize the blank database (internal or server) before attempting to connect. If you have further questions, send to

Best wishes,