locked
mpseal error with centos xml files RRS feed

  • Question

  • Hello Dear SCOM Admins!

    I have the following problem:

    My aim is to seal a xml management pack from the centos library according to the guide: http://blogs.technet.com/b/jonathanalmquist/archive/2008/08/19/seal-a-management-pack.aspx

    The problem is that for importing the centos management pack there is already a error in the xml file and the workaround must be done like this:

    http://hyper-choi.blogspot.com/2011/05/how-to-import-centos-mp.html

    So far so good, but now there is one thing I dont understand:

    If I set up the command to seal:

    C:\MPS>mpseal c:\mps\input\Microsoft.Linux.CentOS.Library.xml /I "c:\mps\mp" /Keyfile
    "c:\mps\key\PairKey.snk" /Company "Company" /Outdir "c:\mps\output"

    I get just one error:

    Error 1:
    : Could not load ManagementPack [ID=Microsoft.Linux.Library, Keytoken=31bf3856ad
    364e35, Version=6.1.7000.273]. ManagementPack not found in the store.
    Cannot find MP File "Microsoft.Linux.Library.mp" in any of the search directories.

    Then I looked into the xml File and saw that the versions of several MPs doesnt even match:

    <References>
          <Reference Alias="System">
            <ID>System.Library</ID>
            <Version>6.1.7221.0</Version>
            <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
          </Reference>
          <Reference Alias="SC">
            <ID>Microsoft.SystemCenter.Library</ID>
            <Version>6.1.7221.0</Version> -> but our version is 6.1.7221.81?? checked with get-managementpack command

    <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
          </Reference>
          <Reference Alias="SCIG">
            <ID>Microsoft.SystemCenter.InstanceGroup.Library</ID>
            <Version>6.1.7221.0</Version>
            <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
          </Reference>
          <Reference Alias="Unix">
            <ID>Microsoft.Unix.Library</ID>
            <Version>6.1.7000.256</Version> but our version is 6.1.7000.277?? checked with get-managementpack command        <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
          </Reference>
          <Reference Alias="Linux">
            <ID>Microsoft.Linux.Library</ID>
            <Version>6.1.7000.273</Version>but our version is 6.1.7000.277?? checked with get-managementpack command            <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
          </Reference>

    Well, the funny thing is if I edit in the xml file and correct the versions to match the actual versions, I get even more errors, but both way at least the Microsoft.Linux.Library Error remains. Yes, I made sure that the mp-files are in the correct folder.

    Can somebody tell me what I am doing wrong??

    Thank you

    tsar1234


    • Edited by tsar1234 Friday, March 9, 2012 2:17 PM
    Friday, March 9, 2012 2:09 PM

Answers

  • I found the error....in the scom console I get the version 6.1.7000.277, in the xml file the required version is 6.1.7000.273 and the unsealed-xml from the MP is acutally 6.1.7000.256.

    So I matched the required version in the xml and now it works....

    Well the main problem is that the version of the console is mismatched with the actual version but this is another issue i will look into it, this topic can be closed:

    thx for your help
    • Edited by tsar1234 Monday, March 12, 2012 3:04 PM
    • Marked as answer by tsar1234 Monday, March 12, 2012 3:04 PM
    Monday, March 12, 2012 3:04 PM

All replies

  • Hi,

    You need to copy the appropriate versions of MP files that are referenced by the management pack that you are sealing here "c:\mps\mp".


    http://OpsMgr.ru/

    • Proposed as answer by Nicholas Li Monday, March 12, 2012 10:12 AM
    Saturday, March 10, 2012 4:13 AM
  • Hello,

    As I said before, I made sure that the mp-Files (just searched for all of them with *.mp and copied them all, and I can see the file referenced right before my eyes in the folder.

    Is there anyway to check the version of the mp files without the scom console? (because in the console i dont see the path referenced to the mp files)

    Monday, March 12, 2012 8:00 AM
  • >Is there anyway to check the version of the mp files without the scom console?

    You can open this file in Authoring Console or unseal it and check the XML directly.


    http://OpsMgr.ru/

    Monday, March 12, 2012 8:53 AM
  • >Is there anyway to check the version of the mp files without the scom console?

    You can open this file in Authoring Console or unseal it and check the XML directly.


    http://OpsMgr.ru/


    Where is exactly the version in the authoring console displayed?
    Monday, March 12, 2012 12:57 PM
  • I found the error....in the scom console I get the version 6.1.7000.277, in the xml file the required version is 6.1.7000.273 and the unsealed-xml from the MP is acutally 6.1.7000.256.

    So I matched the required version in the xml and now it works....

    Well the main problem is that the version of the console is mismatched with the actual version but this is another issue i will look into it, this topic can be closed:

    thx for your help
    • Edited by tsar1234 Monday, March 12, 2012 3:04 PM
    • Marked as answer by tsar1234 Monday, March 12, 2012 3:04 PM
    Monday, March 12, 2012 3:04 PM
  • it doesnt matter which version you are running as long as it's higher then the required version. All public classes are available in the newer mp, so they don't break any reference. Because of this principle you can upgrade referenced mp's without problem...

    e.g. any system library mp will do when the publickeytoken matches and version is higher than 6.1.7221.0.

         <Reference Alias="System">
            <ID>System.Library</ID>
            <Version>6.1.7221.0</Version>
            <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>

    But for sealing u need to have the exact version, so references can be checked before you seal it.


    Rob Korving
    http://jama00.wordpress.com/



    • Edited by rob1974 Monday, March 12, 2012 3:21 PM
    Monday, March 12, 2012 3:13 PM