Jul 11 2017 07:25 AM - edited Jul 11 2017 07:27 AM
We are getting the following errors:
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
Jul 25 2017 04:33 AM
same problem here
Aug 21 2017 11:14 AM
I'm also having the same issue. Error Appears, disappears, but keeps coming up. DPM MP's seem to be the problem, but haven't found a resolution yet. Yet DPM reports all information(Failures as I haven't changed alerts(VERY Few)), volumes, storage, systems covered, etc. Haven't been able to find any info on this issue.
Aug 21 2017 11:19 AM
yeah, exact same I think, I have to wait for it to cycle again, mine appears and then disappears from console. I'll post next time it comes up. Is your's a new installation like mine? Could this just be file build per group in DPM or something?
Aug 21 2017 11:21 AM
Mine
Data Warehouse failed to deploy database component. Failed to deploy Data Warehouse component. The operation will be retried. |
Aug 21 2017 11:33 AM
Have you looked at the table?
Aug 27 2017 08:54 AM - edited Aug 27 2017 08:55 AM
SolutionUninstalling the DPM2016 management packs, then running the SQL Script in the following article and reinstalling the MP's, fixed this problem for my system. Even though script was written for older version.
Aug 27 2017 08:54 AM - edited Aug 27 2017 08:55 AM
SolutionUninstalling the DPM2016 management packs, then running the SQL Script in the following article and reinstalling the MP's, fixed this problem for my system. Even though script was written for older version.