Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 36 replies
  • Subscribers 20 subscribers
  • Views 34013 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

System.IO.IOException: Pipe is broken

DrewbleIT

Starting Dec 21st we started seeing a tremendous amount of errors on both our Server Infrastructure and Endpoint devices.  This created issues with certain .NET related applications on end users workstations that required restarting various applications. One application particularly troublesome was Mimecast For Outlook. Upon investigating we found that the only resolution to fix these errors was to completely remove Sophos (obviously that's not a solution nor a risk we're willing to take). 

Sample Errors - 

28-12-2020 09:07:41,964 ERROR [12] HOST: Domain Unhandled Exception: System.IO.IOException: The pipe is being closed.

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.Pipes.NamedPipeServerStream.BeginWaitForConnection(AsyncCallback callback, Object state)
   at System.IO.Pipes.NamedPipeServerStream.WaitForConnection()
   at Mimecast.Mapi.Remote.NamedPipesServer.AcceptPipeConnection(IAsyncResult asyncResult)
   at System.IO.Pipes.NamedPipeServerStream.AsyncWaitForConnectionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOverlapped)
   at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP). IsTerminating: True (Program)

Message=Application: msddsk.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.IOException
   at System.IO.__Error.WinIOError(Int32, System.String)
   at System.IO.Pipes.PipeStream.WinIOError(Int32)
   at System.IO.Pipes.NamedPipeServerStream.GetImpersonationUserName()
   at Mimecast.Mapi.Remote.NamedPipesServer.AcceptPipeConnection(System.IAsyncResult)
   at System.IO.Pipes.NamedPipeServerStream.AsyncWaitForConnectionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
   at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)

Is anyone else seeing this? We'll certainly open a Ticket with support but wanted to also understand the scope. 



This thread was automatically locked due to age.
Parents Reply
  • 0 in reply to DrewbleIT

    Sophos Support Case 03493304 if needed by members of support. Yes we are MTR Customers.

    In my testing it appeared to be this service that was the cause of the error: Sophos Device Encryption Service (it calls upon the Sohops.Encryption.BitlockerService.exe I listed above). I set the service to Manual instead of Automatic Delayed Start, and while Sophos freaked out, I did not receive the Mimecast error. Looks like this service is running/set to Automatic Delayed Start even if the device is not configured with Sophos Bitlocker encryption.

Children
  • 0 in reply to Justin Rutkowski

    Can you give this a try as well? Disable the MTR service. We had to do this on the server side and are currently testing the workstation side. I currently believe it's the MTR service but we are testing both! 

  • 0 in reply to DrewbleIT

    We confirmed that disabling the MTR service seemed to resolve the issue as well on workstations. Have not tested the encryption service yet. 

  • 0 in reply to DrewbleIT

    Hi Drew, Justin,

    I just came across this post from looking for answers!  I finally found so thanks for the post.  What is the latest with your case?  We are also MTR customer and also using the Mimecast Plugin and it started to happen around the same time for our desktops too.  I haven't looked at any of our servers for errors yet.  I have a ticket logged with Mimecast but I guess this will be for Sophos to resolve.

    Looking forward to the latest update.  Will play around with the services you mention and report back.

    Thanks and Regards (happy new years eve)

  • 0 in reply to Paul Haley

    Good day -

    Unfortunately I have not had any new information from Sophos since confirming that it's related to the MTR service. 

    Happy New years eve to you all well!

  • 0 in reply to DrewbleIT

    We are not using encryption, so that service is not present on our systems.  I can also confirm stopping the MTR service stops the msddsk.exe from repeatedly crashing.  BTW you can manually run the process to start it up but will only run for a maximum of 10-15 mins before it faults again.  My Sophos Support Case 03496588.

Unfiltered HTML