Network Management

We are unable to download the file [FILENAME.msi] from the main server. Please check the connection to the main server.

This article explains the workaround if the Additional Polling Engine(s) and Additional Web Server(s) failed to upgrade Individually or through Centralized Upgrade. "Message": "Can't download file because of the invalid checksum.

First published date

10/9/2019 7:31 PM

Last published date

2/26/2025 4:09 AM

Overview

While performing the Centralized Upgrade from the Main Poller, an error message is seen such as

"Server {ServerName} cannot be upgraded. Unable to calculate the upgrade path for server {ServerName} due to product inconsistencies between the main polling engine and {ServerName}"

If upgrading via Individual Upgrade so after downloading the installer for Scalability Engine Upgrade, you may see an error such as 
"We are unable to download the file {FileName}.msi from the main server. Please check the connection to the main server."


In this case, you will observe an error message in the installer log file such as  
ERROR (null) SolarWinds.Administration.InstallExecutor.Executors.DownloadExecutor - Download of file https://downloads.solarwinds.com/solarwinds/CatalogResources/Core/2020.2/2020.2.5320.27438/CoreInstaller.msi in version 2020.2.5320.27438 failed

SolarWinds.Administration.Downloader.Exceptions.InvalidChecksumException: the invalid checksum: C20FD967D64E9722D840EC4292645B65896D0EE3EBE31090E15C5312D889C89E for file C:\ProgramData\SolarWinds\Downloads\CORE-2020.2.5320.27438-CoreInstaller.msi

Note: The installer name and version may vary.

Product section

Orion Platform

Cause

The files are not present on Main Poller, Aditional Polling Engine, or Additional Web Server. If present, a checksum was not calculated that equaled the expected checksum.

Resolution

Before proceeding on the steps listed below, verify if Firewall rules allow connection to the product catalog where installers should be downloaded, as it  can prevent the outbound connection to the catalog site where we get the installers from

Resolution 1

  1. In C:\ProgramData\Solarwinds\Logs\Installer\[Date] , locate AdministrationService.client.log
  2. Scroll through the file and look for the error message
  3. Copy the URL and use the browser to download the file
  4. Move the downloaded file to both Main Polling Engine, Additional Polling Engine, and Additional Web Server folders in C:\ProgramData\SolarWinds\Installers 
  5.  Run the installer again
    1. If the installer is still open, click retry
    2. If the installer was closed, run with Local Administration rights

You may choose to copy installers from the Main Polling Engine to the Additional Polling Engine to prevent a possible timeout due to slow file transfers.

  • Copy from Main Server: C:\ProgramData\SolarWinds\Installers

  • To Additional Poller: C:\ProgramData\SolarWinds\Installers

 

Then run the APE or AWS installer again.

 

Resolution 2

If resolution 1 does not work, it means the main poller does not have the files needed by the APE, and the APE is unable to access the URL. 
This method is more time and labor intense, but it works when you are left with no other options.

  1. Copy the URL from the AdministrationService.log (C:\ProgramData\SolarWinds\Logs\Administration) that is failing to download C:\ProgramData\SolarWinds\Installers on APE

  2. Rerun the Orion installer

  3. The installer should come back with another "Unable to download" file error

  4. Repeat steps 1-6 as needed until the installer has all the files it needs to download. you may need to do this several times.

Resolution 3

This article describes how to address issues without working through Diagnostics or a support case when your Orion Environment system is down and needs to be restored quickly because of a strict downtime window. As a result, you need to uninstall Orion Products from the affected server and perform a fresh installation on the same server.

Perform a fresh Orion installation (uninstall and reinstall) on the same Windows server
  1. Paste in browser to download
  2. Move the downloaded file to 

  3. Orion 2020.2 and Later or High Availability Installs

  4. If the installer on a new High Availability engine fails with this error, you may attempt to copy the installer from the primary engine. If the installer exists with a failure to transfer the MIBs.msi, you should attempt to update the MIB database on the primary poller and try the installation again on the HA server.
  5. Update the SolarWinds MIB Database in NPM