none
SQL 2016 SP1 Enterprise edition Server local connection provider has stopped listening on [ \\.\pipe\SQLLocal\MSSQLSERVER ] due to a failure. Error: 0xe8, state: 4. RRS feed

  • Question

  • DATE/TIME:        7/5/2017 12:00:02 PM

    DESCRIPTION:   Server local connection provider has stopped listening on [ Server local connection provider has stopped listening on [ \\.\pipe\SQLLocal\MSSQLSERVER ] due to a failure. Error: 0xe8, state: 4.  ] due to a failure. Error: 0xe8, state: 4. The server will automatically attempt to re-establish listening.

    COMMENT:        (None)

    JOB RUN:             (None)

    Wednesday, July 5, 2017 6:03 PM

Answers

All replies

  • Hi,

    This is the forum to discuss questions and feedback for Microsoft Word features, I'll move your question to SQL forum:

    https://social.msdn.microsoft.com/Forums/en-US/home?forum=exceldev

    The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.


    Regards,
    Emi Zhang
    TechNet Community Support

    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, July 6, 2017 8:38 AM
  • Hi khal naser,

     

    Please check if you have enabled Named Pipes in SQL Server, you can open SQL Server Configuration Manager -> Protocols for MSSQLSERVER, right-click on the Named Pipes, click enable.

     

    If you have enabled Named Pipes, this problem can be caused by that it's not ready to accept connection for Named Pipes when client make a connection. Please refer to this article: https://blogs.msdn.microsoft.com/sql_protocols/2005/12/21/troubleshoot-connectivity-issue-in-sql-server-2005-part-iii/

     

    Best Regards,

    Teige

     

     


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, July 6, 2017 8:42 AM
    Moderator