Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Server & Application Monitor (SAM) > Info service v3 logs: The HTTP request is unauthorized with client authentication scheme Basic

Info service v3 logs: The HTTP request is unauthorized with client authentication scheme Basic

Created by William Muhle, last modified by MindTouch on Jun 23, 2016

Views: 58 Votes: 0 Revisions: 4


This article describes the issue when the information service v3 fails to start and you receive the following error in the logs:

[14] 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.tcp://eusta0272123:17777/SolarWinds/InformationService/v3/Orion/certificate that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.


[14] ERROR SolarWinds.Data.Providers.Orion.DynamicServicesHost - (null)     Failed to start dynamic subscriber services. Will try again in one minute.


If you scroll up, the very first error that you see in the logs is this:

[6] ERROR SolarWinds.InformationService.Core.InformationServiceService - (null)     Information Service failed to open a channel.
System.ServiceModel.Security.MessageSecurityException: The HTTP request is unauthorized with client authentication scheme 'Basic'. The authentication header received from the server was 'Basic realm="Spring Security Application"'. ---> System.Net.WebException: The remote server returned an error: (401) Unauthorized.


  • SAM version 6.2.1
  • SAM version 6.2.2
  • SAM version 6.2.3


This is an issue caused by DPA integration.  


  1. Stop all Orion services.
  2. Run the following query against the database:

DELETE FROM [WebSettings] WHERE SettingName IN ('DPA.DpaServiceUserAccountId', 'DPA.ServerUrl', 'DPA.OrionHostname')
DELETE FROM FED_Subscription WHERE ServerId IN (SELECT ServerId FROM FED_RemoteInformationServices WHERE Tag = 'DPAO')
DELETE FROM FED_RemoteInformationServices WHERE Tag = 'DPAO'

    3. Start the Orion Services.


Last modified
02:55, 23 Jun 2016