FIX: The MDX query is unsuccessful and you receive an error message if you query a ROLAP-based dimension in SQL Server 2000 Analysis Services (891575)


The information in this article applies to:

  • Microsoft SQL Server 2000 Analysis Services
Bug #: 14538 (Plato7x)Plato7x:14538

Article contents

SUMMARY

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
  • Whether you must restart your computer after you install the hotfix package
  • Whether the hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes
  • The files that are contained in the hotfix package
back to the top

SYMPTOMS

In Microsoft SQL Server 2000 Analysis Services, you run a Multidimensional Expressions (MDX) query that uses a RANGE function. If you query a ROLAP-based dimension, the MDX query is unsuccessful (fails). When you run the MDX query, you receive the following error message:
Unable to display opened cellset
Cells cannot be created for this cellset because one of the axes contains no positions
For a list of previous hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

810185 SQL Server 2000 hotfix update for SQL Server 2000 Service Pack 3 and 3a

back to the top

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft SQL Server 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.back to the top

Prerequisites

To apply this hotfix, you must have SQL Server 2000 Analysis Services Service Pack 3 (SP3) installed on your computer. For additional information about how to obtain SQL Server 2000 Analysis Services SP3, click the following article number to view the article in the Microsoft Knowledge Base:

290211 How to obtain the latest SQL Server 2000 service pack

back to the top

Restart requirement

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

back to the top

File information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain 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.
   Date         Time   Version    Size       File name
   -------------------------------------------------------
   05-Jan-2005  03:56  8.0.999.0  1,380,944  Msdmine.dll      
   31-Dec-2004  19:30                18,800  Msmd.h
   05-Jan-2005  03:56  8.0.999.0    221,760  Msmdcb80.dll     
   05-Jan-2005  03:56  8.0.0.999  4,076,104  Msmddo80.dll     
   05-Jan-2005  03:56  8.0.999.0  1,036,864  Msmdgd80.dll     
   05-Jan-2005  03:56  8.0.999.0    172,608  Msmdpump.dll     
   05-Jan-2005  03:22  8.0.999.0    446,524  Msmdsgn.rll
   05-Jan-2005  03:56  8.0.0.999  9,642,572  Msmdsgn80.dll    
   05-Jan-2005  03:56  8.0.999.0  1,847,876  Msmdsrv.exe      
   05-Jan-2005  03:56  8.0.999.0  1,397,312  Msmdvldm.exe     
   05-Jan-2005  03:56  8.0.999.0  2,089,552  Msolap80.dll     
   05-Jan-2005  01:00  8.0.999.0    213,068  Msolap80.rll
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

back to the top

WORKAROUND

To work around this problem, set the storage mode to MOLAP for the dimension.

back to the top

STATUS

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

back to the top

MORE INFORMATION

Steps to reproduce the problem

  1. Change the Customer shared dimension storage mode to ROLAP. To do this, follow these steps:
    1. Click Start, click All Programs, click Microsoft SQL Server, click Analysis Services, and then click Analysis Manager.
    2. Expand Analysis Servers, expand yourServer, expand FoodMart 2000, and then expand Shared Dimensions.
    3. Right-click Customers, and then click Edit.
    4. In the properties pane, click the Advanced tab.
    5. In the Storage Mode box, click ROLAP.
    6. On the File menu, click Save.
    7. When you are prompted to confirm that you want to save your changes, click Yes.
    8. On the File menu, click Exit.
    9. Right-click the Sales cube, click Process, and then click OK.

      Note Make sure that you select the Full Process processing method.
    10. After the process is complete, click Close in the Process dialog box.
  2. Run the sample MDX query in the MDX Sample Application. To do this, follow these steps:
    1. Click Start, click All Programs, click Microsoft SQL Server, click Analysis Services, and then click MDX Sample Application.
    2. In the Connect dialog box, enter your logon information, and then click OK.
    3. In the DB box, click FoodMart 2000.
    4. Enter the following MDX query in the query pane. 
      select
{{[Customers].[All Customers].[Canada]:[Customers].[All Customers].[USA]}} on 0
from [Sales]
    5. On the Query menu, click Run.

      Note After you click Run, you receive the error message that is mentioned in the "Symptoms" section.
For additional information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packages

For additional information about the terminology that is used when Microsoft corrects software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

back to the top
Modification Type:MinorLast Reviewed:6/2/2006
Keywords:kbSQLServ2000preSP4fix kbbug kbfix kbQFE kbHotfixServer KB891575 kbAudDeveloper kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.