cat: an unhandled error has occurred:

  • 1
  • Problem
  • Updated 2 years ago
  • Acknowledged
I had been running smartsdr for about 2 hours; I had 4 wsjtx sessions running; The 6m one lost rig control and I found this dialog box:


restarting cat, and doing retry's on the wsjtx sessions got things going again.

In the windows events I found this:
Application: Cat.exeFramework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Net.Sockets.SocketException
   at System.Net.Sockets.Socket.BeginReceive(Byte[], Int32, Int32, System.Net.Sockets.SocketFlags, System.AsyncCallback, System.Object)
   at System.Net.Sockets.NetworkStream.BeginRead(Byte[], Int32, Int32, System.AsyncCallback, System.Object)

Exception Info: System.IO.IOException
   at System.Net.Sockets.NetworkStream.BeginRead(Byte[], Int32, Int32, System.AsyncCallback, System.Object)
   at CatWPF.Ports.PortCommunication.TCPReadCallback(System.IAsyncResult)
   at System.Net.LazyAsyncResult.Complete(IntPtr)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Net.ContextAwareResult.Complete(IntPtr)
   at System.Net.LazyAsyncResult.ProtectedInvokeCallback(System.Object, IntPtr)
   at System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
   at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
Photo of NM1W

NM1W

  • 133 Posts
  • 24 Reply Likes

Posted 2 years ago

  • 1
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9148 Posts
  • 3466 Reply Likes
What version of SmartSDR are you running?

This error indicates that one of the CAT TCP connections (probably port 5002 to DDUtil) was closed improperly (forced closed).

I have entered this problem report into our bug tracker (defect #4021) for additional investigation. Thank you for the defect report.
(Edited)
Photo of NM1W

NM1W

  • 133 Posts
  • 24 Reply Likes
1.9.7
I've seen it happen twice.
I do run DDUTIL, however I also run 4 wsjtx sessions(1.7.0-rc1 releases), and use tcp ports for the cat control; specifically localhost:60004..7
I usually know there is an issue since wsjtx alerts about rig control failure..
I've not seen any issues with ddutil..
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9148 Posts
  • 3466 Reply Likes
Regardless the app that is connecting to the CAT TCP/IP port, it is abnormally aborting the TCP socket.  That needs to be reported as a bug to the developers of the software that you are connecting to.