none
DPM 2016 SCOM Reports Management pack errors RRS feed

  • Question

  • Not sure if this should go in the DPM or SCOM forums, but I'm getting an error after removing the DPM 2012R2 SCOM management packs and importing the new DPM 2016 packs.  I believe it relates specifically to the report management pack, as the report is not showing up in the reporting tab.  One of the recurring SCOM errors is as follows:

    Data Warehouse failed to deploy database component. Failed to deploy Data Warehouse component. The operation will be retried.
    Exception 'DeploymentException': Failed to perform Data Warehouse component deployment operation: Install; Component: DataSet, Id: '34f57e9b-2777-8c69-a5a6-fbc8d0f1824f', Management Pack Version-dependent Id: 'e3a96ce5-bfb2-07b8-ef66-4c711a6606c7'; Target: DataSet, Id: '3f4f9eb6-e811-4b90-a117-bf5fc4809b7b'. Batch ordinal: 8; Exception: Violation of UNIQUE KEY constraint 'UN_StandardDatasetAggregationStorage_BaseTableName'. Cannot insert duplicate key in object 'dbo.StandardDatasetAggregationStorage'. The duplicate key value is (tbl_DPM_BackupEvents).
    The statement has been terminated.


    One or more workflows were affected by this.


    Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Component

    Instance name: Data Warehouse Synchronization Service

    Instance ID: {5F80CF0E-D4C5-E494-E0EB-FAF66CE1AA40}

    Has anyone else encountered this?

    • Edited by JN1226 Tuesday, December 20, 2016 10:41 PM
    Tuesday, December 20, 2016 8:31 PM

Answers

  • I was able to resolve this problem by removing the old DPM 2012 R2 datasets from the data warehouse database.

    Warning: you'll lose your DPM 2012 R2 data, and this process isn't supported by Microsoft, leaving your data warehouse database unsupported. Disclaimer: don't hold me responsible if you break anything!

    Details: https://getblogpost.pendlenet.co.uk/data-warehouse-errors-after-upgrading-dpm-2012-r2-management-packs-to-dpm-2016/


    • Edited by Gary Pendlebury Friday, July 14, 2017 9:54 AM
    • Marked as answer by JN1226 Friday, July 14, 2017 8:02 PM
    Friday, July 14, 2017 9:53 AM
  • Good spot - I hadn't tested the report. After a few days, mine now has data, but also reports the "An item with the same key has already been added" error. This occurs because MS have reused the class name of objects discovered by both the DPM 2012 R2 and 2016 management packs, so there's essentially duplicate data in the data warehouse. The fix is to either delete the redundant data, which gets a bit convoluted because of the foreign key references, or to simply rename the old objects.

    I've added a fix that worked for me to the end of my blog post.


    • Edited by Gary Pendlebury Monday, July 17, 2017 5:13 PM
    • Marked as answer by JN1226 Tuesday, August 1, 2017 7:28 PM
    Monday, July 17, 2017 5:13 PM

All replies

  • I'm experiencing the same problem, along with this error (both with ID 31565):


    Failed to deploy Data Warehouse component. The operation will be retried.
    Exception 'DeploymentException': Failed to perform Data Warehouse component deployment operation: Install; Component: DataSet, Id: 'ee26b229-74db-718a-f5b5-fe951a02ea32', Management Pack Version-dependent Id: '9e315942-a99b-8bb9-56d9-712f601901e7'; Target: DataSet, Id: '3666ddd5-255f-496c-b50c-0a6d6bebb6c3'. Batch ordinal: 8; Exception: Failed to rename staging table as part of dataset maintenance. sp_rename returned ''2627''
    Cannot grant, deny, or revoke permissions to sa, dbo, entity owner, information_schema, sys, or yourself.
    Cannot grant, deny, or revoke permissions to sa, dbo, entity owner, information_schema, sys, or yourself. 

    It looks like a bug in the DPM 2016 management pack, or an incompatibility with the DPM 2012 R2 management pack, which I used to have installed.

    Thursday, January 19, 2017 10:13 AM
  • did you ever find a solution for this? facing the same issue here
    Monday, April 3, 2017 1:30 PM
  • I have the exact same issue.
    Tuesday, April 11, 2017 12:49 PM
  • Never heard anything on this subject.  Hoping if/when a new pack is released it will just magically fix the issue, but I'm not holding my breath.
    Monday, April 24, 2017 2:27 PM
  • I was able to resolve this problem by removing the old DPM 2012 R2 datasets from the data warehouse database.

    Warning: you'll lose your DPM 2012 R2 data, and this process isn't supported by Microsoft, leaving your data warehouse database unsupported. Disclaimer: don't hold me responsible if you break anything!

    Details: https://getblogpost.pendlenet.co.uk/data-warehouse-errors-after-upgrading-dpm-2012-r2-management-packs-to-dpm-2016/


    • Edited by Gary Pendlebury Friday, July 14, 2017 9:54 AM
    • Marked as answer by JN1226 Friday, July 14, 2017 8:02 PM
    Friday, July 14, 2017 9:53 AM
  • This worked in terms of adding the management pack in correctly and getting the report into the server.  It gives an error "Cannot initialize report. An item with the same key has already been added."

    I can run the report from the reporting services server, though it comes back blank.  I'm assuming because no data has been loaded yet.

    Friday, July 14, 2017 8:02 PM
  • Good spot - I hadn't tested the report. After a few days, mine now has data, but also reports the "An item with the same key has already been added" error. This occurs because MS have reused the class name of objects discovered by both the DPM 2012 R2 and 2016 management packs, so there's essentially duplicate data in the data warehouse. The fix is to either delete the redundant data, which gets a bit convoluted because of the foreign key references, or to simply rename the old objects.

    I've added a fix that worked for me to the end of my blog post.


    • Edited by Gary Pendlebury Monday, July 17, 2017 5:13 PM
    • Marked as answer by JN1226 Tuesday, August 1, 2017 7:28 PM
    Monday, July 17, 2017 5:13 PM
  • Thank you for posting the fix, but as you stated this isn't supported by MS. How can it be marked as an answer and more specifically why doesn't someone from MS provide a proper solution.

    Sunday, August 6, 2017 9:27 AM
  • I don't know why someone from MS can't provide a solution, but it was marked as an answer because it worked and got me the reports that I needed.
    Monday, August 7, 2017 1:48 PM