Page 1 of 2

Automatic LOTW Upload

Posted: 22 Jun 2022, 15:16
by K5CKS
This is still a problem without a remedy. Automatic LOTW uploads has failed completely. I exported an ADIF this morning and using TQSL signed and uploaded my log. Everything worked fine. Log4OM is not and has not been uploading my log automatically. My TQSL is current version, my certificate is valid and I have changed nothing in Log4OM configuration. It had been working fine and now it is not. I have tried to use the Upload Confirmations utility but it freezes. Please see the attachment. I hope we can find a fix for this soon!
Thanks & 73,
Rory, K5CKS

Re: Automatic LOTW Upload

Posted: 22 Jun 2022, 16:31
by G4POP
Please EMAIL me your config.json file from the folder.

C:\Users\YOUR USER NAME\AppData\Roaming\Log4OM2\user

DO NOT POST IT HERE

What is the ACTUAL version number of Log4OM that your using?

Re: Automatic LOTW Upload

Posted: 22 Jun 2022, 17:31
by K5CKS
Thanks Terry,
2.22.0.0 I will email you the file in a moment.
73,
Rory, K5CKS

Re: Automatic LOTW Upload

Posted: 24 Jun 2022, 00:49
by ZL2UB
I am now getting the same problem, so interested in a solution.

I have just updated TQSL to the latest version (2.6.4)

and will try the latest version of LOG4OM when it has downloaded

Re: Automatic LOTW Upload

Posted: 24 Jun 2022, 00:56
by KI5IO
Dave,

What version of Log4OM are you using?

The current release is: V2.22.0.2

FWIW - my multiple times each week uploads to LOTW have worked fine. I usually always us the manual method from the QSL Manager.

Re: Automatic LOTW Upload

Posted: 24 Jun 2022, 01:00
by ZL2UB
This for me only started today (23/06/2022 UTC).
And happens both automatically and manually.

I have just upgraded to the latest version of LOG4OM (2.22.0.0), and the latest version TQSL, hoping it would resolve but it has not.

Also please note that Manual Download is still working

Wondering if it is problem with LOTW rather than a problem with LOG4oM

Re: Automatic LOTW Upload

Posted: 24 Jun 2022, 01:05
by ZL2UB
FYI

I have just checked LOTW and all my QSO's have been uploaded, so the problem now actually looks like the status has not been updated from "Requested" to "YES"

I will manually updated the status, and keep an eye on things

Re: Automatic LOTW Upload

Posted: 24 Jun 2022, 06:50
by G4POP
ZL2UB wrote: 24 Jun 2022, 01:05 FYI

I have just checked LOTW and all my QSO's have been uploaded, so the problem now actually looks like the status has not been updated from "Requested" to "YES"

I will manually updated the status, and keep an eye on things
Please update to the beta version 2.22.0.2

Re: Automatic LOTW Upload

Posted: 30 Jun 2022, 20:16
by W4GHV
As we find the solution, what is the best way do do the upload manually?
Selecting all gets stuck
Just selecting a few by dragging the mouse doesn't select them.
Doing CTRL click on them works fine. A LONG process.

It works for a dozen or so clicked/selected, but balks and hangs if you select 25.
TQSL or LOTW doesn't like big uploads it seems.

Re: Automatic LOTW Upload

Posted: 01 Jul 2022, 08:38
by IW3HMH
When uploading a "large" number of QSO, seems TQSL is no more answering to Log4OM (or log4OM is no more listening, but i can't find why even sitting on the debugger side... simply no answers are returned from the TQSL instance).
Running TQSL with the SAME string i'm using to run from inside Log4OM it works correctly.

That happened one day with the new version of TQSL and i was unable to fix it, not having changed anything on my side.
Once more, if the upload fails without changing Log4OM version (the code is built and static), the reason should be something outside Log4OM, maybe an updated file on TQSL side that require manual TQSL start once, or an issue on LOtW system remotely.

Basically, a compiled application, doesn't stop working without external activities, like changes in configuration files, but Log4OM doesn't have anything that updates from remote related to LOtW code (only parameters in program settings), so i can exclude an issue on the code while working with the same release you had yesterday