Log4OM

After upgrading to v1.23 Communicator is not starting (or running). I am running Log4OM as administrator. I found the Communicator program and tried starting it directly, same result - it doesn't show as running. I'm running Windows 10, and had no problems with the v1.22 release.

I looked in the log and found the following...

2015-10-30 18:40:34.7083 INFO: TCPServer: Executing C:\Program Files (x86)\IW3HMH\Log4OM\Log4OmCommunicator.exe TCPPORT:8081 HRDLOGUSER: HRDLOGUPCODE:
2015-10-30 18:40:36.6341 INFO: #=qrGvgWCI4nx4c02zh4fJZUgHGvVD28SKtUPp0qU388HM=: BEGIN SAVE CONFIG
2015-10-30 18:40:36.6422 ERROR: *** #=qrGvgWCI4nx4c02zh4fJZUgHGvVD28SKtUPp0qU388HM=: Path cannot be the empty string or all whitespace. ******* [Function: #=q19JrFY9vi0ayj5wP7h5NIQ==] System.ArgumentException: Path cannot be the empty string or all whitespace.
at System.IO.Directory.CreateDirectory(String path)
at #=qrGvgWCI4nx4c02zh4fJZUgHGvVD28SKtUPp0qU388HM=.#=q19JrFY9vi0ayj5wP7h5NIQ==()
2015-10-30 18:40:36.6682 INFO: #=qrGvgWCI4nx4c02zh4fJZUgHGvVD28SKtUPp0qU388HM=: SAVE CONFIG COMPLETED

Bill - WB9KPT

Hi Bill,

If you like, email me at svtdoug (at) gmail.com, or send a PM, and we can set up a TeamView session and try to get this corrected. It looks like something in your setup is amiss which is preventing Communicator from starting.

Doug - W7DRM

Thanks Doug, I will send you an email.

Bill - WB9KPT

i'll check the code. That sounds like a strange working folder...

There is something "corrupted" in your configuration file.
The error happens when Log4Om tries to save the configuration file.
This is really strange, because configuration file path is determined on program start.

This could be a corrupted installation or something else. I'm investigating on that

Daniele... Doug and I had a Teamviewer session yesterday, where he captured additional information from my computer. Please check with him for an update.

Bill - WB9KPT

I am pleased to report after much work on Bill's part, he found the culprit. There was a program conflict in his Windows 10 system between Communicator and Logitech Process Monitor (LVPrcSrv.exe), associated with Logitech Web Cameras. He found that this program has a history of causing other programs to crash, or not start. The key to finding the cause was to start his computer in SAFE mode, which allowed the Communicator to run. Then is was a matter of one by one eliminating each program in the start up routine until he found that one which was causing Communicator to not run. After disabling LVPrcSrv.exe from starting, no further issues with Communicator running.

Doug - W7DRM

wow... i will never heard nothing about that... good catch!