FIX: You receive an error message when you use a range rowset to iterate through rows that are returned by a Multidimensional Expressions (MDX) query in SQL Server 2005 Analysis Services

This article describes the following about this hotfix release:

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

Consider the following scenario:

• In a Microsoft SQL Server 2005 Analysis Services (SSAS) based application, you use Microsoft OLE DB for Online Analytical Processing (OLAP) to connect to an SSAS server.
• You use a range rowset in the application to iterate through rows that are returned by running a Multidimensional Expressions (MDX) query on a cube.

In this scenario, you may notice that the rows that contain a Null value return error 0x80004005(E_FAIL).

For example, when you use the OLE DB sample application Rowset Viewer (RowsetViewer.exe) to run such an MDX query, you receive an error message resembles the following: Note This problem does not occur when you query data from a cube in SQL Server 2000 Analysis Services.

Hotfix information

SQL Server 2005 Analysis Services Service Pack 1

This hotfix is based on the original release version of SQL Server 2005 Analysis Services. If you are running Microsoft SQL Server 2005 Analysis Services Service Pack 1 (SP1), you can install the SP1-based hotfix that is described in the following Microsoft Knowledge Base article:

SQL Server 2005 Analysis Services

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.

Prerequisites

To apply this hotfix, you must have SQL Server 2005 Analysis Services installed on the computer.

Restart information

After you apply this hotfix, you do not have to restart the computer if the following conditions are true:

• If SSAS is running as a named instance, you stop the SQL Server Browser service before you apply this hotfix.
• You exit all SSAS tools and all client applications before you apply this hotfix.
• You exit Microsoft Internet Information Services (IIS) before you apply this hotfix.

Registry information

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

File information

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 item in Control Panel.

SQL Server 2005 32-bit hotfix

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

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: