Observability

Solarwinds Self-Hosted Platform Web Console returns named-pipe "Access is denied (5, 0x5)" after every reboot of the Main Poller

This article discusses an issue where the SolarWinds Platform Web Console on the Main Polling Engine becomes unavailable after every server reboot, failing with System.IO.PipeException: The pipe name could not be obtained for the pipe URI: Access is denied. (5, 0x5) when accessed over localhost. During startup, SWIS resolves the SID of the SolarWinds Orion Application Pool identity and adds it to the access control list of its local named-pipe endpoints; when that resolution does not succeed, the current implementation logs a warning and continues, so SWIS starts with an ACL that omits the website identity and the IIS worker process is denied access to the pipe.

First published date

9/16/2026 5:20 PM

Last published date

9/16/2026 5:20 PM

Overview

Whenever a server restart is performed on the Main Polling Engine, all SolarWinds services return to running state, but the SolarWinds Platform Web Console does not open and an error page is displayed instead of the login page.

From SWISv3 log:

WARN SolarWinds.Orion.Channels.Wcf.NetNamedPipeBindingAcl - The user 'SolarWinds Orion Application Pool'
could not be mapped to a SecurityIdentifier. This user will be ignored in the ACL configuration.

From OrionWeb log:

ERROR SolarWinds.InformationService.Contract2.InfoServiceProxy - (null)  An error occured opening a connection to the orion communication service.
System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.pipe://localhost/SolarWinds/InformationService/v3/Orion that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.ServiceModel.AddressAccessDeniedException: The pipe name could not be obtained for net.pipe://localhost/SolarWinds/InformationService/v3/Orion. ---> System.IO.PipeException: The pipe name could not be obtained for the pipe URI: Access is denied. (5, 0x5)

Product section

Hybrid Cloud Observability

Cause

There is a startup timing race condition between SWIS and IIS/Windows Process Activation Service (WAS). During SWIS startup, it resolves the SID for SolarWinds Orion Application Pool and adds it to the access control list for its local named-pipe endpoint. If SWIS initializes before WAS/IIS has made the application-pool virtual identity available, the SID resolution fails and the application pool account is omitted from the pipe ACL. The SolarWinds Platform Web console then cannot connect to local SWIS over the named pipe.

Resolution

Resolution:

In IIS Manager, open Application Pools → SolarWinds Orion Application Pool → Advanced Settings and verify that Start Mode is set to AlwaysRunning. If it is set to OnDemand, the application pool identity may not be initialized until first request is made and SWIS can then attempt its SID translation too early.

 

  • In services.msc, set Windows Process Activation Service (WAS) to Automatic startup.

  • Configure SolarWinds Information Service V3 to depend on the WAS service. Run the following command from an elevated Command Prompt or PowerShell:

sc.exe config "SWInfoServiceSvcV3" depend= "NetTcpPortSharing/WAS"

You can then verify that the configuration correctly applied with:

sc.exe qc "SWInfoServiceSvcV3"

Both NetTcpPortSharing and WAS should be listed under Dependencies.

Reboot the server.