Importing a management pack fails in Operations Manager if a dependent management pack isn't imported

This article provides a workaround to solve the issue that you can't import a management pack if a dependent management pack isn't imported in System Center Operations Manager.

Original product version:   System Center 2016 Operations Manager, System Center 2012 R2 Operations Manager, System Center 2012 Operations Manager
Original KB number:   2698846


When importing a management pack in System Center Operations Manager that has a dependency on another management pack, the import may fail with the following message:

<ManagementPackName> could not be imported.

If any management packs in the Import list are dependent on this management pack, the installation of the dependent management packs will fail.
The requested management pack was invalid. See inner exception for details.
Parameter name: managementPack


This issue occurs because a management pack that the management pack being imported depends on isn't imported in the management group. In order to work around this problem, import the dependent management packs first then import the management packs that depend on them.


If you're unsure of the dependencies for a management pack, see Management pack libraries and dependencies.