Log4OM

Ok Cedric merci beaucoup. That's a nice one, good news is your Login credentials are good, no problem with password and/or upload code. I am still trying to understand why this is happening. So here is what's happening.

Log4OM is trying to UPDATE an existing QSO on HRDLog:

17:51:09.113 Info: [#=zGvR_CkmYvWtslNm_zQcOhrDTZd0G] : [HRDLOG UPLOAD] Updating existing QSO on HRDLOG: F4GNW|26/01/2020 17:49:46|40m|RTTY

But that QSO does not exist on HRDLog at all, therefore no update of this QSO possible.

17:51:09.542 Debug: * [#=zVesyneFaOMismavznA==][MoveNext][389 ms] : PostDataAsync: Post completed<?xml version="1.0" ?><HrdLog xmlns="http://xml.hrdlog.com"><NewEntry><error>Unable to find QSO</error></NewEntry></HrdLog>

17:51:09.556 Debug: [#=zGvR_CkmYvWtslNm_zQcOhrDTZd0G][MoveNext] : [HRDLOG UPLOAD - UPDATE] result:<?xml version="1.0" ?><HrdLog xmlns="http://xml.hrdlog.com"><NewEntry><error>Unable to find QSO</error></NewEntry></HrdLog>

A quick lookup confirms this, no QSO found for F4GNW on 26/01/2020

Now I'd like you to go to Log4OM "Recent QSO's (F7)". Edit the QSO with call F4GNW. Go to the Tab "QSL Info" and make a screenshot and post it here.

Thanks
Roland

HB9VQQ wrote: 26 Jan 2020, 19:15 Ok Cedric merci beaucoup. That's a nice one, good news is your Login credentials are good, no problem with password and/or upload code. I am still trying to understand why this is happening. So here is what's happening.


Thanks
Roland

Ok Roland,

this is the scren shot of the qsl info tab

Ok Cedric thank you. According your Screenshot Log4OM "thinks" it has already uploaded this QSO (green Sent Status) which is clearly not the case. That's why updating this QSO in HRDLog is not working.

Now go to Utilities --> QSL Manager

1.) Enter F4GWN in the Callsign field
2.) Select HRDLOG in "Search confirmation"
3.) Select QSO in the QSO table
4.) Mark checkbox "Enable Update"
5.) in the new window (red background) mark checkbox "Sent" and select "No"
6.) Click on Save (Floppy disk icon)
7.) Make sure "Sent" column in the QSO table has changed from Yes to No.
8.) Exit QSL Manager

Here is an example with call 8P2K


Now try to upload QSO again.

73
Roland

HB9VQQ wrote: 26 Jan 2020, 20:18 Ok Cedric thank you. According your Screenshot Log4OM "thinks" it has already uploaded this QSO (green Sent Status) which is clearly not the case. That's why updating this QSO in HRDLog is not working.


73
Roland

Ok Roland it is working now the upload is ok but how can i do for doing this automatic it is working for the other external service
should i do this all the time to upload to hrdlog

or is it a problem with my configuration on the software ?

Cedric, usually you don't have to do this. I never have to do this, it all works automatically for me. I don't know why this happened to you.
But I am glad it is working now.

HB9VQQ wrote: 26 Jan 2020, 21:24 Cedric, usually you don't have to do this. I never have to do this, it all works automatically for me. I don't know why this happened to you.
But I am glad it is working now.

Many thanks Roland for the help

i think i have found the problem
when you are in the configuration tab you can choose for each external service HRDLOG, LOTW, EQSL etc the sent préference and the recieve préference
i have change my HRDLOG preference from yes to no and now it look like ok

i hope it will be really the problem
but for the moment all seems to be ok

many thanks roland

Brilliant Cedric, good catch.

73
Roland

I followed this one.

How do you set your confirmations, use own or default ? In User information .

Or has this nothing to do with upload qso's ?

73 - Rudi - ON7CL

Update

Some how JT-Alert is blocking the automatic external log uploads. Found by accident was not running JT-alert trying to make a contact and it uploaded to QRZ and HRDlog. Started JT-alert again and the next QSO's did not upload. Shut down JT alert again and it started uploading qso's again.

I have similar problem with automatic upload new QSO to Clublig and Hrdlog when QSO is imported from WSJTX. When I enter it manually everything is ok. I have version 2.27.1.0. Before update everything was OK. Any support?
Greetings from SQ3M