Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

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: 1,280 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