KB919598 will shortly be released and available via http://support.microsoft.com/?id=919598

This is essentially the confirming KB article for my previous posts including http://blogs.technet.com/cliveeastwood/archive/2006/05/23/429962.aspx

If the following symptoms are experienced during an import of a MOM 2005 when using SQL Reporting Services 2005:

When you try to import a Microsoft Operations Manager (MOM) 2005 report file by using the Import/Export Management Pack option or the RptUtil.exe utility, the import process fails. Additionally, you receive an error message that resembles the following:

Operation: Import Report
Name: path and name of report.XML
Status: Failed
Description: Import failed. Report server url: http://ReportServername/ReportServer/ReportService.asmx Report import file: <path and name of report.XML>
Error message: System.Web.Services.Protocols.SoapException: The table `tabletable name' is in the report body but the report has no data set.
Data regions are not allowed in reports without datasets. ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: The table `tabletable name' is in the report body but the report has no data set. Data regions are not allowed in reports without datasets. at Microsoft.ReportingServices.ReportProcessing.ReportPublishing.CreateIntermediateFormat(CatalogItemContext reportContext, Byte[] definition, CreateReportChunk createChunkCallback, CheckSharedDataSource checkDataSourceCallback, PublishingErrorContext errorContext, AppDomain compilationTempAppDomain, Boolean generateExpressionHostWithRefusedPermissions, String& description, String& language, ParameterInfoCollection& parameters, DataSourceInfoCollection& dataSources, UserLocationFlags& userReferenceLocation, ArrayList& dataSetsName, Boolean& hasExternalImages, Boolean& hasHyperlinks) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.CompileReport(CatalogItemContext reportContext, Byte[] reportDefinition, CreateReportChunk createChunkCallback, CheckSharedDataSource checkDataSourceCallback, PublishingErrorContext errorContext, AppDomain compilationTempAppDomain, Boolean generateExpressionHostWithRefusedPermissions, String& reportDescription, String& reportLanguage, ParameterInfoCollection& parameters, DataSourceInfoCollection& dataSources, UserLocationFlags& userReferenceLocation, ArrayList& dataSetsName, Boolean& hasExternalImages, Boolean& hasHyperlinks) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.CreateIntermediateFormat(CatalogItemContext reportContext, Byte[] reportDefinition, CreateReportChunk createChunkCallback, CheckSharedDataSource checkDataSourceCallback, AppDomain compilationTempAppDomain, Boolean generateExpressionHostWithRefusedPermissions) at Microsoft.ReportingServices.Library.CreateReportAction.ConvertToIntermediate(Byte[] definition, Boolean usePermanentSnapshot, ItemProperties properties, CatalogItemContext reportContext, DateTime currentDate, Boolean checkAccessForSharedDatasources, ReportSnapshot& intermediateSnapshot, ParameterInfoCollection& parameters, Warning[]& warnings, DataSourceInfoCollection& dataSources, PageProperties& pageProperties) at Microsoft.ReportingServices.Library.SetReportDefinitionAction._SetReportDefinition(String report, Byte[] definition) at Microsoft.ReportingServices.Library.ReportCreator.UpdateExistingItem(String itemPath) at Microsoft.ReportingServices.Library.CatalogItemCreator.CreateItem() at Microsoft.ReportingServices.Library.CreateReportAction._CreateReport(String report, String parent, Boolean overwrite, Byte[] definition, Property[] properties) at Microsoft.ReportingServices.Library.CreateReportAction.CreateReport(CallParameters parameters) at Microsoft.ReportingServices.Library.RSService.ExecuteBatch(Guid batchId) at Microsoft.ReportingServices.WebServer.ReportingService.ExecuteBatch() --- End of inner exception stack trace --- at Microsoft.ReportingServices.WebServer.ReportingService.ExecuteBatch()

This problem occurs if you are using Microsoft SQL Server 2005 Reporting Services.

 

The following MP's were affected

 

  • Microsoft Application Center Management Pack for Microsoft Operations Manager 2005
  • Print Service Management Pack for Microsoft Operations Manager 2005
  • Microsoft Web Sites and Services Management Pack for Microsoft Operations Manager 2005
  • Microsoft Windows Distributed File System Service Management Pack for Microsoft Operations Manager 2005
  • Microsoft Windows DHCP Service Management Pack Management Pack
  • Microsoft Windows File Replication Service Management Pack for MOM 2005
  • Microsoft Windows Terminal Server Management Pack for Microsoft Operations Manager 2005
  • Microsoft Exchange Server 2003 Management Pack for Microsoft Operations Manager 2000 SP1
  • Microsoft Virtual Server 2005 R2 Management Pack
  • The Microsoft Exchange Server 2003 Management Pack for Microsoft Operations Manager 2000 Service Pack 1 (SP1) and the Microsoft Virtual Server 2005 R2 Management Pack are scheduled to be released in the future. If you are experiencing the symptoms that are described in this article and want a copy of these reports before the re-release of these management packs, contact Microsoft Product Support Services to obtain the files.