Log4OM

I hope that this is 'user support'..... Today I entered a contact (one of several) and it took a very long time, but eventually a message saying 'Database is Locked' came up on my screen. I tried a couple of time to save but got same message each time. I shut the program, restarted, and again attempted to enter the contact.... same error message. Next step was a computer reboot which solved the problem and I can now log again.

My question is, does anyone know of a way to unlock the log4om database without the need to reboot should this error happen again ???

(there has to be an easier and quicker way than a reboot)

regards
John

John,
I have never heard of this before and can only imagine something external has done this, like malware or virus! So I don't have a clue what to suggest other than a full virus scan and malware check (Try Malwarebytes)

I guess that you carry out regular defrag's and clean ups of your hard drive, please don't use Ccleaner it can cause issues with all computer programs.

Perhaps Lele has some better ideas but let's hope it was a one off situation

G4POP wrote:John,
I have never heard of this before and can only imagine something external has done this, like malware or virus! So I don't have a clue what to suggest other than a full virus scan and malware check (Try Malwarebytes)

I guess that you carry out regular defrag's and clean ups of your hard drive, please don't use Ccleaner it can cause issues with all computer programs.

Perhaps Lele has some better ideas but let's hope it was a one off situation

Thanks Terry. Yeah, so far its a 1 off. Trust me to have a 'never heard of, 1 off' event As for malware/virus' etc I use Comodo and do regular scans & defrags...

I'll put it down to one of those microsoft mysteries.

73
John

Db locks when an application cannot complete his write on the database.
This could happens if the database is in a "unstable" device or the OS abruptly loose the disk/usb key or access to the file.

There could be also a software issue on that, and in that case a program log could help greatly.

Anyway locks are automatically rollback when you restart the application that locks the file, or you open the file again.

Did you noticed something strange while you have had this issue?

IW3HMH wrote:Db locks when an application cannot complete his write on the database.
This could happens if the database is in a "unstable" device or the OS abruptly loose the disk/usb key or access to the file.

There could be also a software issue on that, and in that case a program log could help greatly.

Anyway locks are automatically rollback when you restart the application that locks the file, or you open the file again.

Did you noticed something strange while you have had this issue?

Sorry for late reply, no, I did not notice anything unusual before this happened. And it has not happened since. It appears to be a one off and not really an issue.

73
John

IW3HMH wrote:Did you noticed something strange while you have had this issue?

This happened again today but this time I did notice something, and I now know the cause, and it is not Log4om.

The database lockup was caused by a program called 'JTalert' and just a moment prior to database lockup a small error message from JTalert came up on the screen. This time I was able to 'unlock' the database without a complete reboot, by closing both JTalert and Log4om and then restarting them.

73
John
VK7XX

JTAlert is directly accessing Log4OM database without using Log4OM interfaces (for adding QSO, as example).
This could cause unexpected behaviours when the database is not correctly released or is accessed in write mode without a clean exit of the caller/updater software.
Was JTAlert adding a QSO?

IW3HMH wrote:------- Was JTAlert adding a QSO?

sorry Lele, I do not know exactly what it was doing. I do not use the logging feature of JTalert, I prefer to type the info in to Log4om myself.

John