LOTW upload Freezes

[AE0S]

Did this ever get resolved? Because I'm getting the same issue:

Code: Select all

03:19:26.858 Trace:         [dje_zTQTYRYZBSAV5LGRDWP2XQ_ejd][MoveNext] : Planned scheduler executed...
03:19:29.037 Info:          [LOTWManagement] : [LOTW UPLOAD] uploading LOG with 202 QSO
03:19:29.043 Info:          [AdifManagement] : Begin export to ADIF file: C:\Users\<redacted>\AppData\Roaming\Log4OM2\temp\LOTW_UPLOAD_20240706031929.adi
03:19:29.101 Info:        * [AdifManagement][57 ms] : Export to ADIF file completed: 202 QSO
03:19:29.107 Debug:         [UCAdvancedListbox][AddRow] : [MESSAGE ON LISTBOX Upload Confirmations] INFO: ADIF File created successfully.
03:19:29.109 Debug:         [LOTWManagement][UploadLog] : [LOTW UPLOAD] ADIF File created successfully
03:19:29.114 Info:          [LOTWManagement] : [LOTW UPLOAD] TQSL Version 2.7.3
03:19:29.12 Debug:         [UCAdvancedListbox][AddRow] : [MESSAGE ON LISTBOX Upload Confirmations] INFO: TQSL Version 2.7.3
03:19:29.126 Debug:         [UCAdvancedListbox][AddRow] : [MESSAGE ON LISTBOX Upload Confirmations] No private TQSL Password set
03:19:29.128 Info:          [LOTWManagement] : [LOTW UPLOAD] No private TQSL Password set
03:19:29.131 Debug:         [LOTWManagement][UploadLog] :  -d  -u -f update -a all   -q -x -l "AE0S Home" "C:\Users\<redacted>\AppData\Roaming\Log4OM2\temp\LOTW_UPLOAD_20240706031929.adi"
03:19:29.137 Debug:         [UCAdvancedListbox][AddRow] : [MESSAGE ON LISTBOX Upload Confirmations] Executing TQSL with upload
03:19:29.139 Info:          [LOTWManagement] : [LOTW UPLOAD] Executing TQSL with upload. Parameters: C:\Program Files (x86)\TrustedQSL\tqsl.exe
03:19:29.153 Info:          [LOTWManagement] : LOTW MANAGED MODE
03:19:29.159 Debug:         [UCAdvancedListbox][AddRow] : [MESSAGE ON LISTBOX Upload Confirmations] MANAGED MODE SET
03:19:31.869 Trace:         [dje_zTQTYRYZBSAV5LGRDWP2XQ_ejd][MoveNext] : Executing planned scheduler...

I see the tqsl.exe running in the task manager but not using any cpu cycles.

I went ahead and manually ran the upload on the command line and it was successful, LotW is showing the logs:

Code: Select all

C:\Program Files (x86)\TrustedQSL>tqsl.exe -d  -u -f update -a all   -q -x -l "AE0S Home" "C:\Users\<redacted>\AppData\Roaming\Log4OM2\temp\LOTW_UPLOAD_20240706031929.adi"

With more investigation I noticed that I can reliably upload up to 12 QSOs via Log4OM to LotW, but as soon as I try to upload 13 or more QSOs the upload process gets stuck.

BTW, I'm using LOG4OM 2 v.2.32.1.0.

[AE0S]

Update: The 12/13 aren't magic. I did encounter the upload issue with less than 12 and was once able to upload 16.

[G4TGJ]

I've just started having this problem. I could upload fine last week but cannot get it to work this week. However, I may have solved the problem. I've just noticed that the callsign certificate for my portable callsign expired a few days ago. In the past the ARRL sent me a reminder email well in advance of expiry but this didn't happen, presumably because of the cyber attack they recently suffered.

So anyone having this problem, run TQSL and check your certificates are up to date.

[G4POP]

I've just started having this problem. I could upload fine last week but cannot get it to work this week. However, I may have solved the problem. I've just noticed that the callsign certificate for my portable callsign expired a few days ago. In the past the ARRL sent me a reminder email well in advance of expiry but this didn't happen, presumably because of the cyber attack they recently suffered.

So anyone having this problem, run TQSL and check your certificates are up to date.

Perhaps you have not heard about the Global IT problem which is affecting many Internet resources.

Give it a couple of days and try again

[G4TGJ]

Perhaps you have not heard about the Global IT problem which is affecting many Internet resources.

Nothing to do with this. It was failing before this happened.

I got my new callsign certificate from the ARRL about 2 hours after requesting it. This has fixed the problem.

The issue is the lack of a useful error message when it fails although I suspect this is more a feature of TQSL than Log4OM.

[ha5uk]

Hi,

I have same issue: can't upload to lotw neither auto nor manually, no matter how few I try to.

INFO: ADIF File created successfully.
INFO: TQSL Version 2.7.1
Executing TQSL with upload
MANAGED MODE SET
and nothing...

Ver 2.33.0, TQSL 2.7.3 (direct upload from tQSL works fine)
Checked all in manual, the LOTW temporary drive to C:\Users\YOUR USER NAME\AppData\Roaming\Log4OM2\temp,
Checked the box 'Require TQSL Log ("-t" parameter)', 'Send my station updated data' also,
Confirmation settings match with upload flag.

Is there anything in UDP settings to deal with?
This issue came along with double logging of qso's came from inbound JtAert anyway, what's finally solved with unchecking one UDP connection - all issue since last update - they worked flawless before...

Any help appreciated,

[EC6DX]

Hi,
I have the same problem, any news about how answer this problem?

Jose EC6DX

[G4POP]

Certificates expired?

[EC6DX]

Hi Terry,
No, Certificate is OK...

I am using TQSL V 2.7.3 and I did not change anything...

I was working well untill last week

Jose EC6DX

[G4POP]

Hi Terry,
No, Certificate is OK...

I am using TQSL V 2.7.3 and I did not change anything...

I was working well untill last week

Jose EC6DX

So what happened last week? did you install any new software, have any updates of windows or other programs, use CC cleaner or similar?

Log4OM does not just stop working unles there is some intervention by the user or other software!