Log4OM

The screenshots
PA3DJY

Screenshots part 2

Screenshots part 3

Sorry screenshots part 3

Anyone an idea ?

73's
Gerrit
PA3DJY

I believe that you will find the alert was re an unsaved QSO?

If you check your log I am sure that the QSO was saved but JTAlert has a habit of doing this is something slows down the save process

In JTAlett somewhere you can set the alert delay, set it to the longest possible to reduce these unwarranted alerts

You don't have to post for each screen shot you can have multiple screen shots on one forum post

Good day Terry,

I have tried your advice:
I have set the time for the alert delay to a higher number, that only results in a longer time for the error message box to be displayed.
After the 73's in a QSO it takes about 8 to 10 secons for JTAlert to come up with the not logged message.
After checking the file is not been written to the log.

Gerrit
PA3DJY

The fact that it was logging OK and suddenly it is not indicates that something changed on your computer......

Moved the logbook file

Firewall or virus protection changed through update perhaps

Change of settings in JTAlert

Server or UDP address changed in JTAlert or Log4OM communicator or both

Something got corrupted in JTAlert or WSJTX - a fresh install could have caused this or could cure it - Perhaps you upgraded to WSJT RC 3 or the latest JTAlert?

So many possibilities but for sure the issue is with your set up notLog4OM because Log4OM is passive during log writing, its JTAlert that does all the heavy lifting

Hi Terry,

on my end i also got a "QSO not logged" message from JTAlert. On my side this error occurs when
Internet connection is to slow. Log4OM sends to eQSL, HamQTH, Clublog and HRDlog (if this is
entered in the settings) and Log4OM will update a new entry only if those uploads are complete.

On my side every QSO will be logged (i don´t lost any) but from time to time with a bigger latency.

So in fact a slow Internet kann force this "error" which isn´t one

Hi Terry and Juergen,

At this time all logging okay.
What i did is remove JTAlert and Log4OM and reinstalled the whole bunch.
All seems to doing fine now.

Gerrit
PA3DJY