I upgraded to version 2.8.0.0 and now I can not access my log as it says the database is invalid, I am using the SQLlite option.
I created a new database successfully, I save everything and exit. When I reload I get the same error message immediately, I did find an error message after trying this a number of times that suggested it was trying to create a read-only database, I have no idea what is doing that if it's correct.
I have checked the configuration settings multiple times and can't see anything that would be causing the issue, I have even checked the database file attributes in file manager and it is not marked as read only or hidden.
I have run out of idea's, does anyone have any suggestions?
Thanks for your help.
Cheers
Dale VK3VZX
Invalid Database
- G4POP
- Log4OM Alpha Team
- Posts: 11592
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Invalid Database
1. Did you create the sqlite database in version 2
2. Where did you store that database?
3. Did you import an ADIF file from Log4OM version 1 in the ADIF 3>>> format?
4. What computer and OS are you using?
2. Where did you store that database?
3. Did you import an ADIF file from Log4OM version 1 in the ADIF 3>>> format?
4. What computer and OS are you using?
73 Terry G4POP
Re: Invalid Database
1. I created a new database in version 2 after not being able to import the version 1 database.
2. The database is stored in the my documents folder which is where I have always stored it with version 1 and also with Nextgen V 2.7.0.0 without issue.
3. I did not try and import anything during the last attempt, I just created the fresh database, saved exited, and then restarted the software to get the same error.
4. I am running an HP (3 years old) with windows 10 with current updates and security patches.
Nextgen V 2.7.0.0 was working fine before the update to 2.8.0.0 but now a I can't roll back to V 2.7.0.0 without the same issue occuring.
Thanks
2. The database is stored in the my documents folder which is where I have always stored it with version 1 and also with Nextgen V 2.7.0.0 without issue.
3. I did not try and import anything during the last attempt, I just created the fresh database, saved exited, and then restarted the software to get the same error.
4. I am running an HP (3 years old) with windows 10 with current updates and security patches.
Nextgen V 2.7.0.0 was working fine before the update to 2.8.0.0 but now a I can't roll back to V 2.7.0.0 without the same issue occuring.
Thanks
- DF5WW
- Log4OM Alpha Team
- Posts: 2035
- Joined: 02 May 2013, 09:49
- Location: Kraam, Rhineland Palatinate, Germany
- Contact:
Re: Invalid Database
Hi Dale,
maybe something broken on the installation of 2.8.0.0. Have you tried a fresh download
and a new installation ?
By the way, if you create a new database it must be activated. After this the database
is empty and need import of ADIF V3 backup. Try a fresh installation first and also try
to open the original V2 database from 2.7.0.0.
We have had no changes to the database structure between 2.7 and 2.8 and here all is
running fine since the first releases of V2.

maybe something broken on the installation of 2.8.0.0. Have you tried a fresh download
and a new installation ?
By the way, if you create a new database it must be activated. After this the database
is empty and need import of ADIF V3 backup. Try a fresh installation first and also try
to open the original V2 database from 2.7.0.0.
We have had no changes to the database structure between 2.7 and 2.8 and here all is
running fine since the first releases of V2.


73´s .. Juergen ... ALT-512 SDR (10W) , 50 m random wire at SG-211 autotuner, 2 x Xiegu G90 (20W HF TRX) one as portable Radio. Also TS-790E (40 W) for VHF/UHF with X-50 vertical and Duoband 4-Element LPDA.
Re: Invalid Database
Hi Juergen,
Thanks for the help, unfortunately, it didn't work
I deleted all copies of the original download, uninstalled, and then restarted the PC.
I then downloaded and installed a fresh copy of 2.8.0.0 as suggested.
Once installed and started I was immediately prompted to create/connect to a database - of note, all of the previous configurations information was preloaded so the software must be finding a file somewhere that was not deleted prior to the reinstall.
Firstly I tried to connect to the database from 2.7.0.0 and got the error message that the database doesn't seem to be valid, so I then went on to create a new database that appeared to be successful, I made sure to click on the save and apply button before closing the configuration screen
I then imported my log from eQSL and this seemed to work without a problem, once the import was complete I was able to review the content of the log and it all seems to be in order.
It is at this point it all went south on me, I exited the software, reloaded it, and once again I was immediately prompted to create/connect to a database. I attempted to connect to the database I had just created and was able to view only to get the same error message that the database doesn't seem to be valid.
I have reviewed the quick start guide to make sure there wasn't anything I was missing out on, I not in your message you mention something about the database being activated but I couldn't find anything relating to that in the quick start guide.
There are only 2 potential issues I can think of:
1. Something in that configuration file that is getting loaded is correupted or,
2. The information I am importing from eQSL is causing an issue with the database becoming invalid after closing. It's a long shot I know but the file I get from eQSL is actually a .txt file even though I ask it for export an ADIF file. But it imports ok, saves ok and is readable until I restart the software.
Sorry for the long winded reply but I think it is helpful if I am detailed about the steps taken in case something I've done is an issue.
Thanks heaps for your time, I really appreaciate the effort you guys put in.
Cheers
Dale
Thanks for the help, unfortunately, it didn't work

I deleted all copies of the original download, uninstalled, and then restarted the PC.
I then downloaded and installed a fresh copy of 2.8.0.0 as suggested.
Once installed and started I was immediately prompted to create/connect to a database - of note, all of the previous configurations information was preloaded so the software must be finding a file somewhere that was not deleted prior to the reinstall.
Firstly I tried to connect to the database from 2.7.0.0 and got the error message that the database doesn't seem to be valid, so I then went on to create a new database that appeared to be successful, I made sure to click on the save and apply button before closing the configuration screen
I then imported my log from eQSL and this seemed to work without a problem, once the import was complete I was able to review the content of the log and it all seems to be in order.
It is at this point it all went south on me, I exited the software, reloaded it, and once again I was immediately prompted to create/connect to a database. I attempted to connect to the database I had just created and was able to view only to get the same error message that the database doesn't seem to be valid.
I have reviewed the quick start guide to make sure there wasn't anything I was missing out on, I not in your message you mention something about the database being activated but I couldn't find anything relating to that in the quick start guide.
There are only 2 potential issues I can think of:
1. Something in that configuration file that is getting loaded is correupted or,
2. The information I am importing from eQSL is causing an issue with the database becoming invalid after closing. It's a long shot I know but the file I get from eQSL is actually a .txt file even though I ask it for export an ADIF file. But it imports ok, saves ok and is readable until I restart the software.
Sorry for the long winded reply but I think it is helpful if I am detailed about the steps taken in case something I've done is an issue.
Thanks heaps for your time, I really appreaciate the effort you guys put in.
Cheers
Dale
- G4POP
- Log4OM Alpha Team
- Posts: 11592
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Invalid Database
Can you install TeamViewer on the Log4om computer and email me for a sked so that I can fix this for you?
73 Terry G4POP
Re: Invalid Database
HI Juergen,
yes we can do that, I have teamviewer installed already our only issue will be sorting out a time.
I am currently working nightshift for the next 3 nights, if my time calculations are correct 0600 hrs Australian EST would be 2000 UTC which may work out as I in theory get home from work avout 0530 if I don't work overtime, being an ambulance officer that is always possible.
Please let me know what you think time wise.
Cheers
Dale
yes we can do that, I have teamviewer installed already our only issue will be sorting out a time.
I am currently working nightshift for the next 3 nights, if my time calculations are correct 0600 hrs Australian EST would be 2000 UTC which may work out as I in theory get home from work avout 0530 if I don't work overtime, being an ambulance officer that is always possible.
Please let me know what you think time wise.
Cheers
Dale
- G4POP
- Log4OM Alpha Team
- Posts: 11592
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Invalid Database
Well first of all my name is Terry!
Email me to set uo a time, my email is g4pop (AT) arrl.net
Email me to set uo a time, my email is g4pop (AT) arrl.net
73 Terry G4POP
Re: Invalid Database
Opp's sorry Terry
Will email
Cheers
Will email
Cheers