When you try to import a Microsoft Operations Manager 2005 report file, the import process fails (919598)


The information in this article applies to:

  • Microsoft Operations Manager 2005, when used with:
    • Microsoft SQL Server 2005 Reporting Services

SYMPTOMS

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.

CAUSE

This problem occurs because SQL Server 2005 Reporting Services imposes a more rigorous XML validation on the report schema. This behavior prevents some reports that were created by using an older schema convention from being imported.

The following Microsoft management pack reports are known to be 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

RESOLUTION

Updated reports that correct the problem are available for the first seven reports that are listed in the "Cause" section. To obtain these corrected reports, visit the following Microsoft Web site, and then search for the report:

http://www.microsoft.com/management/mma/catalog.aspx

The Microsoft Exchange Server 2003 Management Pack for Microsoft Operations Manager 2005 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.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

The Microsoft management packs that have been updated to correct this problem only contain changes to the report XML schemas. If the management pack and the reports are already installed and an upgrade to SQL Server 2005 is performed, you do not have to reimport the management pack or the reports.

Note Reports that are supplied in management packs from third-party vendors may be affected. If you experience this problem when you try to import reports that are supplied in a management pack from a third-party vendor, contact that vendor for an updated report file.
Modification Type:MinorLast Reviewed:10/4/2006
Keywords:kbtshoot kbprb KB919598 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.