Network Management

Configuration Wizard Error: No valid package combination was found for current system

This article addresses the following configuration wizard error: No valid package combination was found for current system. This error typically occurs when running configuration wizard on Additional Pooling Engines or Additional Web Servers (Scalebailty engines)

First published date

10/12/2018 5:21 PM

Last published date

10/5/2023 9:55 AM

Overview


The configuration wizard fails with the following error(s) on multiple pollers. The error could be different depending on which package is failing but the common message is "Cannot find no valid combination for current system"

2017-05-25 13:50:32,331 [17] INFO PackageManager - Cannot find no valid combination for current system. 2017-05-25 13:50:32,331 [17] 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() 2017-05-25 13:50:32,331 [1] INFO OipClient - Tracking event: ConfigurationWizard - ConfigurationProgressScene - UpdateFailureText: • • No valid package combination was found for current system.

Product section

Network Performance Monitor

Resolution

  1. Check config wizard logs.
    • To identify which files/packages are missing from the server.
  2. Copy the failed packages from main poller to APE from repository directory.
    • Program Files (x86)\SolarWinds\Orion\Packaging\Repository\

 
Example of failed packages will look like this:
 

2019-06-13 06:57:05,426 [16] DEBUG DependencyAnalyzer - Orion.ESI [1.3.0.524,]

2019-06-13 06:57:05,426 [16] DEBUG DependencyAnalyzer -    1.3.0.478 [FAIL]

2019-06-13 06:57:05,426 [16] ERROR DependencyAnalyzer -    No packages are matching constraint Orion.ESI [1.3.0.524,]

2019-06-13 06:57:05,426 [16] DEBUG DependencyAnalyzer - Orion.SSH [1.0.2.360,]

2019-06-13 06:57:05,426 [16] DEBUG DependencyAnalyzer -    1.0.1.358 [FAIL]

 
Usually the errors can be found in ConfigurationWizard.log which is located 

  • (On Server) C:\programdata\solarwinds\logs\orion\ConfigurationWizard.log
  • (In Diagnostics zip) xxxx.zip\logfiles\orion\ConfigurationWizard.log


With NPM 12.3and newer you may want to simply perform a uninstall and reinstall of the Orion software as this is typically a sign of an incorrect install. Please see this article for how to reinstall your Orion software: https://support.solarwinds.com/SuccessCenter/s/article/Perform-a-fresh-Orion-installation-on-the-same-Windows-Server