Communicator failure
Communicator failure
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
K4SHQ
- G4POP
- Log4OM Alpha Team
- Posts: 10803
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Communicator failure
Sounds like Log4OM was not installed with 'Administrator Privileges'
Try a reinstall by right clicking the install file and selecting 'Run as administrator'
Try a reinstall by right clicking the install file and selecting 'Run as administrator'
73 Terry G4POP