LOTW manual upload

[w7rjr]

Please forgive should this have been already answered despite searching. I am running version 2.27.1.0 and TQSL version 2.6.5. In the recent past I have been able to upload selected QSOs to LOTW successfully. After execute "select required" I get a list of highlighted QSOs (72 of them). They are marked sent=no. Now when I click on upload selected qso I get the Upload confirmations screen that is black (so far so good). The QSO count shows 72. Confirmation type=LOTW. When I click the UP ARROW I get ADIF file created, INFO: TQSL 2.6.5 then Executing TQSL with upload and nothing happens. It appears that I am hung at that point. If I exit the process and retry it says "LOTW END" but none of the QSOs have really uploaded to LOTW. This process works flawlessly with Clublog and eQSL so I must assume it's just a TQSL problem? Checked station location (CQ,IARU, ITU) all good. Running TQSL as admin. No problem uploading .ADI file from TQSL.

[KI5IO]

Please forgive should this have been already answered despite searching. I am running version 2.27.1.0 and TQSL version 2.6.5. In the recent past I have been able to upload selected QSOs to LOTW successfully. After execute "select required" I get a list of highlighted QSOs (72 of them). They are marked sent=no. Now when I click on upload selected qso I get the Upload confirmations screen that is black (so far so good). The QSO count shows 72. Confirmation type=LOTW. When I click the UP ARROW I get ADIF file created, INFO: TQSL 2.6.5 then Executing TQSL with upload and nothing happens. It appears that I am hung at that point. If I exit the process and retry it says "LOTW END" but none of the QSOs have really uploaded to LOTW. This process works flawlessly with Clublog and eQSL so I must assume it's just a TQSL problem? Checked station location (CQ,IARU, ITU) all good. Running TQSL as admin. No problem uploading .ADI file from TQSL.

Bob,

Have you properly set up the "temporary path" for the LOTW/TQSL uploads? Image below shows my configuration.

.

[w7rjr]

Thanks for the reply. I do have a temporary path setup. It differs somewhat from what you show. Here is the path I am using "\Users\w7rjr\AppData\Roaming\Log4om2\temp" Here I find numerous .adi files of small size. Some are for Clublog, eQSL and LOTW. One of the many LOTW files begins with "LOTW_UPLOAD" followed by a date/time string. I assume this is the file LOG4OM is attempting to upload. I have verified that the temp folder has read/write permissions. A friend of mine running the same version(s) of software is exhibiting the same problem. I set it up for him so it's likely something I am doing wrong?? Thanks

[KI5IO]

Thanks for the reply. I do have a temporary path setup. It differs somewhat from what you show. Here is the path I am using "\Users\w7rjr\AppData\Roaming\Log4om2\temp" Here I find numerous .adi files of small size. Some are for Clublog, eQSL and LOTW. One of the many LOTW files begins with "LOTW_UPLOAD" followed by a date/time string. I assume this is the file LOG4OM is attempting to upload. I have verified that the temp folder has read/write permissions. A friend of mine running the same version(s) of software is exhibiting the same problem. I set it up for him so it's likely something I am doing wrong?? Thanks

Bob,

The temporary folder should NOT be put in the directory area you noted. It is protected.

Rather, put it under your Windows default "Documents" folder. Create a series of folders that make sense for you.

Image below shows my actual path that I have created under the "Documents" folder.

.

[w7rjr]

I can understand the concern about placing the folder in App Data. I changed the path to \Users\w7rjr\documents\lotw-tqsl. Created the folder and made sure there was read/write permissions.
Ran update again with the same problem. In the new folder there now exists one file named LOTW-UPLOAD_20230418001809.adi, 89 kb in size. It seems the app simply doesn't want to upload this file??
The odd thing is this worked fine about a month ago. Additionally, the download function works just fine. Clublog and eQSL work fine both up and down.

[KI5IO]

Bob,

Couple of things to try:

1) Delete the folder you had created under App Data. Or put in a folder you might have to historic backups.

2) Install the current (beta) version: V 2.27.1.2 beta (run this release and see if anything changes)

3) Make sure your Station ID properly matches between Log4OM and TQSL. (likely is OK, but just an item to check)

4) Recall that over the past 2-3 weeks (actually since early January-2023) ARRL has been having problems with LOTW. There have been extensive delays in processing Q's. They "finally" got some new hardware installed for a 'band-aide' fix and processing time has improved substantially. Hopefully they will get a plan in place to do a complete update/upgrade/overhaul of LOTW that is pretty much running on a wing and a prayer. I'm hopeful that none of their slowness impacted your operation. FWIW - mine is working FB since they made the hardware changes late last week.

5) I just re-read your original post. Do NOT run TQSL with Admin privileges. Not necessary.

6) File name creation (as you noted) is working as it should.

7) You could also (next time you try an upload) is to turn the Log Level from Info to Debug and see if there are more clues presented there. Help / Log Level (Info, Debug, Trace).

8) It appears the uploads you tried were changed from No to Yes after the manual upload process. You can utilize QSL Manager (LOTW) and 'enable update' and you can select those Q's involved and change the Yes back to No. Then do another Select Required and Upload Selected QSOs.

Give that a go and advise.

[w7rjr]

Nolan
Thanks for the suggestions and advice. Here is how I solved this particular issue.
I used the update function to change every outstanding record (QSO) from sent status NO to sent status YES.
Once accomplished all returned to normal. Apparently some flag was set or a bit flipped causing this?? I don't really know but I won't argue with success. Thanks and 73, W7RJR