none
FYI - Named Pipe Failed RRS feed

  • General discussion

  • I have an application that runs on a server that uses named pipes.  It has run for years without a problem.  This morning I came to work and was getting this error.

    Access to the path is denied.
       at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
       at System.IO.Pipes.NamedPipeServerStream.Create(String fullPipeName, PipeDirection direction, Int32 maxNumberOfServerInstances, PipeTransmissionMode transmissionMode, PipeOptions options, Int32 inBufferSize, Int32 outBufferSize, PipeAccessRights rights, SECURITY_ATTRIBUTES secAttrs)
       at System.IO.Pipes.NamedPipeServerStream..ctor(String pipeName, PipeDirection direction, Int32 maxNumberOfServerInstances, PipeTransmissionMode transmissionMode, PipeOptions options, Int32 inBufferSize, Int32 outBufferSize, PipeSecurity pipeSecurity, HandleInheritability inheritability, PipeAccessRights additionalAccessRights)
       at System.IO.Pipes.NamedPipeServerStream..ctor(String pipeName, PipeDirection direction, Int32 maxNumberOfServerInstances, PipeTransmissionMode transmissionMode, PipeOptions options, Int32 inBufferSize, Int32 outBufferSize, PipeSecurity pipeSecurity)
       at LRImpl.ProcComm.RSMoHelper.CreateServer()
       at LRImpl.ProcComm.RSMoHelper..ctor(Boolean isServer)
       at RSMoAssist.Module1.Main()

    After much hand wringing we discovered that this update, kb4489893, when removed, fixed the error.

    Not sure how to let Microsoft know about this.


    Search Documentation

    SerialPort Info

    Multics - An OS ahead of its time.

     "Those who use Application.DoEvents have no idea what it does

        and those who know what it does never use it."    former MSDN User JohnWein

    Friday, March 22, 2019 6:19 PM

All replies

  • Not sure how to let Microsoft know about this.

    It's probably let it go, be happy you found the problem and don't use the update again.

    Friday, March 22, 2019 8:16 PM