It is the last day of the year but it is not too late for a new blog post. When applying Update Rollup for System Center 2012 R2 I’ve encountered an issue when updating the VMM Management Pack and I’ve blogged about it in my tips.
Update Rollup 3 for System Center 2012 R2 contains updated VMM Management Pack and when I’ve updated them I’ve started to receive the following error on my SCOM Management Servers:
Data Warehouse failed to deploy reports for a management pack to SQL Reporting Services Server. 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 ‘bc01c069-4ea6-f477-75d8-2c456773e63d’. Failed to deploy report ‘Microsoft.Virtualization.Reports.ForecastMachineGroupNetworkIO’. AdjustDataSources: Exception <ErrorCode xmlns=”http://www.microsoft.com/sql/reportingservices“>rsInvalidElementCombination</ErrorCode><HttpStatus xmlns=”http://www.microsoft.com/sql/reportingservices“>400</HttpStatus><Message xmlns=”http://www.microsoft.com/sql/reportingservices“>The combination of values for the fields UserName and CredentialRetrieval are not valid.</Message><HelpLink xmlns=”http://www.microsoft.com/sql/reportingservices“>http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&EvtID=rsInvalidElementCombination&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=11.0.3153.0</HelpLink><ProductName xmlns=”http://www.microsoft.com/sql/reportingservices“>Microsoft SQL Server Reporting Services</ProductName><ProductVersion xmlns=”http://www.microsoft.com/sql/reportingservices“>11.0.3153.0</ProductVersion><ProductLocaleId xmlns=”http://www.microsoft.com/sql/reportingservices“>127</ProductLocaleId><OperatingSystem xmlns=”http://www.microsoft.com/sql/reportingservices“>OsIndependent</OperatingSystem><CountryLocaleId xmlns=”http://www.microsoft.com/sql/reportingservices“>1033</CountryLocaleId><MoreInformation xmlns=”http://www.microsoft.com/sql/reportingservices“><Source>Microsoft.ReportingServices.ProcessingCore</Source><Message msrs:ErrorCode=”rsInvalidElementCombination” msrs:HelpLink=”http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&EvtID=rsInvalidElementCombination&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=11.0.3153.0” xmlns:msrs=”http://www.microsoft.com/sql/reportingservices“>The combination of values for the fields UserName and CredentialRetrieval are not valid.</Message></MoreInformation><Warnings xmlns=”http://www.microsoft.com/sql/reportingservices” />
One or more workflows were affected by this.
Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Report
Instance name: Data Warehouse Synchronization Service
Instance ID: {71E6A404-7C83-F5A6-2514-FF4F5D85F46B}
Management group: SCOM_MG
Basically this error was logged every 10 minutes in the OpsMgr log and of course appeared as critical alert in SCOM console. If you try to search for it you will find some common proposal how to fix it but in this particular case those proposals will not work. As I’ve encountered this issue in 3 environments this definitely looks like a bug to me so I’ve contacted Microsoft support in helping me resolve it. There are two resolutions for this issue: one proposed by me and one proposed by Microsoft.
1st Solution (the one I’ve discovered):
You will need to reinstall your SCOM Reporting Server. The steps are described here: http://technet.microsoft.com/en-us/library/hh457588.aspx
In this solution you will also need first to check if your VMM Connection Profile in SCOM is associated with your VMM Connection account in SCOM. Here are the steps provided by Microsoft:
If the VMM Connection RunAsProfile in SCOM is not associated with the corresponding RunAsAccount, here are the instructions to fix it:
Re-enable Operations Manager/VMM integration
After you import the VMM UR3 MP into Operations Manager, you must re-enable integration.
Re-associate the Virtual Machine Manager Connection Account Run As account with the Virtual Machine Manager Connection Account Run As profile.
- Open the Operations console.
-
Open the Administration workspace.
-
Expand Run As Configuration -> Profiles.
-
In the Profiles pane, double-click Virtual Machine Manager Connection Account.
-
On the Run As Accounts page, add the Virtual Machine Manager Connection Account, and then click OK.
-
Click Save.
Then, refresh Operations Manager/VMM integration in VMM. To do this:
- In the VMM console, open the Settings workspace.
Click System Center Settings.
Right-click Operations Manager Server, and then click Properties.
On the Details page, under Diagnostics, click Refresh.
Be aware that this refresh operation can take a long time (can take more than 20 minutes).
2nd Solution (proposed by Microsoft):
Allow 5 minutes between each step to ensure changes have been applied through the system:
1- Remove Reports MP.
2- Update VMM Connection RunAsProfile in SCOM, as described below.
If the VMM Connection RunAsProfile in SCOM is not associated with the corresponding RunAsAccount, here are the instructions to fix it:
Re-enable Operations Manager/VMM integration
After you import the VMM UR3 MP into Operations Manager, you must re-enable integration.
Re-associate the Virtual Machine Manager Connection Account Run As account with the Virtual Machine Manager Connection Account Run As profile.
- Open the Operations console.
Open the Administration workspace.
Expand Run As Configuration -> Profiles.
In the Profiles pane, double-click Virtual Machine Manager Connection Account.
On the Run As Accounts page, add the Virtual Machine Manager Connection Account, and then click OK.
Click Save.
Then, refresh Operations Manager/VMM integration in VMM. To do this:
- In the VMM console, open the Settings workspace.
Click System Center Settings.
Right-click Operations Manager Server, and then click Properties.
On the Details page, under Diagnostics, click Refresh.
Be aware that this refresh operation can take a long time (can take more than 20 minutes).
3- Add Reports MP
4- Remove and Add SSASConnection.
I would recommend to use the solution proposed by Microsoft as mine is more like shooting rabbits with riffle for bears. I hope this will be helpful in resolving this issue. In my case it helped.
No rabbits were harmed during the resolution of this case 
Cloud Administrator in Azure World 
One thought on “Report Deployment Error After Updating VMM Management Packs with 2012 R2 Update Rollup 3”