Submit a ticketCall us

AnnouncementsSystem Monitoring for Dummies

Tired of monitoring failures disrupting the system, application, and service? Learn the key monitoring concepts needed to help you create sophisticated monitoring and alerting strategies that can help you save time and money. Read the eBook.

Get your free eBook.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Configuration wizard error: No valid package combination was found for current system

Configuration wizard error: No valid package combination was found for current system

Updated April 12, 2017


The following error occurs in the Configuration wizard after upgrading to SAM version 6.4:

No valid package combination was found for current system

The ConfigurationWizard.log displays the following error:

ERROR ConfigurationProgressScene - Exception while configuring plugins.
          System.Exception: No valid package combination was found for current system.
             at SolarWinds.Packaging.Core.PackageManager.UpdateSystemInternal(UpdateSystemContext updateSystemContext, Boolean checkChangesOnly)
             at SolarWinds.ConfigurationWizard.Common.Packaging.PackagingExecutor.UpdateSystem(IHostInfo hostInfo)
             at SolarWinds.ConfigurationWizard.Host.Presentation.CommonConfiguration.ConfigurationProgressScene.DoConfigInThreadUnsafe_DeployPackages(IOrionConfigHost host, PackagingExecutor packaging)
             at SolarWinds.ConfigurationWizard.Host.Presentation.CommonConfiguration.ConfigurationProgressScene.DoConfigInThreadUnsafe(IOrionConfigHost host)
             at SolarWinds.ConfigurationWizard.Host.Presentation.CommonConfiguration.ConfigurationProgressScene.DoConfigInThread()
          2027-03-13 11:45:10,913 [1] INFO  OipClient - Tracking event: ConfigurationWizard - ConfigurationProgressScene - UpdateFailureText:             
          No valid package combination was found for current system.


  • SAM version 6.4 or later
  • All NTA versions



The error is caused by a failed upgrade of NTA 4.2.1 to 4.2.2.  As a result, the MSI file in


was 4.2.2.

However, the following installed packages were from 4.2.1:




***NTA 4.2.2 msi file requires these two opkg files:




  1. Ensure Orion Platform 2017.1 HotFix 1 has been installed. To find out:
    1. Go to start > run > appwiz.cpl and press enter. Programs and Features open.
    2. Click View installed updates.
    3. Scroll down to the bottom and look under SolarWinds section.
  2. If you still have the issue, re-run the NTA 4.2.2 installation program to complete the upgrade. The Configuration wizard should not return any errors because the NTA packages were upgraded.
  3. You may need to follow the resolution instructions in the following article as well for the NTA 4.2.2 installation to complete:
  4. You may also need to apply the steps in the article below as well:


Orion Platform 2017.1 Hotfix 1 includes a new version of the packageCleaner tool, which moves unnecessary packages into the Repository.Backup folder, but it saves the two latest versions of every package.

If there is an issue with "No valid package combination" before the hotfix is applied, move the missing packages from the Repository.Backup into the Repository. Move only the packages that are missing. These are usually NTA packages, hotfixes, or patches.




Last modified