Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Unable to access Web Console with error: No process is on the other end of the pipe

Unable to access Web Console with error: No process is on the other end of the pipe

Updated June 14, 2017


The Orion Web Console cannot be accessed and the following error is shown in the SWIS logs:


2017-06-12 15:03:44,617 [7] WARN  SolarWinds.Orion.Swis.PubSub.MessageBus.MessageBusTopologyProvider - (null) (null)     Could not load updated message bus host list from database.
System.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) ---> System.ComponentModel.Win32Exception (0x80004005): No process is on the other end of the pipe
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)


NPM 11.5 and later


This issue occurs when SolarWinds services attempts to connect using named pipes and the server is not configured to allow remote connections using named pipes, or when the services attempt to connect with the named pipes protocol before trying the TCP protocol and named pipes are not enabled on the server.



  1. Select Start, and in your list of programs, select SQL Server Configuration Manager.
  2. Navigate to SQL Server Configuration Manager > SQL Server Network Configuration > Protocols for <machine instance>.
  3. Double-click Named Pipes. The Named Pipes Properties screen appears.
  4. From Enabled, select Yes. Then click OK.
  5. Double-click TCP/IP. The TCP/IP Properties screen appears.
  6. On the Protocol tab, ensure Yes is selected for Enabled. On the IP Addresses tab, ensure that Yes is selected for the appropriate IP Address. Also, ensure that the appropriate TCP Port is indicated.
  7. Click OK.
  8. From SQL Server Management Studio, restart the server instance.


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.


Last modified