Log4OM

Hello all,

I am running v.2.7.0.0 and TQSL version 2.5.4. I've suddenly noticed with the upgrade to 2.7.0.0 that my LoTW uploads get stuck. Here is what I see (sorry, I'm running remotely and can't seem to get a proper screen grab):

INFO: ADIF File created successfully.
INFO: TQSL Version 2.5.4
No private TQSL Password set
Executing TQSL with upload

and that is where it stops. I've double checked my settings "User" (which is the LoTW login username, correct?), TQSL exe path, Temporary path, Station ID. After this happens I notice that L4OM has to perform a forced closure. Any help is appreciated!

Thanks,
Brian WB8AM

Update, I reverted back to 2.6.0.0 and the same thing is happening. Could my SQLite file be corrupted? I suppose next step is to try one of my backups?

Thanks,
Brian

The backup route did not work either. Unfortunately, I'm not sure how to debug this any further.

Thanks,
Brian

Please email me direct and I will provide a download for you to try

Email is as on QRZ

Thanks Terry,

Email sent.

Very best, Brian

TQSL 2.5.4. and 2.7.0.0 working perfect here. Win 10 latest build.

SOLVED!

Major shout out to Terry & Daniele for working with me to solve this issue.

The problem: LoTW uploads were freezing which caused L4OM to not shut down gracefully. No error messages were indicated.

The troubleshooting: Terry recommended that I use an ADIF export of one of the trouble QSOs to upload directly to LoTW via TQSL. TQSL does not report errors back to L4OM, so this step was critical in finding the solution. During upload I discovered that my QSO ITU Zone and CQ Zones did not match my TQSL cert (I'm in the US and we have 3 ITU Zones... I chose the wrong one in L4OM.)

The solution: First step was to update my L4OM settings to the correct ITU/CQ Zones. Next I used the "Single Field Updater" in QSO Manager to update the zones and problem solved. LoTW accepted my upload without any further issues.

Thanks guys!
Brian WB8AM

WB8AM wrote: 22 Jun 2020, 18:03 (I'm in the US and we have 3 ITU Zones... I chose the wrong one in L4OM.)

Thank you for reporting back what caused the problem. Very strange thing.

Exact the same problem und exact the same solution !!!
Thanks, 73
Martin DG2MB