Microsoft KB Archive/313269

= FIX: When you run an MDX query on a write-enabled cube, the query returns #Err, or the query fails and you receive an &quot;Unable to open cellset...&quot; error message in SQL Server 2000 Analysis Services =

Article ID: 313269

Article Last Modified on 11/21/2006

-

APPLIES TO


 * Microsoft SQL Server 2000 Analysis Services

-



This article was previously published under Q313269



BUG #: 12690 (PLATO7x)



SYMPTOMS
When you run a Multidimensional Expressions (MDX) query on a write-enabled cube that has a parent-child dimension, the MDX query may fail and you may see the following behavior:  If the MDX query contains the Descendants function, all the cells in the result set may contain #Err. If the MDX query contains the Order function, you may receive the following error message:

Unable to open cellset

An error occurred during query execution - query to the source data is too long.





RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000 Analysis Services. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How to obtain the latest SQL Server 2000 service pack

The following hotfix was released before SQL Server 2000 Analysis Services Service Pack 3.

The English version of this fix has the file attributes (or later) 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.   Date         Time   Version       Size      File name --  17-Nov-2001  00:37  8.0.470.0   1,831,492   Msmdsrv.exe Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section of this article.

This problem was first corrected in Microsoft SQL Server 2000 Analysis Services Service Pack 3.

