Geocaching Australia

The update to 7.7.0.109 throws an SQLite Error.

SQLite Error 1 - no such column: Available.

with the program continually restarting irrespective of the button clicked on the Exception Log dialog.


Has anybody else experienced this?

I have notified Clyde.

Works OK for me.

New version seems OK here. I haven't been using it much yet though.

Ok here too.

just upgraded and all ok, I would guess a restore database and reapply upgrade. it looks like your database is corrupt

riblit wrote:The update to 7.7.0.109 throws an SQLite Error.

SQLite Error 1 - no such column: Available.

with the program continually restarting irrespective of the button clicked on the Exception Log dialog.

What version were you updating from?

maccamob wrote: What version were you updating from?

I would say 7.6.3.13 as that's the version on my laptop, which I'm loath to update now.

mtrax wrote: I would guess a restore database and reapply upgrade. it looks like your database is corrupt

That option won't for two reasons, firstly this upgrade makes major changes to the database as it now completely running on the newer database engine.

The second is the program continually loops at the error message so its not possible to access any of the program functions.

GSAK should have backed up your default database before the upgrade (7.7Back.zip). Open the zip file and copy the backed up dbs over the faulty ones and try again. I seem to recall something like that happening to me when I updated to 7.7 when it was in beta, but it worked ok second time round.

maccamob wrote:GSAK should have backed up your default database before the upgrade (7.7Back.zip). Open the zip file and copy the backed up dbs over the faulty ones and try again. I seem to recall something like that happening to me when I updated to 7.7 when it was in beta, but it worked ok second time round.

I have the same problem as Riblit.

GSAK continually opens in update mode and the file 7.7Back.zip seems to be created at the beginning and has nothing useful in it now by way of the data that I had before I started. I can recreate my database as it wasn't anything special but cannot get GSAK itself to start without going through this continual update loop.

I have no idea what version it was before I started.

I had a similar problem when using GSAK for the first time with Windows 7. The problem was something to do with opening the program as administrator and having forced file assocation checked in the Tools menu. Are you using Windows 7 too?

maccamob wrote:GSAK should have backed up your default database before the upgrade (7.7Back.zip). Open the zip file and copy the backed up dbs over the faulty ones and try again. I seem to recall something like that happening to me when I updated to 7.7 when it was in beta, but it worked ok second time round.

I tried that as well. It optimises, repairs and then gives me the same exception log and program looping.

Team Rubik wrote:I had a similar problem when using GSAK for the first time with Windows 7. The problem was something to do with opening the program as administrator and having forced file assocation checked in the Tools menu. Are you using Windows 7 too?

no, its on XP.

riblit wrote:

maccamob wrote: What version were you updating from?

I would say 7.6.3.13 as that's the version on my laptop, which I'm loath to update now.

Try http://gsak.net/board/index.php?showtopic=13728 if you want to go back to 7.6.3 while you get it sorted.

I read that thread earlier. I need 7.6.2 build 45 before I can put that on as it isn't full release. Finding that is proving to be a problem. The link is to the the home GSAK page and the only download links there are to the latest 7.7.0.109 that is causing the problem or 6.6.5.20 which is too far back.


I tried renaming the data directory to see if GSAK would create a default one. It did so and created a new blank database. If I change to an existing database I get the SQLite error 1 - No such column: AVAILABLE message with the cursor telling me its waiting for an SQL statement to finish running. Clicking either Restart or OK on the Exception Log Dialogue will cause the program to restart and open with the blank database.


I have checked both the newly created test database and an updated one for a column called "AVAILABLE" without success.

I still have 7.62 Build 45 downloaded executable here from when I got the new PC, PM your email if you want and I can try and email it at just under 10MB or use dropsend or similar.