Submit a ticketCall us

Quickly Address Software Vulnerabilities
Patch Manager is an intuitive patch management software which extends the capabilities of WSUS and SCCM to not only patch Windows® servers and workstations, and Microsoft® applications, but also other 3rd-party applications which are commonly exploited by hackers. Learn more about our patch management solution.


Home > Success Center > Network Performance Monitor (NPM) > HA installation error: Can't receive data from SolarWinds Administration Service

HA installation error: Can't receive data from SolarWinds Administration Service

Updated April 17, 2017


The following error is displayed on the High Availability (HA) server when running the SolarWinds Orion installer for HA:

SolarWinds Orion Compatibility Check

Can't receive data from SolarWinds Administration Service


The following error is displayed in the Administration log:

ERROR SolarWinds.Administration.HAInstaller.WCF.FileTransferService - GetPackageFileStream
System.IO.FileNotFoundException: Failed to locate package file.
File name: 'C:\ProgramData\SolarWinds\Installers\CoreInstaller.msi'

The log file is located in C:\ProgramData\SolarWinds\logs\Orion\Administrationservice by default.


  • NPM 12.x
  • HA


This occurs when installers are missing from the primary server. 


  1. Check the Installers folder in the primary server to determine the missing installer. This is located in C:\ProgramData\SolarWinds\Installers by default.
  2. Download the missing installer from the SolarWinds Customer Portal.
    Note: Verify that it is the same as the version installed on the primary server.
  3. Run the installer.
  4. Go to the SolarWinds folder in %appdata%. This is where the temp installers are placed during extraction.
    Note: If %appdata% does not show the temp installers, copy the installer from an additional polling engine.
  5. Copy the missing installer to the Installers folder.  
  6. Rerun the installer on the HA server.

If the issue persists, more installers are still missing. Repeat the steps and verify that all missing installers are identified.



Last modified
18:17, 16 Apr 2017



Internal Use Only