Article ID: 932697 - Last Review: March 8, 2007 - Revision: 1.0

FIX: A calculated member that uses the DistinctCount function always returns 0 when you query a virtual cube that contains the calculated member after you install SQL Server 2000 Analysis Services Service Pack 4

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Bug #: 50000804 (SQL Hotfix)
Microsoft distributes Microsoft SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release.

On This Page

Expand all | Collapse all

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
  • 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

SYMPTOMS

When you query a virtual cube that contains a calculated member and the calculated member uses the DistinctCount function, the calculated member always returns 0 unexpectedly. For example, you query the following calculated member:
DistinctCount(Projects.Members)
This problem occurs after you install Microsoft SQL Server 2000 Analysis Services Service Pack 4 (SP4).

CAUSE

This problem occurs because of a regression in SQL Server 2000 Analysis Services SP4.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only 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 Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (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.

Prerequisites

You must have Microsoft SQL Server 2000 Service Pack 4 (SP4) installed to apply this hotfix.

For more information about how to obtain SQL Server 2000 Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:
290211  (http://support.microsoft.com/kb/290211/ ) How to obtain the latest SQL Server 2000 service pack

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.

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 item in Control Panel.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Updatelauncher.exe5.2.3790.12888,70406-Feb-200710:25x86
_sfx_manifest_Not Applicable4914-Mar-200600:21Not Applicable
Spupdsvc.exe6.2.29.025,82414-Mar-200600:22x64
Msdmbr.ocx8.0.0.2241258,12806-Feb-200710:24x86
Msmdadin.dll8.0.0.2241196,68006-Feb-200710:24x86
Msmdcb.ocx8.0.0.2241909,39406-Feb-200710:24x86
Msmdctr80.dll8.0.2241.061,44006-Feb-200710:24x86
Msmddo80.dll8.0.0.22414,093,36806-Feb-200709:19x86
Msmdsgn.dll8.0.0.22416,344,70406-Feb-200709:18x86
Msmdsgn80.dll8.0.0.22419,650,24906-Feb-200710:24x86
Msmdsrv.exe8.0.2241.01,970,17606-Feb-200710:24x86
Msmdtsm.dll8.0.0.2241446,55006-Feb-200710:24x86
Msmdtsp.dll8.0.0.2241372,82106-Feb-200710:24x86
Msolap80.dll8.0.2241.02,123,12006-Feb-200709:19x86
Osql.exe2000.80.2039.057,34406-Feb-200710:25x86
Sqlse.rll1.1.2041.045,56808-Jun-200602:07Not Applicable
Sqlstpcustomdll.dll1.1.2041.02,662,40008-Jun-200602:07x64
Sqlstpcustomdll.rll1.1.2041.012,80008-Jun-200602:07Not Applicable
Updspapi.dll6.2.29.0462,04814-Mar-200600:22x64
Spupdsvc.exe6.2.29.022,75214-Mar-200600:22x86
Msdmbr.ocx8.0.0.2241258,12806-Feb-200710:23x86
Msmdadin.dll8.0.0.2241196,68006-Feb-200710:23x86
Msmdcb.ocx8.0.0.2241909,39406-Feb-200710:23x86
Msmdctr80.dll8.0.2241.061,44006-Feb-200710:23x86
Msmddo80.dll8.0.0.22414,093,36806-Feb-200709:19x86
Msmdsgn.dll8.0.0.22416,344,70406-Feb-200709:18x86
Msmdsgn80.dll8.0.0.22419,650,24906-Feb-200710:23x86
Msmdsrv.exe8.0.2241.01,970,17606-Feb-200710:23x86
Msmdtsm.dll8.0.0.2241446,55006-Feb-200710:23x86
Msmdtsp.dll8.0.0.2241372,82106-Feb-200710:23x86
Msolap80.dll8.0.2241.02,123,12006-Feb-200709:19x86
Osql.exe2000.80.2039.057,34406-Feb-200710:25x86
Sqlse.rll1.1.2041.045,05608-Jun-200602:07Not Applicable
Sqlstpcustomdll.dll1.1.2041.01,846,78406-Feb-200710:25x86
Sqlstpcustomdll.rll1.1.2041.012,28808-Jun-200602:07Not Applicable
Updspapi.dll6.2.29.0371,42414-Mar-200600:22x86
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 "Applies to" section.

MORE INFORMATION

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:
822499  (http://support.microsoft.com/kb/822499/ ) New naming schema for Microsoft SQL Server software update packages
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:
824684  (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates

APPLIES TO
  • Microsoft SQL Server 2000 Analysis Services SP4
Keywords: 
kbbug kbfix kbhotfixserver kbqfe KB932697
Retired KB ArticleRetired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.