MOM Report Import Failures after Upgrade to SQL 2005

A post SQL 2005 upgrade issue I ran into I thought worth mentioning for anyone unaware... A few weeks ago, right after I performed the upgrade to SQL 2005 (in test) and applied the 3 post-upgrade hotfixes, I ran into an issue that may likely prevent me from repeating the operation in production for now. The problem is presumably related to more stringent XML validation in SQL 2005. Specifically, when I attempt to import MOM Reports, the import fails for several MPs with an identical error: System.Web.Services.Protocols.SoapException: The table `table1' is in the report body but the report has no data set. Data regions are not allowed in reports without datasets. Affected MPs: I started with a clean slate and started importing MPs (about 10 on the first pass). The error has appeared when importing reports for the following MPs: Exchange, VirtualServerR2, PrintServerMP, FRS, DFS (AD, , SQL and several others imported successfully). Status: I'm told this is a known issue. I exchanged posts with Clive who reported the issue is on the radar and being addressed, but could offer no timeframe for resolution at present. This issue was mentioned near the bottom of KB 917615 in the notes section as follows: Microsoft has identified issues that occur when you import reports into a MOM 2005 Reporting Server installation that is using SQL Server 2005. These issues occur because of more rigorous XML validation requirements in SQL Server 2005 Reporting Services. Microsoft is currently working on a solution for these issues.