Problem with upload to HRDLOG service

General discussions V2
sp5ah
Novice Class
Posts: 24
Joined: 11 Dec 2022, 11:51

Re: Problem with upload to HRDLOG service

Post by sp5ah »

G4POP wrote: 24 Mar 2023, 10:57
sp5ah wrote: 24 Mar 2023, 10:56 I'm using 2.25 ....
You need t update to 2.27.1.0 ASAP
I didn't know it was already 2:27. I will check it right away
sp5ah
Novice Class
Posts: 24
Joined: 11 Dec 2022, 11:51

Re: Problem with upload to HRDLOG service

Post by sp5ah »

Now even the login functionality on the HRDLOG.NET website does not work :-(
User avatar
G4POP
Log4OM Alpha Team
Posts: 10752
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: Problem with upload to HRDLOG service

Post by G4POP »

sp5ah wrote: 24 Mar 2023, 11:29 Now even the login functionality on the HRDLOG.NET website does not work :-(
Then something is wrong in your set up, have you asked HRDLog for a new upload code?

Ft8 or normal ssb loging


As you can see from my earlier post its working fine
73 Terry G4POP
sp5ah
Novice Class
Posts: 24
Joined: 11 Dec 2022, 11:51

Re: Problem with upload to HRDLOG service

Post by sp5ah »

Login issues resolved.
But unfortunately, using version LOG4OM 2.27.1, upload to HRDLOG.NET still doesn't work, despite using the correct Upload Code....
"upload result [ERROR] qso: Callsign: IM0A Date: 18/03/2023 10:40:15 Band: 10m Mode: USB
HRDLOG END"
User avatar
G4POP
Log4OM Alpha Team
Posts: 10752
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: Problem with upload to HRDLOG service

Post by G4POP »

sp5ah wrote: 24 Mar 2023, 14:00 Login issues resolved.
But unfortunately, using version LOG4OM 2.27.1, upload to HRDLOG.NET still doesn't work, despite using the correct Upload Code....
"upload result [ERROR] qso: Callsign: IM0A Date: 18/03/2023 10:40:15 Band: 10m Mode: USB
HRDLOG END"
was that with a new upload code?

Try enabling debug or trace mode in the help menu and see if there is more information after another attempted upload
73 Terry G4POP
User avatar
G4POP
Log4OM Alpha Team
Posts: 10752
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: Problem with upload to HRDLOG service

Post by G4POP »

Help/log level if I recall
73 Terry G4POP
sp5ah
Novice Class
Posts: 24
Joined: 11 Dec 2022, 11:51

Re: Problem with upload to HRDLOG service

Post by sp5ah »

Take a look at the log snippet. I blurred the UPLOAD CODE
I'm having trouble figuring out what it could be...
My Upload Code is OK.

"2023-03-24 17:29:02.8331 DEBUG: [FwFile][JsonSerializeObject] : JSON Serializing C:\Users\pluty\AppData\Roaming\Log4OM2\user\layout_datagrid_ManageConfirmation_user.json
2023-03-24 17:29:02.8331 DEBUG: [FwFile][WriteFile] : Begin writing text file C:\Users\pluty\AppData\Roaming\Log4OM2\user\layout_datagrid_ManageConfirmation_user.json
2023-03-24 17:29:02.8331 DEBUG: [FwFile][WriteFile] : Text file write completed C:\Users\pluty\AppData\Roaming\Log4OM2\user\layout_datagrid_ManageConfirmation_user.json
2023-03-24 17:29:02.8331 DEBUG: [FwFile][JsonSerializeObject] : Serialization completed C:\Users\pluty\AppData\Roaming\Log4OM2\user\layout_datagrid_ManageConfirmation_user.json
2023-03-24 17:29:06.7905 DEBUG: [dje_zXKBMXJSRAJJ29RCRXFDHD_ejd][MoveNext] : HRDLog update status not triggered. Check internet connection / HRDLog settings / CAT running status
2023-03-24 17:29:49.3127 DEBUG: [FwFile][ComposeFilename] : ComposeUserFilename: Returning USER file C:\Users\pluty\AppData\Roaming\Log4OM2\user\layout_datagrid_ManageConfirmation_user.json
2023-03-24 17:29:49.3127 DEBUG: [FwFile][JsonDeserializeObject] : Deserializing C:\Users\pluty\AppData\Roaming\Log4OM2\user\layout_datagrid_ManageConfirmation_user.json as L4ONG.BE.LAYOUT.DataGridViewStructure
2023-03-24 17:29:49.3127 DEBUG: [FwFile][LoadFile] : Begin load text file C:\Users\pluty\AppData\Roaming\Log4OM2\user\layout_datagrid_ManageConfirmation_user.json
2023-03-24 17:29:49.3127 DEBUG: [FwFile][LoadFile] : Text file load completed C:\Users\pluty\AppData\Roaming\Log4OM2\user\layout_datagrid_ManageConfirmation_user.json
2023-03-24 17:29:58.7342 INFO: [dje_zSYYTUD8GZSRMKJ8XVXQBZMYVU4KQ_ejd] : Massive upload of 1 on HRDLOG
2023-03-24 17:30:00.5653 INFO: [dje_zNR59ZFMSE76UKA8RVFEFQ8A973K78NVVKX_ejd] : [HRDLOG UPLOAD LOG] uploading LOG with 1 QSO
2023-03-24 17:30:00.5653 INFO: [dje_zJ6S8N7M4EZ6H9L5G84AECX8NUVJAHRAHKX_ejd] : [HRDLOG UPLOAD] Uploading QSO on HRDLOG: CT2GSN|19.03.2023 17:53:57|10m|USB
2023-03-24 17:30:00.5653 INFO: [dje_zJ6S8N7M4EZ6H9L5G84AECX8NUVJAHRAHKX_ejd] : [HRDLOG UPLOAD] Updating existing QSO on HRDLOG: CT2GSN|19.03.2023 17:53:57|10m|USB
2023-03-24 17:30:00.5653 INFO: [AdifManagement] : Begin export single QSO to ADIF string
2023-03-24 17:30:00.5653 INFO: [AdifManagement] : Export QSO to ADIF file completed
2023-03-24 17:30:00.5653 DEBUG: [dje_zJ6S8N7M4EZ6H9L5G84AECX8NUVJAHRAHKX_ejd][MoveNext] : [HRDLOG UPLOAD - UPDATE] payload:
CALLSIGN=SP5AH CMD=UPDATE ADIFKEY=<CALL:6>CT2GSN<QSO_DATE:8:D>20230319<TIME_ON:6>175357<EOR> CODE=XXXXXXXXXX APP=LOG4OM2 ADIFDATA=<CALL:6>CT2GSN <BAND:3>10M <MODE:3>SSB <QSO_DATE:8>20230319 <TIME_ON:6>175357 <DISTANCE:7>2517.89 <DXCC:3>272 <EQSL_QSL_RCVD:1>R <EQSL_QSL_SENT:1>Y <FREQ:9>28.450000 <GRIDSQUARE:6>IN51QM <LOTW_QSL_RCVD:1>R <LOTW_QSL_SENT:1>Y <SUBMODE:3>USB <STATION_CALLSIGN:5>SP5AH <QSL_RCVD:1>N <QSL_SENT:1>N <QSL_SENT_VIA:1>E <RST_RCVD:2>58 <RST_SENT:2>58 <EOR>
2023-03-24 17:30:00.5809 INFO: [dje_z37BXMBCLY4GPD83KQ22JD_ejd] : PostDataAsync: Posting data to http://robot.hrdlog.net/NewEntry.aspx. upload information:
CALLSIGN=SP5AH CMD=UPDATE ADIFKEY=<CALL:6>CT2GSN<QSO_DATE:8:D>20230319<TIME_ON:6>175357<EOR> CODE=XXXXXXXXXX APP=LOG4OM2 ADIFDATA=<CALL:6>CT2GSN <BAND:3>10M <MODE:3>SSB <QSO_DATE:8>20230319 <TIME_ON:6>175357 <DISTANCE:7>2517.89 <DXCC:3>272 <EQSL_QSL_RCVD:1>R <EQSL_QSL_SENT:1>Y <FREQ:9>28.450000 <GRIDSQUARE:6>IN51QM <LOTW_QSL_RCVD:1>R <LOTW_QSL_SENT:1>Y <SUBMODE:3>USB <STATION_CALLSIGN:5>SP5AH <QSL_RCVD:1>N <QSL_SENT:1>N <QSL_SENT_VIA:1>E <RST_RCVD:2>58 <RST_SENT:2>58 <EOR>
2023-03-24 17:30:01.0264 DEBUG: * [dje_z37BXMBCLY4GPD83KQ22JD_ejd][MoveNext][445 ms] : PostDataAsync: Post completed
<?xml version="1.0" ?>
<HrdLog xmlns="http://xml.hrdlog.com">
<NewEntry>
<error>Unable to find QSO</error></NewEntry>
</HrdLog>

2023-03-24 17:30:01.0264 DEBUG: [dje_zJ6S8N7M4EZ6H9L5G84AECX8NUVJAHRAHKX_ejd][MoveNext] : [HRDLOG UPLOAD - UPDATE] result:
<?xml version="1.0" ?>
<HrdLog xmlns="http://xml.hrdlog.com">
<NewEntry>
<error>Unable to find QSO</error></NewEntry>
</HrdLog>

2023-03-24 17:30:01.0264 DEBUG: [UCAdvancedListbox][AddRow] : [MESSAGE ON LISTBOX Upload Confirmations] upload result [ERROR] qso: Callsign: CT2GSN Date: 19.03.2023 17:53:57 Band: 10m Mode: USB
2023-03-24 17:30:01.0264 WARN: [dje_zJ6S8N7M4EZ6H9L5G84AECX8NUVJAHRAHKX_ejd][MoveNext] : [HRDLOG UPLOAD] update result [ERROR]
2023-03-24 17:30:01.0264 WARN: [dje_zJ6S8N7M4EZ6H9L5G84AECX8NUVJAHRAHKX_ejd][MoveNext] : [HRDLOG UPLOAD - UPDATE] payload:
CALLSIGN=SP5AH CMD=UPDATE ADIFKEY=<CALL:6>CT2GSN<QSO_DATE:8:D>20230319<TIME_ON:6>175357<EOR> CODE=XXXXXXXXXX APP=LOG4OM2 ADIFDATA=<CALL:6>CT2GSN <BAND:3>10M <MODE:3>SSB <QSO_DATE:8>20230319 <TIME_ON:6>175357 <DISTANCE:7>2517.89 <DXCC:3>272 <EQSL_QSL_RCVD:1>R <EQSL_QSL_SENT:1>Y <FREQ:9>28.450000 <GRIDSQUARE:6>IN51QM <LOTW_QSL_RCVD:1>R <LOTW_QSL_SENT:1>Y <SUBMODE:3>USB <STATION_CALLSIGN:5>SP5AH <QSL_RCVD:1>N <QSL_SENT:1>N <QSL_SENT_VIA:1>E <RST_RCVD:2>58 <RST_SENT:2>58 <EOR>
2023-03-24 17:30:01.0419 INFO: * [dje_zJ6S8N7M4EZ6H9L5G84AECX8NUVJAHRAHKX_ejd][476 ms] : [HRDLOG UPLOAD] ###### END ######
2023-03-24 17:30:01.0419 INFO: * [dje_zNR59ZFMSE76UKA8RVFEFQ8A973K78NVVKX_ejd][476 ms] : [HRDLOG UPLOAD LOG] ###### END ######
2023-03-24 17:30:01.0419 DEBUG: [UCAdvancedListbox][AddRow] : [MESSAGE ON LISTBOX Upload Confirmations] HRDLOG END
2023-03-24 17:30:05.3306 DEBUG: [FwFile][JsonSerializeObject] : JSON Serializing C:\Users\pluty\AppData\Roaming\Log4OM2\user\layout_datagrid_ManageConfirmation_user.json
2023-03-24 17:30:05.3306 DEBUG: [FwFile][WriteFile] : Begin writing text file C:\Users\pluty\AppData\Roaming\Log4OM2\user\layout_datagrid_ManageConfirmation_user.json
2023-03-24 17:30:05.3306 DEBUG: [FwFile][WriteFile] : Text file write completed C:\Users\pluty\AppData\Roaming\Log4OM2\user\layout_datagrid_ManageConfirmation_user.json
2023-03-24 17:30:05.3451 DEBUG: [FwFile][JsonSerializeObject] : Serialization completed C:\Users\pluty\AppData\Roaming\Log4OM2\user\layout_datagrid_ManageConfirmation_user.json
2023-03-24 17:30:06.9104 DEBUG: [dje_zXKBMXJSRAJJ29RCRXFDHD_ejd][MoveNext] : HRDLog update status not triggered. Check internet connection / HRDLog settings / CAT running status
"
Last edited by sp5ah on 24 Mar 2023, 20:47, edited 2 times in total.
Iw7dol
Novice Class
Posts: 19
Joined: 14 Dec 2022, 11:15

Re: Problem with upload to HRDLOG service

Post by Iw7dol »

G4POP wrote: 24 Mar 2023, 09:39
Iw7dol wrote: 24 Mar 2023, 09:07 The upload with HRDLOG was working until the last release: on 2.27 it doesn't work!
My guess is that you are using FT8 and have not followed the instructions here viewtopic.php?t=8260

Because I just auto uploaded two QSO's to HRDLog without issues, see below



Untitled.jpg
I followed the instructions of the new functions that complicate life. I also had to change the recommended ports because they were wrong. However, the upload doesn't work. Can you show me your settings?
I use JTDX+JT-Alert or WSJT-X only.
User avatar
KD0ZV
Log4OM Alpha Team
Posts: 730
Joined: 04 Mar 2015, 13:42
Location: Ankeny, Iowa
Contact:

Re: Problem with upload to HRDLOG service

Post by KD0ZV »

The ports are not recommended ports. They are specific to the apps on YOUR system. So check your 3rd party apps and configure the ports in Log4OM to match your other apps.
73,
Rich
KD0ZV
Log4OM Alpha Team
sp5ah
Novice Class
Posts: 24
Joined: 11 Dec 2022, 11:51

Re: Problem with upload to HRDLOG service

Post by sp5ah »

Problem still exists :-(
Post Reply