Log4OM

Has anyone else run into this issue? When I close LOG4OM2 the small blue window that comes up freezes.

This first appeared after the NAQP RTTY contest last night. I had imported the ADI file from N1MM, like I've done many time before, then closed LOG4OM. I noticed the closing sequence didn't seem to be advancing in the blue window as it normally does. I left the computer running for a while, thinking it just might be running slow, but no change. A screenshot of what I'm seeing is attached.

The only way I could get it to close is through the task manager. It appears that it did complete an upload to LOTW on closing though, as I saw new confirmations today when I logged in.

I'm using LOG4OM v.2.32.1.0. I thought it might be a problem with TQSL, so updated that. The problem persists. Running it on Windows 11.

Thanks,
Mike, KI1U

How long did you wait before forcing closure?

How many n1 mm qso's were imported?

Why are you not using real-time saving of n1mm QSOs via udp?

Have you got auto upload to lotw selected?

How long did you wait before forcing closure? I waited about 8 hours, just let it go overnight.

How many n1 mm qso's were imported? 221

Why are you not using real-time saving of n1mm QSOs via udp? Haven't set it up yet.

Have you got auto upload to lotw selected? Auto upload when closing the program.

Turns out the issue might with TQSL. It turns out my certificate expired in the middle of the contest. I noticed it uploaded Q's from the contest up to a point and then stopped. I've submitted the certificate renewal, once that's complete will try again.

Turns out the issue might with TQSL. It turns out my certificate expired in the middle of the contest. I noticed it uploaded Q's from the contest up to a point and then stopped. I've submitted the certificate renewal, once that's complete will try again.

That will be the problem, unfortunately TQSL does not return an error message when that happens so the task does not get ended

There is a workaround for that issue, please select this parameter in the application config:

I am experiencing exactly the same issue.
I have only used the Log4OM2 a couple of months and this was not an issue until some weeks ago.
Unfortunately I am unable to pinpoint what changed, beacause a lot of things change since I installed wsjtx and Gridtracker.

I don´t think there is any issue with my TQSL, it´s valid till 2027, but how do I know...

Yes, I have given it a lot of time to finish, but it nver gets there.
Using Win11 task manager to terminate process at every occasion. Bit frustrating...
Can this be debugged, somehow?

Edit: Apparantly, the qso data gets properly uploaded to LoTW while Log4OM tries to shut down since I find updated qso status on the LoTW web site afterwards.

73 de SM0IKC