Page 1 of 1

Communicator failure

Posted: 28 Jan 2017, 01:33
by K4SHQ
There has been a discussion about JTAlertX having a logging failure. It just happened to me. I use Log4OM 1.27.0.0, and the failure seems to be connected to the Communicator app. I had to cycle the “Start” “Stop” buttons twice before logging was accepted. I do have “Auto Start” enabled.

Re: Communicator failure

Posted: 02 May 2017, 08:32
by G4POP
Sounds like Log4OM was not installed with 'Administrator Privileges'

Try a reinstall by right clicking the install file and selecting 'Run as administrator'