Communicator failure

Yes, sometimes it happens... Please report any bugs here
Post Reply
dmalcolm
Advanced Class
Posts: 47
Joined: 03 Nov 2015, 13:31

Communicator failure

Post by dmalcolm » 28 Jan 2017, 01:33

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.
Dan Malcolm
K4SHQ

User avatar
G4POP
Moderator
Posts: 5537
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: Communicator failure

Post by G4POP » 02 May 2017, 08:32

Sounds like Log4OM was not installed with 'Administrator Privileges'

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

Post Reply