DB Upgrade required WARNING

[k1fj]

I have been using Log4OM for 2 years and the updates have always been seamless. So after the turn of the new year (2016), I started Log4OM today for the first time this year, and the program has no configuration file to work to and I get a splash screen that states: "DB Upgrade Required" and refers to a an "activation.sqlite" filename.

I am running Windows 10, and running Log4OM version 1.24.0.0.

What do I need to do to:
1) Retrieve my original configuration file;
2) "activate" the database?

Frank - K1FJ

[G4POP]

I have been using Log4OM for 2 years and the updates have always been seamless. So after the turn of the new year (2016), I started Log4OM today for the first time this year, and the program has no configuration file to work to and I get a splash screen that states: "DB Upgrade Required" and refers to a an "activation.sqlite" filename.

I am running Windows 10, and running Log4OM version 1.24.0.0.

What do I need to do to:
1) Retrieve my original configuration file;
2) "activate" the database?

What version of Log4OM were you using before the upgrade?

1. Retrieve my original configuration file;

This sort of problem is usually caused by storing the config file in the Log4om program folder instead of with all of the other configuration files here: C:\Users\YOUR USER NAME\AppData\Roaming\LogOM - Otherwise it is caused by the user using a computer cleaner like C-cleaner etc

You can restore your configuration file by visiting the C:\Users\YOUR USER NAME\AppData\Roaming\LogOM\Backup folder

Either find the latest zip file named something like 20151226110352_backup.zip in which you will find a file called config.xml - You should copy that file to the folder ..... C:\Users\YOUR USER NAME\AppData\Roaming\LogOM

Alternatively the backup folder might just contain files if so fine the latest file that looks like

20151226110352_config.xml

Remove the date and time at the front of the name to get this config.xml and again copy and paste the file to your C:\Users\YOUR USER NAME\AppData\Roaming\LogOM

Restart Log4OM

2. "activate" the database?

Depends upon your answer to my question above

[k1fj]

Hi Terry,

I was running 1.23.0 before, but I had been running the latest (1.24.0.0) for a few weeks without trouble. Just seemed odd it would happen at the turn of the new year.

I did as you requested and renamed the latest back up config file and that took care of the issue. I have my correct config file back and all the log data too.

I would chance to guess that the computer must have corrupted something when it shut down the other night (New Years Eve), since I did notice that it took longer than usual to shut down and I had to manually turn the computer off.

Thank-you very much!

73 de Frank/K1FJ

[WA2SQQ]

My transition to 2016 went without any problems.

[IW3HMH]

Hi Frank,
there are no changes at database level between 1.23 and 1.24.
This message is usually reported when Log4Om is not able to "open" the database file to read into.

Can you try relocating the database file to another folder and try if you can open it?
Before that, make a copy of your latest ADIF from backup folder, to avoid loosing it by backup rotation.