Exit Code 67

  • Thread starter Thread starter dave_uhrenholdt
  • Start date Start date
D

dave_uhrenholdt

I have a fairly simple Windows Forms application
developed using C#. It basically listens to two
serial ports and displays the results. There are
three threads that each listen to a network socket.
Additionally there is the GUI thread, the two
serial threads, and some threads to process the
data from the serial ports. For the serial communications
I am using John Hind's NETSerialComm wrapper library.
Occasionally, the tool will exit with error code 67.
When you look that up, it is listed as "The network name
cannot be found." At the time it happens there are
no network connections, just three sockets in listen
state. It can happen after 12 hours or 3 days. Or
not show up for a while.

Any insight into why this might happen is appreciated.

Dave Uhrenholdt
 
I have a fairly simple Windows Forms application
Click to expand...
^^ it's the most comple 'very simple application' I ever saw, hehehe...
developed using C#. It basically listens to two
serial ports and displays the results. There are
three threads that each listen to a network socket.
Additionally there is the GUI thread, the two
serial threads, and some threads to process the
data from the serial ports. For the serial communications
I am using John Hind's NETSerialComm wrapper library.
Occasionally, the tool will exit with error code 67.
When you look that up, it is listed as "The network name
cannot be found." At the time it happens there are
no network connections, just three sockets in listen
state. It can happen after 12 hours or 3 days. Or
not show up for a while.

Any insight into why this might happen is appreciated.
Click to expand...
I'm sure looking at the stacktrace might help!

be sure of catch all exception by putting a try/cath in the main and/or
doing Application.ThreadExceptionHandler += new ...(MyHandler)
 
Thanks for the reply. There is no exception to catch.
As far as I can tell the exit 67 is from unmanaged code.
And there is no stack trace. It would make me much
happier if I had that.

This application has plenty of odd ways of exitting,
such as an occasional "fatal execution engine error"
(sorry, I don't recall that exact text)
And offering to show me details, but being completely
frozen.
 
Check the port name used for the call to CreateFile. It should be in the
format of \\.\COMx. A malformed port name could look like a URI.
 
Back
Top