Tuesday, September 7, 2010

EventID 31567: Failed to deploy reporting component to the SQL Server Reporting Services server.

Bumped into this issue at a customers site. All was well, almost all MPs uploaded their reports as designed. One MP however suffered some issues. This caused a partial Report deployment. Not all Reports were uploaded to the SSRS instance.

So I removed the MP but the partial uploaded Reports didn’t want to go away anymore. And after having waited some time (about 30 minutes or so) I imported the MP again. Same error!

But now the issue which caused the first error, had been fixed. So apparently the ‘left over's’ of the first attempt when importing that MP were blocking the whole thing now. And again, the OpsMgr event log of the RMS showed EventID 31567, Failed to deploy reporting component to the SQL Server Reporting Services server.

Time for another approach:

  1. Removed the MP (again);
  2. Opened the web interface of the SSRS instance (http://localhost/Reports) on the SQL Server which was used by SCOM R2;
  3. Set it to the Detailed View;
  4. Selected the folder containing the partially uploaded Reports and removed it;
  5. Imported the MP again.

Within ten minutes ALL Reports were uploaded to SSRS and the OpsMgr event log on the RMS showed no errors anymore!

7 comments:

John Bradshaw said...

Just noticed this error popping up.
How does one determine which MP to delete from the following?
Failed to deploy reporting component to the SQL Server Reporting Services server. The operation will be retried.
Exception 'DeploymentException': Failed to deploy reports for management pack with version dependent id '3865f46b-54a4-464e-aa7c-2762b5b42856'. Failed to deploy report 'SCC.HealthCheck.Reports.V2.OM.Misc.ManagementPacks'. AdjustDataSources: Exception rsInvalidParameter400The value of parameter 'DataSources' is not valid.http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&EvtID=rsInvalidParameter&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=10.50.1617.0Microsoft SQL Server Reporting Services10.50.1617.0127OsIndependent1033ReportingServicesLibrary<Message msrs

Thx,
John Bradshaw

Marnix Wolf said...

Hi John.

Seems like you have imported the SCC MP containing all SCOM Health Reports and forgot to create the additional data source which allows some Reports to tap into the Operational Database.

Cherrs,
Marnix

Natalya said...

Worked perfect in SCOM2012\SQL2012 infrastructure. Thanks Marnix!
Natalya

Sundar Kannan said...

In my case I'm getting the below error, Kindly suggest which one to delete please,
"Failed to deploy reporting component to the SQL Server Reporting Services server. The operation will be retried.
Exception 'DeploymentException': Failed to deploy reports for management pack with version dependent id '8178375c-1e4e-9d9a-6232-bed7a26d555d'. Failed to deploy linked report 'Microsoft.SystemCenter.WebApplicationSolutions.Reporting.WebTestPerformanceReport'. The item '/Microsoft.SystemCenter.DataWarehouse.Report.Library/Microsoft.SystemCenter.DataWarehouse.Report.Performance' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/Microsoft.SystemCenter.DataWarehouse.Report.Library/Microsoft.SystemCenter.DataWarehouse.Report.Performance' cannot be found.

One or more workflows were affected by this.

Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Report
Instance name: Data Warehouse Synchronization Service
Instance ID: {A5124DA3-7C78-98E4-9B47-E08899550006}"

Regards,
Sundar

Brian W said...

This is fine and dandy if you can deleted the MP in question, but in my case this is happening to me after applying UR9 for SCOM 2012 R2, and the MP "Microsoft.SystemCenter.DataWarehouse.Report.Library" is one on which all my other imported MPs depend, and I can't remove it without deleting all the other ones. Not practical... I have over 200 MPs imported and/orcreated for custom overrides, monitors, and rules.

Marnix Wolf said...

HI Rian. Yes you are right. With so many MPs this approach isn't viable. Are there any other errors you get? What version of SCOM are you on? And what Cumulative Update level? Are those MPs updated as well?

Marnix Wolf said...

HI Rian. Yes you are right. With so many MPs this approach isn't viable. Are there any other errors you get? What version of SCOM are you on? And what Cumulative Update level? Are those MPs updated as well?