FIX: A query disappears in the MDX query designer, and you cannot modify a report in Layout view when you create the report in Business Intelligence Development Studio in SQL Server 2005

This article describes the following about this hotfix release:

• The issues that are fixed by this hotfix package
• The prerequisites for installing the hotfix package
• Information about whether you must restart the computer after you install the hotfix package
• Information about whether the hotfix package is replaced by any other hotfix package
• Information about whether you must make any registry changes
• The files that are contained in the hotfix package

Consider the following scenario. In SQL Server 2005, you create a report in Business Intelligence Development Studio. When you connect to a data source of Analysis Services, Report Designer displays the Multidimensional Expressions (MDX) query designer in Data view. You build a MDX query by using Report Wizard, and then you click the Data tab to display the MDX query designer. In this scenario, you notice that the created query has disappeared, and you cannot modify the report in Layout view. However, you can still preview and deploy the report.

This problem occurs because the Report Designer cannot correctly deserialize the rd:MdxQuery element in the report that is written by the Report Wizard. Therefore, when the Report Definition Language (RDL) is loaded into the MDX query designer, the MDX metadata in the rd:MdxQuery element is lost. The MDX query designer cannot load data correctly.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry after you apply this hotfix.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

SQL Server 2005 Reporting Services 32-bit versions

SQL Server 2005 Reporting Services IA-64 version

SQL Server 2005 Reporting Services x64 version

Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

To work around this problem, carefully remove all white space and line breaks in the report between the <rd:MdxQuery> XML tag and the <QueryDefinition OtherProperties> XML tag. To do this, follow these steps:

1. On the View menu, click Code to switch to Code view.
2. Modify the RDL code in the editor to remove the white space and the line breaks.
3. Save the file, and then return to Data view.

After you remove the intervening white space and line breaks, the line of RDL code in question must appear similar to the following:

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

For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the terminology that Microsoft uses when it corrects software after the software is released, click the following article number to view the article in the Microsoft Knowledge Base:

For more information, see the following topics in SQL Server 2005 Books Online:

• Using MDX Query Designer in Design View
• Report Definition Language