So why blog about it again? Well I have seen situations when you upgrade to the newest version of the Exchange 2010 MP you might bump into the same EventID and situation as well. Unlike the previous posting, this time I will share the Stored Procedure required to get it all running again.
BUT… be careful AND run it only when you know what you’re doing. When in doubt, open a case with PSS. And even when you decide to run the SP, be sure to BACK UP both databases (OpsMgr & Data Warehouse) so there is a way back. Why backing up both databases when you run the SP only against the DW? When a restore is required and you only restore the DW, the OpsMgr and DW will be out of sync. So it’s always better to backup BOTH databases and restore the BOTH of them as well.
A small recap of my previous posting:
The performance Reports turn up empty or show no data from a certain date, point in time until present. And this behavior will continue, meaning that when you don’t act the performance Reports won’t show recent data at all. Reports which are affected are generally the performance reports, like the ones from the Windows Server OS Reports. Other performance Reports are affected as well.
Hmm. The message Failed to store data in the Data Warehouse tells a lot. The Instance name (Microsoft.Exchange.2010.Reports.Dataset.Availability) tells me exactly what Dataset is being problematic.
As it turns out, data aggregation for Exchange 2010 isn’t working as it should. Danielle Grandini blogged about it in detail. Because of this the performance Reports end up empty. Like stated before, data inserted into the Data Warehouse goes through a series of processes:
So the data is present but not ready for consumption by the Reports.
The Solution/Work Around
Removing any MP won’t remove any dataset from the Data Warehouse. The same goes for the Exchange 2010 Reporting MP. So removing it won’t remove the Dataset. Thus the performance Reports will still end up empty. So when the culprit has been removed a Stored Procedure must be ran against the Data Warehouse (DW) in order to get the flow of data running again in the Data Warehouse.
This is the SP you need to run against the DW:
Some explanations are at order here:
- The name after USE is the name of the Data Warehouse database, which is by default OperationsManagerDW. When your DW has another name, change it accordingly in the SP;
- The name of the dataset is in blue. When EventID 31552 shows another dataset, adjust it in the SP accordingly.
Like stated in the previous posting, after this the data came back in the Performance Reports (it took about 12 to 15 hours for the Reports to catch up). When the Reports were OK again, I imported the Exchange 2010 MP but left out the Reporting MP part of it. Until now all is well.
I hope that the latest Exchange 2010 Report MP does not have this issue. Still testing it.