This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Configuration Wizard error "No valid package combination was found for current system"

tfbissett over 6 years ago

Running Versions:

Orion Platform 2016.2.100

NPM 12.0.1

SAM 6.3.0

NCM 7.5

NTA 4.2.0

IPAM 4.3.2

Configuration wizard will not complete due to the error "no valid package combination was found for current system" on 1 of 7 APE's.

The only info on resolving the issue points to PackageCleaner.exe which is contained in Orion Platform 2017, I'm not prepared to upgrade the total infrastructure at this time.

I have uninstalled all software from the APE and reinstalled and the error continues what am I missing has anybody run into this and have a resolution? I do have a support case started 1181939 the initial response was use the PackageCleaner.

Any thoughts or idea's would be greatly appreciated.

Thanks Tom

Top Replies

0 neomatrix1217 over 6 years ago
Are you on NPM 12.1 as the hot fix addresses that issue.
Upgrade to NPM 12.1 with NTA 4.2.1 fails with the following error: No valid package combination was found for current system.
NPM 12.1 Hotfix 1 - SolarWinds Worldwide, LLC. Help and Support
Cancel
Vote Up 0 Vote Down

Cancel
0 tfbissett over 6 years ago in reply to neomatrix1217

I'm on NPM 12.0.1........
Cancel
Vote Up 0 Vote Down

Cancel
0 patriot over 6 years ago

I just installed 12.1 with HF3, which is supposed to include HF 2 and 3, but I still get the error trying to install an APE and an AWS.
Cancel
Vote Up 0 Vote Down

Cancel
0 tfbissett over 6 years ago in reply to patriot
On 12.1 the recommended fix is as follows........
Please try the following to resolve.

Locate the PackagesCleaner.exe.config file. By default, this is located in c:\Program Files (x86)\SolarWinds\Orion.
Edit the file and change <add key="RunCleaner" value="true"/> to
<add key="RunCleaner" value="false"/>.
Copy all opkg files from c:\Program Files (x86)\SolarWinds\Orion\Packaging\Repository.Backup
to c:\Program Files (x86)\SolarWinds\Orion\Packaging\Repository.
Run the configuration wizard.
Cancel
Vote Up +5 Vote Down

Cancel
0 neomatrix1217 over 6 years ago in reply to tfbissett

My feeling is that the issue is with NTA but without seeing the logs it's tough.
Installer does not launch during an upgrade to NTA 4.2.2 - SolarWinds Worldwide, LLC. Help and Support
Cancel
Vote Up 0 Vote Down

Cancel
0 patriot over 6 years ago in reply to patriot

I just finished installing Platform 2017 HF3 on the PPE and then attempting to install the APE using the "Download" option from the Polling Engines page. Still get the error.
The goofy thing is, the ReadMe for HF3 says that it should be installed on the APE as well, but you can't do that since SolarWinds has not yet been installed there!!
What the.....?
Cancel
Vote Up 0 Vote Down

Cancel
0 tfbissett over 6 years ago

I was able to resolve my issue by comparing the c:\Program Files (x86)\SolarWinds\Orion\Packaging\Repository
with one of my other APE files there was one opkg file different copied to the APE having the issue and the configuration wizard completes and all services are working again on the APE.......
Thanks for the suggestions and help!
Cancel
Vote Up +3 Vote Down

Cancel
0 sh27 over 6 years ago in reply to tfbissett

Disabling the packages cleaner and copying packages from the main polling engine worked for me. Thanks for the clue. I'm on 12.1 HF1.
Cancel
Vote Up 0 Vote Down

Cancel
0 lynchnigel over 6 years ago in reply to tfbissett

Had the same issue as you, the guys from support was looking at it and thats what they was looking at, one package being a different version. I've been told to use the installer on the additional pollers because it basically sucks the same config from the primary poller. So well done
Cancel
Vote Up 0 Vote Down

Cancel
0 marcrobinson over 6 years ago in reply to tfbissett

I am on 12.1 HF1, Orion 2017 HF3, and this suggestion worked on a poller also. Disabled the cleaner, copied the files (from the backup repo in my case), and ran config wizard. I was using the scalability installer to actually install everything on a new poller. Thanks for posting this solution!
Cancel
Vote Up 0 Vote Down

Cancel