FIX: Execution Location and Default Isolation Mode Connection String Properties Return Results That Are Not Correct

Article translations Article translations
Article ID: 829582 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

On This Page


When you use the Execution Location connection string property and the Default Isolation Mode connection string property to force a Multidimensional Expressions (MDX) expression to run on a computer that is running Microsoft SQL Server 2000 Analysis Services 64-bit, the results of the MDX query are not correct.

Note This problem only occurs on computers that are running Analysis Services 64-bit.


Service pack information

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, 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

Hotfix information

The English version of this hotfix 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
   20-Sep-2003  01:54  8.0.861.0       5,483,008  Msmdcb80.dll     
   20-Sep-2003  01:54  8.0.861.0       5,792,768  Msmdgd80.dll     
   20-Sep-2003  01:54  8.0.861.0       5,121,536  Msmdpump.dll     
   20-Sep-2003  01:54  8.0.861.0       5,980,160  Msmdsrv.exe      
   20-Sep-2003  01:54  8.0.861.0       6,661,120  Msolap80.dll     
   20-Sep-2003  01:26  8.0.861.0         201,216  Msolap80.rll
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.


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

This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.


Article ID: 829582 - Last Review: February 27, 2014 - Revision: 2.2
  • Microsoft SQL Server 2000 Analysis Services
kbnosurvey kbarchive kbhotfixserver kbqfe kbqfe kbsqlserv2000presp4fix kbfix kbbug KB829582

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from