Thursday, April 12, 2012

[OpsMgr 2007R2][OpsMgr 2012] How to keep SQL 2000 monitoring after upgrading the MP in version 6.3.173.0

As you should know, the SQL Server Management Pack has been released in version 6.3.173.0 and this new MP provides the capabilities for Operations Manager 2007 R2 and Operations Manager 2012 to discover SQL Server 2005, 2008, 2008 R2, and SQL Server 2012. It monitors SQL Server components such as database engine instances, databases, and SQL Server agents.

That means the librairy does not contain any more the classes dedicated to SQL 2000 monitoring... What a pitty when you always have SLQ 2000 instances and when the SQL team tell you they are ready for SQL 2012 installations !

Microsoft has also published in May 2011 a dedicated MP + it's library to monitor SQL 2000 instances ! See http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=15226 
BUT what a surprise to see that both Library ( in the SQL 2000 MP and in the release 6.3.173.0) have the same name : Microsoft.SQLServer.Library.mp

Impossible to import both library... and also impossible to keep SQL 2000 monitoring after an upgrade to  6.3.173.0 MP version.

I've also decided to unseal the MPs and rename the Library to be able to import SQL 2000 MP in parallele of the release 6.3.173.0 MP.

Or you can download a .ZIP file here : >>>>>> Click to Download <<<<<<


Please reseal all 3 MPs before importing in SCOM.

NOTE this will be supported by Microsoft but it's the only way I've found to be able to always monitor the SQL 2000 instances and be ready for SQL 2012 monitoring.


Here is the result after import in SCOM :


Hope this will help you ! :)

This posting is provided "AS IS" with no warranties.

4 comments:

  1. There is a problem to download the library. Can you fix it ?

    ReplyDelete
  2. Seems to work today ! I'll add a link to download a zipped package.

    ReplyDelete
  3. Can we request a resealed management pack instead? I cannot reseal the Discovery and Monitoring. I'm having some errors. Please see below.

    : Verification failed with 14 errors:
    -------------------------------------------------------
    Error 1:
    Found error in 1|Microsoft.SQLServer2000.Library|1.0.0.0|Cat.Microsoft.SQLServer2000.DBEngine.Image.
    80|| with message:
    The value specified for the Value attribute is not valid. Element Cat.Microsoft.SQLServer2000.DBEngi
    ne.Image.80 references a Value enumeration that cannot be found.
    -------------------------------------------------------
    Error 2:
    Found error in 1|Microsoft.SQLServer2000.Library|1.0.0.0|Cat.Microsoft.SQLServer2000.IntegrationServ
    ices.Image16|| with message:
    The value specified for the Value attribute is not valid. Element Cat.Microsoft.SQLServer2000.Integr
    ationServices.Image16 references a Value enumeration that cannot be found.
    -------------------------------------------------------
    Error 3:
    Found error in 1|Microsoft.SQLServer2000.Library|1.0.0.0|Cat.Microsoft.SQLServer2000.Database.Image8
    0|| with message:
    The value specified for the Value attribute is not valid. Element Cat.Microsoft.SQLServer2000.Databa
    se.Image80 references a Value enumeration that cannot be found.
    -------------------------------------------------------
    Error 4:
    Found error in 1|Microsoft.SQLServer2000.Library|1.0.0.0|Cat.Microsoft.SQLServer2000.Database.Image1
    6|| with message:
    The value specified for the Value attribute is not valid. Element Cat.Microsoft.SQLServer2000.Databa
    se.Image16 references a Value enumeration that cannot be found.
    -------------------------------------------------------
    Error 5:
    Found error in 1|Microsoft.SQLServer2000.Library|1.0.0.0|Cat.Microsoft.SQLServer2000.ReportingServic
    es.Image80|| with message:
    The value specified for the Value attribute is not valid. Element Cat.Microsoft.SQLServer2000.Report
    ingServices.Image80 references a Value enumeration that cannot be found.
    -------------------------------------------------------

    Thanks!

    Marlon

    ReplyDelete
    Replies
    1. Hi Marlon, sorry for the late answer. I cannot provide a sealed version just because the key I used to sealed is not mine but the one of my actual Customer.

      Let me try in my side to seal again the 3 .xml from the .ZIP file.
      - I've redownloaded the .zip file and extract tre 3 xml file.
      - Open the Microsoft.SQLServer2000.Library.xml in the authoring console and save as .MP with success
      - Open the Microsoft.SQLServer2000.Discovery.xml in the authoring console and save as .MP with success
      - same for the third .xml file.

      I guess your download has failed, may I suggest you to dowload again the .ZIP file from the link : https://docs.google.com/open?id=0BwNcwJETg36SOWJFX1FMWUgxMlE
      and try again to seal the 3 file by using your SCOM 2007 authoring console ?

      Best regards
      Tristan

      Delete