Unable to enter or edit log entries after update

[KC6WOG]

Hello. I've been enjoying this fine program for some time now and a few days ago, I updated to the latest version. The majority of my contacts are logged automatically from WJST-X, which works brilliantly. Today I manually typed in a SSB QSO and received an error saying "QSO not saved. Check band/mode/callsign/date". At this point I noticed that the last QSO actually logged was from Nov 10, the day I updated, nothing since had been recorded.

Trying to import an ADIF file also produces an error for each entry, "unable to open database." Any attempt to edit existing entries gives the previously mentioned "QSO not saved..." error.

The problem obviously correlates with the date of the update and to me, it smells like a Windows permission error. But running the program in Admin mode does not change the behavior. Any ideas what I'm doing wrong? I looked through the FAQ and didn't find anything directly addressing this.

Thanks in advance for any help! Cheers es 73.

Code: Select all

ou're running Log4OM V2 version: 2.34.0.0
Application is running in INSTALLED mode
You're running Log4OM without ADMIN privileges
Your program settings are OK. User is initialized
Log4OM application settings folder is located here:
C:\Users\lsgoo\AppData\Roaming\Log4OM2\
Log4OM is installed here:
C:\Program Files (x86)\IW3HMH\Log4OM NextGen\

DATABASE INFO
Log4OM is currently CONNECTED to a valid database
SQLITE Database Name: C:\Users\lsgoo\Documents\LogOM\KC6WOG.SQLite

[G4POP]

I beleive your suffering the same type of issue described here viewtopic.php?t=9392

Try moving the SQLite database to another location e.g. an installed hard drive (not on the cloud) because its probably a windows update that has made the file or folder read only

[KC6WOG]

Thanks Terry. It actually is on a local drive (Users\username\Documents\LOG4OM) and not the cloud. But I'll try another location on the drive and see what happens.

[G4POP]

Thanks Terry. It actually is on a local drive (Users\username\Documents\LOG4OM) and not the cloud. But I'll try another location on the drive and see what happens.

Dont use a removable drive like a USB stick

[KC6WOG]

I've only ever used the internal C drive, never a USB or cloud drive.

I have now moved the database from the Documents\Log4OM folder where it's always happily lived to a new folder in the root directory of my C drive and everything is working fine again. Not the most elegant solution, but I guess that's how it goes when Windows arbitrarily decides to mess with permissions.

Again Terry, thank you for your help resolving this, it's greatly appreciated.

Cheers es 73 de Larry, KC6WOG