Page 1 of 1

LOTW UPload

Posted: 29 Jan 2018, 14:14
by NZ4DX
Hey everyone,
I have just switched logging software to Log4OM and was trying to do the first LOTW upload and I get stuck on a step.. I have attached a photo of that spot.. ANy help would be appreciated
73 Fred NZ4DX
Capture.JPG
Capture.JPG (33.52 KiB) Viewed 5995 times

Re: LOTW UPload

Posted: 29 Jan 2018, 15:42
by G4POP
did you select the QSO's to be uploaded?

Re: LOTW UPload

Posted: 29 Jan 2018, 16:06
by NZ4DX
Yes I selected the qsl's to be uploaded prior to hitting the upload arrow

Re: LOTW UPload

Posted: 29 Jan 2018, 16:12
by G4POP
NZ4DX wrote: 29 Jan 2018, 16:06 Yes I selected the qsl's to be uploaded prior to hitting the upload arrow
Generate a support request with trace mode on and include an ADIF - See what you need to do here http://www.log4om.com/log4om-support/

Then email it to me at g4pop (at) arrl.net

DO NOT POST THE LOG REPORT ON THIS FORUM

Re: LOTW UPload

Posted: 29 Jan 2018, 16:23
by NZ4DX
Hi Terry,
I got a different error this time
1.JPG
1.JPG (115.99 KiB) Viewed 5987 times

Re: LOTW UPload

Posted: 29 Jan 2018, 16:37
by K7PT
The Private Pass Sign password is not normally used. It is not the same as you use for logging onto the LOTW web site. Unless you created one in the CERT process, clear it.

Also, the station location normally is not your call sign, it's normally like DESKTOP, LAPTOP, etc.

Check these and let us know what you find out.

Re: LOTW UPload

Posted: 29 Jan 2018, 16:51
by NZ4DX
thanks for the reply Chuck.. I cleared out the private password and my station location is set to my callsign.. guess i changed that when setting it up.. still getting the same error

Re: LOTW UPload

Posted: 29 Jan 2018, 20:18
by K7PT
Do as Terry says above.

Re: LOTW UPload

Posted: 30 Jan 2018, 12:25
by IW3HMH
Error returned is "13".
This means: The TQSL duplicates database is locked

I think there is something into TQSL (a temporary database) that is locked or TQSL has not been closed properly last time and leaved his internal database opened.
If you check in the TQSL folder (i guess) you should see a file with strange extension like ".tmp" or ".running" or ".working"...
try removing (copying away) this file from the folder and then check if it works.

Another option (last option) is to save certificates and reinstall TQSL.