When opening program the configuration window opens randomly
Re: When opening program the configuration window opens randomly
Update Report: I loading 2.33.0. successfully and I have no further issues when opening the program. All seems stable again. thanks
Mike - W0MS
Re: When opening program the configuration window opens randomly
Today I again had the issue of opening the program and I got the Welcome window and the program wants me to set up the configuration again from scratch. This issue was a corrupted .JSON file in the past. I forgot how to correct that. I know where to find the .JSON file. I tried to rename a previous version but it did not correct the issue. Please advise.
Mike - W0MS
-
G4POP
- Log4OM Alpha Team
- Posts: 11569
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: When opening program the configuration window opens randomly
PLEASE READ CAREFULLY
In some situations, windows doesn't allow applications to access to specific folders. This is due to the internal windows mechanism that consider any application as "malicious" until a certain number of instances are found running in the world.
What could happen:
Windows, after a windows update will not allow Log4OM to access to the configuration folder, preventing the application from retrieving his config structure. In this situation Log4OM will suppose it's the first run, and shows you the "welcome message".
BUT YOUR DATA IS STILL THERE.
Log4OM has a couple of "safety functions" to keep your data safe.
your log is actually (by default) backupped in ADIF format on every application closing. Last 6 use-days backups are kept, and a backup is made each end of the month.
WHERE: From Log4OM, open HELP MENU -> OPEN CONFIGURATION FOLDER, then browse the BACKUP FOLDER. Here you can find your latest ADIF backup
Your configuration: your config is saved in the BACKUP folder, simply get the file named <your call>_yyyyMMdd_hhmmss_config.json>, go back to main configuration folder and place the file in the USER folder, naming it: config.json (Log4OM must be closed when you do that)
A configuration copy is also saved in the user folder too, in the "last_valid_config.json". Simply rename it into "config.json" (Log4OM must be closed when you do that)
the folder is also accessible from resource manager, simply type: %APPDATA%\Log4OM2
in the address bar
On latest version we added an additional configuration backup into your DOCUMENTS folder. On restart Log4OM, if no valid config is found, will try recovering the config file from the backup folder and from document folder. If this fails, most probably due to those windows policies, simply follow the procedure stated above.
LAST BUT NOT LEAST:
HELP MENU -> SELF CARE INFORMATIONS
This will produce a simple TXT file with all vital info, like the database location, your passwords and everything else you may need, now and in the future, to recover your data, suggest you print this out just in case you need it.
In some situations, windows doesn't allow applications to access to specific folders. This is due to the internal windows mechanism that consider any application as "malicious" until a certain number of instances are found running in the world.
What could happen:
Windows, after a windows update will not allow Log4OM to access to the configuration folder, preventing the application from retrieving his config structure. In this situation Log4OM will suppose it's the first run, and shows you the "welcome message".
BUT YOUR DATA IS STILL THERE.
Log4OM has a couple of "safety functions" to keep your data safe.
your log is actually (by default) backupped in ADIF format on every application closing. Last 6 use-days backups are kept, and a backup is made each end of the month.
WHERE: From Log4OM, open HELP MENU -> OPEN CONFIGURATION FOLDER, then browse the BACKUP FOLDER. Here you can find your latest ADIF backup
Your configuration: your config is saved in the BACKUP folder, simply get the file named <your call>_yyyyMMdd_hhmmss_config.json>, go back to main configuration folder and place the file in the USER folder, naming it: config.json (Log4OM must be closed when you do that)
A configuration copy is also saved in the user folder too, in the "last_valid_config.json". Simply rename it into "config.json" (Log4OM must be closed when you do that)
the folder is also accessible from resource manager, simply type: %APPDATA%\Log4OM2
in the address bar
On latest version we added an additional configuration backup into your DOCUMENTS folder. On restart Log4OM, if no valid config is found, will try recovering the config file from the backup folder and from document folder. If this fails, most probably due to those windows policies, simply follow the procedure stated above.
LAST BUT NOT LEAST:
HELP MENU -> SELF CARE INFORMATIONS
This will produce a simple TXT file with all vital info, like the database location, your passwords and everything else you may need, now and in the future, to recover your data, suggest you print this out just in case you need it.
73 Terry G4POP
Re: When opening program the configuration window opens randomly
Yes all good to know thanks Terry. One thing I'd add.... if your config.json is corrupted as mine seems to be from time to time, one will need to find a day or two older version of the config file and move that to the user folder. The latest version if corrupted, will not work and an older one must be used.
Mike - W0MS
