Log4OM

Hi,

I have done for Clublog as I have for eQSL and LOTW and selected the required QSOs and then pressed the "upload selected" button and nothing happens.

How is this feature supposed to work?

73 de Guy G4DWV 4X1LT

Check the log in the help menu and you will see the upload was done

G4POP wrote: 17 Mar 2018, 09:38 Check the log in the help menu and you will see the upload was done

I can't tell by watching the program that anything was done either. I did get a confirmation email back from Club Log, but that was the only way I knew it uploaded. The log does not show that you uploaded to Club Log. Not sure why the visual indications were left out of this upload as compared to Eqsl and LoTW - both having progress bars. Just a suggestion: why not have those for the Club Log upload?

All I see in the log is this bunch of computer nastiness that probably only the software engineer-in-charge can figure out -

2018-03-17 12:11:30.7759 ERROR: *** ClubLogManagement: The remote server returned an error: (403) Forbidden. ******* [Function: #=qWBeag2WF4F1lqzZk1i75ew==] System.Net.WebException: The remote server returned an error: (403) Forbidden.
at System.Net.HttpWebRequest.GetResponse()
at LogOM.BL.ClubLogManagement.#=qWBeag2WF4F1lqzZk1i75ew==(QSO #=q_i9g4otYM2xPTjRiRzTwfg==, String #=qnFO0ewzNxzzNoVveE85fzA==, String #=qtOoPEeRD7dt$P2fLN6efXg==, String #=qOeB1M_J079yURlmipCXx5g==, String #=qk_KU0eGB2$vMYwc3$Pf87Q==, String #=qPEiTz1bYkcMJI1KJTP0yvQ==)
2018-03-17 12:11:30.7759 ERROR: *** ClubLogManagement: Delete QSO from ClubLog caught in error ******* [Function: #=qt_toA8VH$IIdRX02Bf6FTzvRrgfuKTCD4g2sSESGmK8=] System.Net.WebException: The remote server returned an error: (403) Forbidden.
at System.Net.HttpWebRequest.GetResponse()
at LogOM.BL.ClubLogManagement.#=qWBeag2WF4F1lqzZk1i75ew==(QSO #=q_i9g4otYM2xPTjRiRzTwfg==, String #=qnFO0ewzNxzzNoVveE85fzA==, String #=qtOoPEeRD7dt$P2fLN6efXg==, String #=qOeB1M_J079yURlmipCXx5g==, String #=qk_KU0eGB2$vMYwc3$Pf87Q==, String #=qPEiTz1bYkcMJI1KJTP0yvQ==)
at LogOM.BL.ClubLogManagement.#=qt_toA8VH$IIdRX02Bf6FTzvRrgfuKTCD4g2sSESGmK8=(Object #=qY0kuyoZPZuKVZcdUKzhlEg==, DoWorkEventArgs #=qbxrfHs0kD3_NVOCcKhnJng==)
2018-03-17 12:11:30.9947 ERROR: *** ClubLogManagement: Delete caught in error with code:

Yes a visual indicator is essential and will be include in the next release, we rushed thus one out because Clublog and IOTA made some Changes that broke many external software packages like Log4om, DXLabs, Logger32 Tec

For now make sure you update your Clublog password and replicate the update in the Log4om settings

G4POP wrote: 17 Mar 2018, 13:22 Yes a visual indicator is essential and will be include in the next release, we rushed thus one out because Clublog and IOTA made some Changes that broke many external software packages like Log4om, DXLabs, Logger32 Tec

For now make sure you update your Clublog password and replicate the update in the Log4om settings

Can you please elucidate on whether we need a new "App Password" at Clublog, or do we use our regular user name and password? I saw in another thread that somebody says we need to now use an "App Password" for Log4OM.

Thanks.

N5INP wrote: 17 Mar 2018, 13:35

G4POP wrote: 17 Mar 2018, 13:22 Yes a visual indicator is essential and will be include in the next release, we rushed thus one out because Clublog and IOTA made some Changes that broke many external software packages like Log4om, DXLabs, Logger32 Tec

For now make sure you update your Clublog password and replicate the update in the Log4om settings

Can you please elucidate on whether we need a new "App Password" at Clublog, or do we use our regular user name and password? I saw in another thread that somebody says we need to now use an "App Password" for Log4OM.

Thanks.

This is necessitated because Clublog made server changes

Yep, got the confirmation emails that the upload actually worked.

Only one error and that was in a QTH that Clublog changed.

73 de Guy G4DWV 4X1LT