New KMS MP released version 6.0.7234.0 and some things you should know

A new KMS (Key Management Services) MP is released.  I don't expect this is a widely used MP out there…. but there are some things you should know if you ever imported the previous versions.

First – the new MP is available on the catalog:


DO NOT download this MP directly via the R2 direct download mechanism.  You need to get this one from the web catalog.  As in all MP’s – you need to read the guide FIRST… because the “Before you import” section is critical.


  • The new MP is not backward compatible with the previous MP.  You MUST delete any previous version of the KMS MP you have installed.


  • If you used the previous version of the KMS MP – you might have noticed some issues.  For instance, the old KMS MP added a unique dataset type to the warehouse, with a grooming procedure just for the KMS dataset.  These didn't work.  When you download the new MP, it comes with instructions and a cleanup script to fix this.  If you ever imported the old MP – you are affected.  You will see the following events on your RMS every 10-11 minutes:

Log Name:      Operations Manager
Source:        Health Service Modules
Date:          9/23/2009 4:20:53 PM
Event ID:      31552
Task Category: Data Warehouse
Level:         Error
Keywords:      Classic
User:          N/A
Failed to store data in the Data Warehouse.
Exception 'SqlException': Sql execution failed. Error 777971002, Level 16, State 1, Procedure StandardDatasetGroom, Line 303, Message: Sql execution failed. Error 2812, Level 16, State 62, Procedure StandardDatasetGroom, Line 145, Message: Could not find stored procedure 'KMS_EventGroom'.

One or more workflows were affected by this. 

Workflow name: Microsoft.SystemCenter.DataWarehouse.StandardDataSetMaintenance
Instance name: KMS Activation Event Data Set
Instance ID: {35CE8740-3FCF-FA7F-D733-1ECD0FBE0D7F}
Management group: PROD1


So – here are the necessary steps to get this new MP working (from reading the MP guide):

  1. Delete the old MP (typically going to be version 6.0.6278.9)
  2. Run the cleanup SQL script against the OperationsManagerDW (Warehouse) database.
  3. Import the new MP.


If you had previously imported the old KMS MP – and are getting this event on your RMS, and you no longer wish to use the KMS MP anymore….. you can clean this up using the script that is included with the new MP.  So for a cleanup ONLY – where you do not wish to use the KMS MP:

  1. Make sure the old KMS MP is deleted.
  2. Run the cleanup SQL script against the OperationsManagerDW (Warehouse) database.

The script output simply displays this when complete:



A cleaned up environment will no longer have any KMS datasets, or stored procedures for grooming this dataset.  You can inspect for these with the following queries against the warehouse:

select * from standarddataset WHERE SchemaName = 'KMSEvent'

select * from sysobjects where name like ('%kms%')


Once the cleanup script has been run – these should return no results.


***Note – the new MP does not contain any reports.  The old MP had reports the leveraged the KMS Dataset, but the new MP does not.

Comments (10)

  1. Kevin Holman says:

    Weird.  On the warehouse – do you have a standarddataset table?

    What does "select * from standarddataset" return?

  2. Anonymous says:

    Thx Kevin

    It returns a table with

    DatasetID  SchemaName  DebugLevel  DefaultAggregationIntervalCount  RawInsertTableCount and several other columns

    Under the Row for SchemeName = KMSEvent I have

    DatasetId = CFE6513D-3364-4156-84CB-B897360091E4

    DeugLevel = 0

    DefaultAggregationIntervalCount = 0

    RawInsertTableCount = 1

    and so on.

    I am at if that would make it easier…


    John Bradshaw

  3. Anonymous says:

    I am getting the error regulally, and had the new MP installed.

    So I removed the new MP then ran the script….Got the following error.

    Msg 208, Level 16, State 1, Line 82

    Invalid object name ‘StandardDataSet’.

    Eek! Any ideas? thx,

    John Bradshaw

  4. Kevin Holman says:

    Did you run the script against the warehouse DB – or the OpsDB?  This should be run against the warehouse DB.

  5. Anonymous says:

    Got it now Kevin…

    Ran sp_updatestats first and then your script ran fine.

  6. Anonymous says:

    Hi Kevin,

    Yes against the WareHouseDB


    John Bradshaw

  7. Julius T. says:

    one other thing to note on this MP is that it no longer contains reports whereas the old MP did.  Not sure why they remove it but I did put in a few feelers at MS

  8. Mark says:

    Can you confirm if this MP will work withS COM 2012R2 / Windows Server 2012R2?

  9. Nick Bostwick says:

    KMS 2008 Mp "KMS Idle Time Monitor" resolution says this:
    If there has been a failure, check the following:

    Software Licensing service (slsvc) is running.

    but the health explorer item two steps up shows sppsvc. Which is it?

  10. Jon Sykes says:

    No Managment Pack guide for the newer version? Not on Microsoft downloads site? I wish there was some consistency as to how MPs were posted (through web service, MSFT downloads, pinpoint). Running this MP in a fresh environment, SCOM 2012 R2 UR2/WinServer2012R2,
    discoveries aren’t functional

Skip to main content