AKM Import Error ProcessRuleBulkInsertCompound Failed.
HRESULT=0X40ED2

Failed to import processing rules and saved views from the provided Management Pack file into database.

Unspecified error
Result code: 80004005

I am aware that when the Auditing feature is on, as stated in article 828783, will cause this problem. However, the Auditing feature is NOT turned on on my MOM server.

Contributed By: Bill Hodghead [MSFT]
If the Full Management Pack (MP) is failing to import:
Besides the auditing or DB full reasons, this error most likely indicates a conflict between an object in the MP and one in the DB.

If you have computer group in the MP with the same name, but different GUID from a computer group in the DB then the import may fail.

This occurs if you try to import an MP that uses the same name for a computer group that you already have in the DB. Example: you have a group called "Computers" and you try to import a different group called "Computers" (different GUID).

The main workaround is to try to figure out which group it's failing on and delete that one in the UI. You can try to get more info by looking at the log files in the %Temp%\Microsoft Operations Manager folder.

If PART of the MP is failing to import:
That means the rule group you're importing is conflicting with a rule group you already have. Likely what has happened is that at some time you deleted a rule group but it's child still exists. This child rule group may now appear at the root level of the processing rule groups or it may still be associated with another rule group (like the NT4 Windows NT System Misc Dll's).

There are a couple of possible fixes but the easiest may be to delete the rule group and then import the retail MP.