I have the exact problem that started a week ago!
73
NJ0F
LOTW upload Freezes
-
G4POP
- Log4OM Alpha Team
- Posts: 11210
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: LOTW upload Freezes
Has to be one of the reasons previously discussed in this thread like expired cert or wrong set up, Log4OM does not suddenly stop working unles there is some local or internet issue.
I just tested upload and download and bot worked fine version 2.33, see image below
- Untitled.png (33.85 KiB) Viewed 2703 times
73 Terry G4POP
Re: LOTW upload Freezes
I'm having the exact same issue.
LOTW uploads will lockup if I do more than 10 or 11 at a time. And lockups require me to restart Log4OM. VERY frustrating.
The stop point is always "MANAGED MODE SET" in TSql.
QRZ uploads worked better but it locked up when I tried to to 100. However, those did not require a restart of the program.
The connection to TSql seems fragile for sure. And if it's that sensitive to windows and other updates thats a big issue that needs addressing.
LOTW uploads will lockup if I do more than 10 or 11 at a time. And lockups require me to restart Log4OM. VERY frustrating.
The stop point is always "MANAGED MODE SET" in TSql.
QRZ uploads worked better but it locked up when I tried to to 100. However, those did not require a restart of the program.
The connection to TSql seems fragile for sure. And if it's that sensitive to windows and other updates thats a big issue that needs addressing.
Re: LOTW upload Freezes
Same here LOTW freeze
I try already
-new cert
-with/without password
seems related to the amount if I upload 1 or 5 QSO at a time all is ok
I try already
-new cert
-with/without password
seems related to the amount if I upload 1 or 5 QSO at a time all is ok
w7btm wrote: ↑14 Oct 2024, 22:57 I'm having the exact same issue.
LOTW uploads will lockup if I do more than 10 or 11 at a time. And lockups require me to restart Log4OM. VERY frustrating.
The stop point is always "MANAGED MODE SET" in TSql.
QRZ uploads worked better but it locked up when I tried to to 100. However, those did not require a restart of the program.
The connection to TSql seems fragile for sure. And if it's that sensitive to windows and other updates thats a big issue that needs addressing.
Re: LOTW upload Freezes
That's interresting. Hard to say if it's an issue with Log4OM or TSQL....
Re: LOTW upload Freezes
An Observation on the "LOTW Upload Freezes" situation.
The below is just my 'observation' and 'experience' and may be 'food for thought' (or not). Meaning that it may or may not trigger a thought that might help some OMs find something that will help resolve their situation with this matter.
================
I used to use Log4OM V1 and when Log4OM V2 was released I started using it and have been using it since that time.
Each/every installation/update of Log4OM V2 has always simply followed the recommended 'path' locations for all the various elements that are part of Log4OM V2. In that I have never selected any external, cloud drive or ever chosen any drive (IE: D, G, whatever) save for the default "C" drive as is the basis in the Windows O/S world.
Same goes for my installation of TQSL. I let the TQSL installer put its related elements in their default locations.
As for setting up LOTW in Log4OM V2 ... I followed what is in the User Guide and the information provided by Terry in his multiple YouTube videos. I went over those videos and the User Guide information several times to ensure that my settings were matching in case I had a typo, etc..
I've also tested the LOTW Upload on Close and it also worked FB for me. I no longer use that feature as I just prefer to physically have a hand in my LOTW uploads so do that via the QSL Manager. A few extra key-clicks and a minute or two of my time for such is not a big deal.
FWIW I've used Log4OM V2 in both the Windows 10 Pro and Windows 11 Pro O/S. All my installations have been on very 'mature' (IE: old) Dell laptops. I finally was able to get a new Dell laptop about one year ago as I just couldn't find parts to keep my 'mature' laptop running. And ... no LOTW Upload Freezes experienced on any of my installations.
I have also uploaded quantity counts of over 200 Q's and most often my uploads range from 50 to 175 several times each week. I have NEVER experienced any 'freeze' of the LOTW uploads in all my years of using Log4OM V2.
I have spent hours reviewing this thread (and others in the Forum) related to the same issue, but have never been able to replicate what has been posted about.
I don't have any magical wand for a possible solution and there 'might be' some glitch in the code, but if that were the case I'm sure that far more OMs would be adding their input about such.
No two installations are alike and each of us have our own ways of setting up our computers and how we load programs on them and often in such variances there might be some very small difference that is the culprit of this issue.
So ... my final thoughts are that it might be wise to take a step back and make notes of your overall installation. Is it done to the default folders/locations? Is TQSL installed to the default folders/locations? I strongly suggest using your local PC's "C" drive for both and go from there and do not install on any remote or cloud drive. Make sure your syntax is proper in the LOTW and TQSL setup and (again) keep the folders/path on your 'local' drive ... NOT a cloud/remote drive.
Finally ... the above are just my observations and 'maybe' those thoughts may be of assistance and then again they may not. However ... give it some thought and review your overall installation and settings very carefully.
The below is just my 'observation' and 'experience' and may be 'food for thought' (or not). Meaning that it may or may not trigger a thought that might help some OMs find something that will help resolve their situation with this matter.
================
I used to use Log4OM V1 and when Log4OM V2 was released I started using it and have been using it since that time.
Each/every installation/update of Log4OM V2 has always simply followed the recommended 'path' locations for all the various elements that are part of Log4OM V2. In that I have never selected any external, cloud drive or ever chosen any drive (IE: D, G, whatever) save for the default "C" drive as is the basis in the Windows O/S world.
Same goes for my installation of TQSL. I let the TQSL installer put its related elements in their default locations.
As for setting up LOTW in Log4OM V2 ... I followed what is in the User Guide and the information provided by Terry in his multiple YouTube videos. I went over those videos and the User Guide information several times to ensure that my settings were matching in case I had a typo, etc..
I've also tested the LOTW Upload on Close and it also worked FB for me. I no longer use that feature as I just prefer to physically have a hand in my LOTW uploads so do that via the QSL Manager. A few extra key-clicks and a minute or two of my time for such is not a big deal.
FWIW I've used Log4OM V2 in both the Windows 10 Pro and Windows 11 Pro O/S. All my installations have been on very 'mature' (IE: old) Dell laptops. I finally was able to get a new Dell laptop about one year ago as I just couldn't find parts to keep my 'mature' laptop running. And ... no LOTW Upload Freezes experienced on any of my installations.
I have also uploaded quantity counts of over 200 Q's and most often my uploads range from 50 to 175 several times each week. I have NEVER experienced any 'freeze' of the LOTW uploads in all my years of using Log4OM V2.
I have spent hours reviewing this thread (and others in the Forum) related to the same issue, but have never been able to replicate what has been posted about.
I don't have any magical wand for a possible solution and there 'might be' some glitch in the code, but if that were the case I'm sure that far more OMs would be adding their input about such.
No two installations are alike and each of us have our own ways of setting up our computers and how we load programs on them and often in such variances there might be some very small difference that is the culprit of this issue.
So ... my final thoughts are that it might be wise to take a step back and make notes of your overall installation. Is it done to the default folders/locations? Is TQSL installed to the default folders/locations? I strongly suggest using your local PC's "C" drive for both and go from there and do not install on any remote or cloud drive. Make sure your syntax is proper in the LOTW and TQSL setup and (again) keep the folders/path on your 'local' drive ... NOT a cloud/remote drive.
Finally ... the above are just my observations and 'maybe' those thoughts may be of assistance and then again they may not. However ... give it some thought and review your overall installation and settings very carefully.
73 - Nolan Kienitz - KI5IO
Plano, TX
Plano, TX
-
G4POP
- Log4OM Alpha Team
- Posts: 11210
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: LOTW upload Freezes
Nothing can change as log4om doesn't download patches or other things so if the problem arises in the same version the user has used for some time the problem is not in the Log4OM software its something local
73 Terry G4POP
Re: LOTW upload Freezes
Answer in the style of "it works for me" 
The problem is real, it occurs for many users. For me, sending the log to LOTW does not work when I send more than 10 items.
Win 8.1 32bit, LOG4OM v. 2.33.0.0, tQSL v. 2.7.5
By the way, LOG4OM is the best, thanks for it
The problem is real, it occurs for many users. For me, sending the log to LOTW does not work when I send more than 10 items.
Win 8.1 32bit, LOG4OM v. 2.33.0.0, tQSL v. 2.7.5
By the way, LOG4OM is the best, thanks for it
