Log4OM

Twice within the last 12 hours I have had two "Log4OM has stopped working" events. Of course the only solution at that time is to OK it and it gets shut down. I'll try to provide a screen shot the next time it happens if that helps.

Has anyone else experienced this? Any idea where to start looking.

Thanks.

Jim W1RET

Check the log file and see if it indicates why it malfunctioned, hint it's in your c:\...........\roaming\logom\logs folder

Thanks for the response Terry.

I found the files you mentioned. In the one labeled ....20141116 here are the last two lines..

2014-11-16 13:52:42.5443 INFO: #=qZSFStBZTniSy2UBNQshJ58shaBtyqbAo_e4QypP1aJQ=: *Calling CLUSTER FORM*
2014-11-16 13:52:50.0143 INFO: #=qZSFStBZTniSy2UBNQshJ58shaBtyqbAo_e4QypP1aJQ=: *Calling CLUSTER FORM*

In the file ....20141115 here are the last couple of lines.

at XmlRpcProxy237e3e4b-c760-45f0-a32e-7e372ec8a6d6.SetMode(String mode)
at Log4OmCommunicator.BL.FldigiManagement.SetMode(String mode)
2014-11-16 05:52:26.4241 ERROR: *** TCPClientManager: Socket error during Read: [SocketException] An existing connection was forcibly closed by the remote host

Am I on the right track?

If I assume that the time listed in the lines is local time then this is about the time things stopped working.

Thanks.

Jim W1RET

Is the computer a laptop? I am wondering if either the hard drive is power saving or something similar?

Terry,

No, its a desktop. And both times I was sitting in front of it when it occurred.

I usually let it run 24X7 so maybe it's time for a power cycle. Then wait to see if it occurs again. Stranger things have happened. Of course it is always reports that Windows is searching for a solution. They must still be searching.

Jim W1RET

See what happens after a recycle, if it happens again set debug mode in the help menu, leave the program running and when it happens agai email us the log file

Please send me your logfile using HELP function for creating a support request.
(you should mail the zip file to my pvt mail)

Please refer to this topic in your mail, so i can easily find the issue