Log4OM will not shut down. I have attached a screen shot of the stopped shutdown window. The only way I can completely shutdown the program is to go to the Task Manager and END the task.
Help please.
Steve - N6RSH
Will not Shut Down
Will not Shut Down
- Attachments
-
- Screenshot 2022-08-08 125101.png (35.56 KiB) Viewed 44565 times
Re: Will not Shut Down
Steve,
Take a look at your log file ... found at: Help / Open log file
It will likely give you a clue as to error encountered when closing Log4OM.
Also ... go into: Settings / Program Configuration / External Services / LOTW ... and untic the box for Automatic upload on application close.
This will stop the "Auto Upload" of your LOTW Q's when Log4OM closes.
Check to make sure that you have the most current version of TQSL installed on your computer. I've attached a screen clip of the most current version that I have on my PC.
Also ... what version of Log4OM are you using? The current version is: v2.23.0.0
Make sure you have the current versions of both of those APPs.
I'm going to guess that when you turn off LOTW Auto Upload that Log4OM will close without too much delay.
Take those steps and and let me know how you get on.
Take a look at your log file ... found at: Help / Open log file
It will likely give you a clue as to error encountered when closing Log4OM.
Also ... go into: Settings / Program Configuration / External Services / LOTW ... and untic the box for Automatic upload on application close.
This will stop the "Auto Upload" of your LOTW Q's when Log4OM closes.
Check to make sure that you have the most current version of TQSL installed on your computer. I've attached a screen clip of the most current version that I have on my PC.
Also ... what version of Log4OM are you using? The current version is: v2.23.0.0
Make sure you have the current versions of both of those APPs.
I'm going to guess that when you turn off LOTW Auto Upload that Log4OM will close without too much delay.
Take those steps and and let me know how you get on.
- Attachments
-
- TQSL-version_080322.JPG (54.46 KiB) Viewed 44562 times
73 - Nolan Kienitz - KI5IO
Plano, TX
Plano, TX
Re: Will not Shut Down
Thank you for the help.
Success!! Un-checking 'Automatic ... close' seems to have solved the problem.
All of my applications are up to date, by the way.
Again thanks. I am looking forward to enjoying Log4OM more in the future. 73,
Steve - N6RSH
Success!! Un-checking 'Automatic ... close' seems to have solved the problem.
All of my applications are up to date, by the way.
Again thanks. I am looking forward to enjoying Log4OM more in the future. 73,
Steve - N6RSH
Re: Will not Shut Down
Guys, have same issue but is there a solution if I want to keep the auto upload to LOTW?
Thanks
Paul
Version number of TQSL and Log4OM would help us!
Thanks
Paul
Version number of TQSL and Log4OM would help us!
Re: Will not Shut Down
Apologies,
ver 2.23.0.0
TQSL ver 2.6.5
ver 2.23.0.0
TQSL ver 2.6.5
Re: Will not Shut Down
Hi guys i have the same problem. the LOG4OM doesn´t shutdown. i have the autoupload on for the LOTW and i want keep it like that way. If you can help me please let me know. TQSL V2.7.2 - LOG4OM v 2.30.1.0. Best regards
José - CT1EDG
José - CT1EDG
Re: Will not Shut Down
I have the same problem and un-ticking the LOTW auto upload does indeed resolve the issue. However, when I attempt to manually upload selected records it says “managed mode” then does nothing. If I attempt it again it says “End LOTW” I can’t find anything in the logs that indicate why that would happen?? Thanks
Re: Will not Shut Down
Did you resolve this problem? If so what did you do?
TNX
Bret C / AC0AE
TNX
Bret C / AC0AE
Re: Will not Shut Down
Same issue here. I looked at the help log and there may have been an issue communicating on the port set for FLDigi. I unchecked the box to activate and tried again. Still the same unable to close issue. I unchecked the auto upload to LOTW....and it closed as expected...but got a runtime error shown in the pic. I shut down and restarted....closed and this time no runtime error. I opened TQSL and it need an update. Did the update and it did not solve the problem. I was hoping the new Log4OM update would have fixed this but apparently not.
Thanks and 73
Greg AB7R
Thanks and 73
Greg AB7R
73,
Greg - AB7R
Caldwell, ID
Greg - AB7R
Caldwell, ID