¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Clublog Upload TImeout


 

I've been getting the "the connection with ClubLog terminated before the upload completed" message when trying to upload to Clublog. Is this normal until the Clublog servers get back to normal from doing the CoVID-19 research?

From the ErrorLog.txt

2020-04-12 11:44:48.137 > ClubLogModule.UploadFile: upload initiated
2020-04-12 11:44:48.138 > ClubLogModule.UploadFile: OperationCompleted = false in upload completion loop
2020-04-12 11:44:48.138 > ClubLogModule.HandleInetStateChange, theState = 3(Connecting), OperationCompleted = False
2020-04-12 11:44:48.139 > ClubLogModule.HandleInetStateChange: connecting to Club Log host
2020-04-12 11:44:48.140 > ClubLogModule.UploadFile: OperationCompleted = false in upload completion loop
2020-04-12 11:44:48.141 > ClubLogModule.UploadFile: OperationCompleted = false in upload completion loop


 

No this isn't normal. Even with the shift in computing resources on the Club Log side, they are still processing the normal workload, it just takes longer. I've uploaded numerous times since the announcements. I just did another upload and it went fine.

73,
Mike ND9G


On Sun, Apr 12, 2020 at 7:24 AM Sherman Banks <w4atl@...> wrote:
I've been getting the "the connection with ClubLog terminated before the upload completed" message when trying to upload to Clublog. Is this normal until the Clublog servers get back to normal from doing the CoVID-19 research?

From the ErrorLog.txt

2020-04-12 11:44:48.137 > ClubLogModule.UploadFile: upload initiated
2020-04-12 11:44:48.138 > ClubLogModule.UploadFile: OperationCompleted = false in upload completion loop
2020-04-12 11:44:48.138 > ClubLogModule.HandleInetStateChange, theState = 3(Connecting), OperationCompleted = False
2020-04-12 11:44:48.139 > ClubLogModule.HandleInetStateChange: connecting to Club Log host
2020-04-12 11:44:48.140 > ClubLogModule.UploadFile: OperationCompleted = false in upload completion loop
2020-04-12 11:44:48.141 > ClubLogModule.UploadFile: OperationCompleted = false in upload completion loop


 

It's working again, but I'm not sure exactly why it's fixed. I determined that the upload was not making it to Clublog by changing to an incorrect Clublog password and the error messages stayed the same. I verified that DXKeeper is an approved app in the Firewall. On a whim, I turned Firewall off and it still had the problem. WIth Firewall still off, I rebooted the computer, and the upload was successful. I turned Firewall back on, rebooted, and it was still successful.? Very strange.?


 

+ AA6YQ comments below

On Tue, Apr 14, 2020 at 08:02 AM, Sherman Banks wrote:

It's working again, but I'm not sure exactly why it's fixed. I determined that the upload was not making it to Clublog by changing to an incorrect Clublog password and the error messages stayed the same. I verified that DXKeeper is an approved app in the Firewall. On a whim, I turned Firewall off and it still had the problem. WIth Firewall still off, I rebooted the computer, and the upload was successful. I turned Firewall back on, rebooted, and it was still successful.? Very strange.?

+ Based on your description, there are several possible culprits, but DXKeeper isn't one of them.

? ? ? ?73,

? ? ? ? ? ? Dave, AA6YQ

?


 

Perhaps ClubLog was not accepting uploads/log-ins temporarily:

<>

73,

... Joe, W4TV

On 2020-04-14 11:02 AM, Sherman Banks wrote:
It's working again, but I'm not sure exactly why it's fixed. I determined that the upload was not making it to Clublog by changing to an incorrect Clublog password and the error messages stayed the same. I verified that DXKeeper is an approved app in the Firewall. On a whim, I turned Firewall off and it still had the problem. WIth Firewall still off, I rebooted the computer, and the upload was successful. I turned Firewall back on, rebooted, and it was still successful.? Very strange.


 

+ Based on your description, there are several possible culprits, but DXKeeper isn't one of them.

I agree Dave. DXKeeper wasn't the problem and never thought it was since it's worked for years. At first I thought it was a Clublog issue, like what W4TV linked to. But after a month of this I decided to post and do some troubleshooting. I'm not sure if my tinkering with the Windows Defender Firewall did something or not. But at least it's working and hopefully will stay working!

No doubt these Windows "upgrades" will continue to provide hours of troubleshooting fun!