EventID 26319 and error ‘An exception was thrown while processing ImportManagementPack for session id xxxx’ when trying to update a MP

Bumped into this issue when I tried to update the SQL MP to the most recent version.

No matter what I did (importing it directly from the SCOM R2 Console, downloading it as a msi-package), SCOM R2 kept on throwing this error:

So it was time for a deeper dive into the OpsMgr eventlog of the RMS, and these events were shown:

Contents of the error message:

Log Name:      Operations Manager Source:        OpsMgr SDK Service Date:          8/10/2010 8:37:47 PM Event ID:      26319 Task Category: None Level:         Error Keywords:      Classic User:          N/A Computer:      xxxxx.yyyy.zzzz Description: An exception was thrown while processing ImportManagementPack for session id uuid:ad49afad-e118-4523-a7f1-3bf3d685d74c;id=4. Exception Message: The creator of this fault did not specify a Reason. Full Exception: System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.ManagementPackException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to : Verification failed with [2] errors: ------------------------------------------------------- Error 1: : Could not load ManagementPack [ID=Microsoft.SQLServer.Library, Keytoken=31bf3856ad364e35, Version=6.1.314.36]. ManagementPack not found in the store. Version mismatch. For ManagementPack [[Microsoft.SQLServer.Library, 31bf3856ad364e35, 6.1.314.0]] requested version from the database was [6.1.314.36], and actual version available is [6.1.314.0] ------------------------------------------------------- Error 2: : Could not load ManagementPack [ID=Microsoft.SQLServer.2008.Discovery, Keytoken=31bf3856ad364e35, Version=6.1.314.36]. ManagementPack not found in the store. Version mismatch. For ManagementPack [[Microsoft.SQLServer.2008.Discovery, 31bf3856ad364e35, 6.1.314.0]] requested version from the database was [6.1.314.36], and actual version available is [6.1.314.0] -------------------------------------------------------

This is strange. I have updated the SQL MP already in a few SCOM R2 environments, and every time without any issue. So what is happening now?

Time for another approach:

1. Exported the MP containing the overrides for the SQL MP;
2. Deleted all SQL MPs which were loaded in SCOM R2;
3. Waited about ten minutes in order to avoid a race condition;
4. Imported the newest SQL MPs and now all went just fine.

Still it bothers me what caused it. However, the OpsMgr eventlog on the RMS is OK, no more errors to be found there and the SQL MP is running like clockwork.