Communicator stops working

[NA4MM]

I have a problem with the Communicator program stopping.
It run fine for a few minutes then stops.
It affects PstrotatorAZ and updating the log from JTAlert.
I can restart the Communicator and JTAlert will update but will stop again.
JT65-HF HB9HQX is sending the record fine to JTAlert.
Once PstRotatorAZ stops I cannot get it to work until I reload Log4OM.
I am running:
Windows 10 / 64bit,
Log4OM V. 1.24.0.0,
PstRotatorAZ V. 11.96
JTAlert V. 2.6.28
JT65-HF HB9HQX V. 2.0

Thanks
Paul NA4MM

[NN7D]

Hi Paul,

Make sure you are running Log4OM as Administrator. To do this - on the shortcut for Log4OM, right click, click Properties, on the Compatibility tab check Run this program as an administrator, then click OK.

If that does not cure the issue, then try restarting the computer in SAFE mode. If Communicator then runs, you could have a conflict with a driver or other program which is running.

Doug - W7DRM

[IW3HMH]

If you can reproduce the issue please fill a support request from log4om HELP menu and send us the packaged ZIP with informations (not on forum as it contains some private info's)

[NA4MM]

After working with this a few days and trying everything I have it working better now.
In the Communicator settings, Inbound I had enable File Monitoring. Why I don't know.
When I unchecked that box it went back to working.
If I stop the Communicator and start it back the rotor part does not work until I reload Log4OM again. That's OK.

I want to thank everyone for there help.
I sure do love this program.

73 Paul NA4MM

[G4POP]

After working with this a few days and trying everything I have it working better now.
In the Communicator settings, Inbound I had enable File Monitoring. Why I don't know.
When I unchecked that box it went back to working.

That was probably the problem if you were trying to monitor a file type that it is not designed to monitor