LOTW upload Freezes

[KI0EB]

Hello,
I am using Log4OM Version 2.30.1.0 on a Windows 11 computer. Since November when uploading QSOs to LOTW it freezes (after displaying "MANAGED MODE SET" with the following displayed in the "Upload confirmations" window:

INFO: ADIF File created successfully.
INFO: TQSL Version 2.7.1
No private TQSL Password set
Executing TQSL with upload
MANAGED MODE SET

LOTW continues to download with no issues. I have had no issues with uploading and downloading from QRZ. All other functions appear to be OK.

Any Suggestions? Thanks in advance,

Tanks,
Kevin Fontes
KI0EB

[KI5IO]

Kevin,

What is the location of your LOTW Temporary Path? I'm guessing it is not in a folder that is "un-protected" ... meaning that you would have to have Admin Privileges to access it.

See images below that show where I have mine set under the "My Documents" or "Documents" folder created by the Windows O/S.

.

[KI0EB]

Thanks so much for the quick reply.

The attachment shows where I had my temporary path. I changed it to a location as you recommended. I got the sam result. Also, I was sucessfully using the original path before this problem started in November. Any other ideas?

thanks,
Kevin Fontes
KI0EB

[KI5IO]

Kevin,

OneDrive situations have been known to cause issues.

Can you try a local folder on your main "C" drive under the "Documents" O/S created folder?

Have you tried to un-tic the "auto upload" option for LOTW Q's?

Only change is that you would have a couple key clicks to upload to LOTW via the QSL Manager.

You could also try and tic (or enable) the TQSL Interactive Mode and see if that might resolve.

[OA9DVK]

Hi there, same issue here. my temp is in c:\ . It worked flawlessly for months. Recently I got the same problem. No changes were made whatsoever.

please help

73 de Daniel
IK3SGL
OA9DVK

[KI5IO]

Daniel,

Try the suggestions I made above.

The Temporary Path needs to go to an area on your HDD/SSD that is "not protected" ... meaning that you have to elevate to Administrative Level to save a file to that area.

Also ... try the tic / un-tic options I suggested above as well.

Changes may have come about with a Windows Update that might have changed something.

I've had 2-3 updates on my laptops in the past couple of months so have to always be checking for things to make Microsoft doesn't do something to mess up my settings.

[OA9DVK]

Hi Nolan, yep I performed all the actions you had suggested but nothing changed. There might be something else.

[KI5IO]

Hi Nolan, yep I performed all the actions you had suggested but nothing changed. There might be something else.

Daniel,

What is your version of Log4OM? Help / About will provide that information.

What is your version of TQSL? Help / About will provide that information.

Are the QSOs being uploaded from your direct entry into the Main UI of Log4OM or are they via input via some 3rd party APP related to the FTxx modes?

[OA9DVK]

Thank you Nolan for the fast reply.
Log4om ver= 2.30.1.0
TQSL ver= 2.7.2
Qso were both from main entry and from JTDX, VarAc.

I do not have a clue what happenned. Everything worked 'till last week... I guess it has to do with some Windows upgrades... I am getting tired of this os...

73 de Daniel
IK3SGL
OA9DVK

[WR0H]

I found this thread as I was searching for an answer to the same question. I've started having the same issue out of the blue. The problem began a couple of days ago (prior to upgrading to v2.31)
My TQSL version is 2.7.2, and none of my directories or file locations were changed recently.