“Data Aggregation” field became empty in OpsMgr 2007 linked Performance Report

Today I needed to change some parameters in a linked performance report in one of the OpsMgr 2007 R2 management groups at work. When I opened the report property, the Data Aggregation field somehow became blank and greyed out:

As the result, when I tried to run the report, I get this error:

I found a blog article from Dieter Wijckmans “SCOM 2007: Scheduled reports failing”, it indicates it’s because there are duplicate management group ID specified in the report parameters. Dieter’s fix doesn’t really apply to me as the my report is not a scheduled report, however, my approach is much easier.

below is what I’ve done:

1. log on to the RMS box, and run below PowerShell script to get the management group ID:

$RMS = $env:computername
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.EnterpriseManagement.OperationsManager.Common") | Out-Null
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.EnterpriseManagement.OperationsManager") | Out-Null

$MGConnSetting = New-Object Microsoft.EnterpriseManagement.ManagementGroupConnectionSettings($RMS)
$MG = New-Object Microsoft.EnterpriseManagement.ManagementGroup($MGConnSetting)
$MG.Id

Note:

If RMS is clustered, replace “$env:computername” to the RMS cluster name in the first line.

2. export the management pack (assuming the linked report is stored in a unsealed MP), open the unsealed MP in a text editor

3. Go to

<Reporting>
  <LinkedReports>
    <LinkedReport ID= (where ID is the Id of the problematic report)>
      <Parameters>

Find the ManagementGroupId parameter and delete the incorrect value

4. Save the XML and import the unsealed MP back to the management group.

After importing the MP back, the “Data Aggregation” field is populated:

Note:

I can also change the report parameter in SSRS web site:

However, by directly modifying report in SSRS, the fix is only temporary. the original MP is not fixed and it will over write the report definition in SSRS. I’ve tried to update SSRS directly, the report got changed back shortly after.