FIX: A drillthrough operation fails, and you may receive an "Unable to drill through" error message after you configure drillthrough permissions on a virtual cube in SQL Server 2000 Analysis Services (892517)



The information in this article applies to:

  • Microsoft SQL Server 2000 Analysis Services
  • Microsoft SQL Server 2000 Analysis Services 64 bit

Bug #: 14512 (Plato7x)
Bug #: 14583 (Plato7x)
Bug #: 14458 (Plato7x)
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.

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

After you configure drillthrough permissions on a virtual cube in Microsoft SQL Server 2000 Analysis Services, the drillthrough operation fails. Additionally, you may receive an error message that is similar to the following:
Unable to drill through.
Access denied to the cube BaseCube.
Note BaseCube is the name of a base cube for the virtual cube.

CAUSE

This problem occurs because drillthrough security permissions are not set on the base cube. When you set security permissions on the virtual cube, the security permissions are not propagated to the base cube. When the server on which SQL Server 2000 Analysis Services is installed receives a drillthrough request, the server evaluates drillthrough security permissions on the virtual cube and on the base cubes. The most restrictive set of drillthrough permissions is applied.

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 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: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 SQL Server 2000 Analysis Services Service Pack or SQL Server 2000 Analysis Services Service Pack 4 installed to apply this hotfix.

Restart information

You do not have to restart the computer after you apply this hotfix. However, the Analysis Services service will be stopped and then restarted when 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 tool in Control Panel.SQL Server 2000 Analysis Services Service Pack 3, x86
   Date         Time   Version     Size       File name
   --------------------------------------------------------
   19-Jan-2005  01:48  8.0.1002.0  1,380,944  Msdmine.dll      
   19-Jan-2005  01:48  8.0.1002.0    221,760  Msmdcb80.dll     
   19-Jan-2005  01:48  8.0.0.1002  4,076,104  Msmddo80.dll     
   19-Jan-2005  01:48  8.0.1002.0  1,036,864  Msmdgd80.dll     
   19-Jan-2005  01:48  8.0.1002.0    172,608  Msmdpump.dll     
   19-Jan-2005  01:19  8.0.1002.0    446,524  Msmdsgn.rll
   19-Jan-2005  01:48  8.0.0.1002  9,642,572  Msmdsgn80.dll    
   19-Jan-2005  01:48  8.0.1002.0  1,851,972  Msmdsrv.exe      
   19-Jan-2005  01:48  8.0.1002.0  1,401,408  Msmdvldm.exe     
   19-Jan-2005  01:48  8.0.1002.0  2,089,552  Msolap80.dll     
   19-Jan-2005  00:06  8.0.1002.0    213,068  Msolap80.rll   
SQL Server 2000 Analysis Services Service Pack 3, Itanium Architecture
   Date         Time   Version     Size       File name
   -------------------------------------------------------
   19-Jan-2005  17:34  8.0.1002.0  5,150,720  Msdmine.dll
   19-Jan-2005  17:34  8.0.1002.0  5,534,720  Msmdcb80.dll
   19-Jan-2005  17:34  8.0.1002.0  5,843,968  Msmdgd80.dll
   19-Jan-2005  17:34  8.0.1002.0  5,173,760  Msmdpump.dll
   19-Jan-2005  17:34  8.0.1002.0  6,062,592  Msmdsrv.exe
   19-Jan-2005  17:34  8.0.1002.0  6,714,368  Msolap80.dll
   19-Jan-2005  17:34  8.0.1002.0    201,728  Msolap80.rll 
SQL Server Analysis Services Service Pack 4, x86
   Date         Time   Version     Size       File name         
   --------------------------------------------------------
   01-Sep-2005  23:52  8.0.0.2157  4,090,656  Msmddo80.dll     
   01-Sep-2005  23:51  8.0.0.2157  9,646,153  Msmdsgn80.dll    
   01-Sep-2005  23:00  8.0.2157.0  1,970,176  Msmdsrv.exe      
   01-Sep-2005  23:52  8.0.2157.0  2,120,408  Msolap80.dll    
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

MORE INFORMATION

For more information about how to enable end users to access cube data, visit the following Microsoft Developer Network (MSDN) Web site:

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 New naming schema for Microsoft SQL Server software update packages

For more information about the terminology that Microsoft uses when Microsoft corrects software after the software 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


Modification Type:MinorLast Reviewed:6/1/2006
Keywords:kbbug kbfix kbHotfixServer kbQFE KB892517 kbAudITPRO kbAudDeveloper