Log4OM

Trying to get Log4OM up and running before I make the switch from HRD.
Running Windows10
Checked Windows Task Manager to make sure no programs are running.
Log4OM set to run as administrator
Log4OM Communicator set to run as administrator
When I start Log4OM I get an error "Application is already running. Continue?" I click OK and Log4OM starts up. It connects to the rig, brings up the correct database, then I get another error when the Log4OM Communicator tries to start "Application is already running" I click OK and the communicator shuts down and I can't get it to start. There is no log for the communicator. Attached is the Log4OM log and pics of the two error messages.
Any help would be appreciated.
Ken, AC5EZ

Try rebooting your computer and make sure that you only attempt to open Log4OM once

This happens if the program has not finished loading and the user attempts to start the program again.

Tried the power off power on sequence several times.
Launched Log4OM as first app to load and still get the same response.
Have checked Task Manager to double check no instances of program is running.
Could there be something in my configuration settings inside Log4OM to is causing the problem?
Tks,
ken, AC5EZ

ac5ez wrote:Tried the power off power on sequence several times.
Launched Log4OM as first app to load and still get the same response.
Have checked Task Manager to double check no instances of program is running.
Could there be something in my configuration settings inside Log4OM to is causing the problem?
Tks,
ken, AC5EZ

Please send me the bug report from the help menu and include the ADIF file by email to g4pop (AT) arrl.net

DO NOT POST THE FILE ON THIS FORUM

Hi, i'm checking the routine for flaws or possible reasons.
Stay tuned...

Hello @ all.

I got the same popup when i have closed Log4OM but communicator don´t shutting down with L4O (from time to time i have this problem). If i then start again i got the same error message. I simply click on continue and the program starts.

I have reported this problem (communicator sometimes not shutting down) several month ago in the Beta community and nobody have had an idea. But it´s not a big problem for me. Most time i check my taskbar when i´ve shutted down L40. If communicator is still running i close manually

I think I know how the problems occurred. There was a RTTY contest, several weeks ago, that I wanted to work using Log4OM and FLdigi. In trying to setup the programs to talk to each other I stopped and started each program many, many times in one day. Here is what I observed. When the Communicator starts up it tries to establish a UDP port connection for incoming QSO's and a TCP port to talk to FLdigi. Even though the ports are all localhost connections there could be a slight delay in establishing these connections. And the same holds true when shutting down the applications. I think what happened was I would stop Log4OM and then restart it again, not giving the Communicator time to drop the UDP/TCP links. So now you have a program trying to close all the data links and at the same time a second occurrence of the program trying to establish the same links, hence double pointers in the registry.  I verified this just the other day. I actually caused double entries of the Communicator, in the PC registry, by shutting down Log4OM and then restarting it before the Communicator had time to drop all the data links. Some PC’s have a slight delay in the time it takes to drop the data channels so be sure to wait for the communicator to close the UDP and TCP links before you try to restart Log4OM. I have also noticed there are times when I stop Log4OM that the Communicator does not shutdown on its own. If this happens you need to manually stop the Communicator before you restart Log4OM again.