FIX: A drillthrough request may cause a SQL Server 2000 Analysis Services server to shut down

View products that this article applies to.

SYMPTOMS

If a drillthrough request is sent to Microsoft SQL Server 2000 Analysis Services for a cube or a virtual cube during a Refresh Data processing operation, a fatal error may occur on the Analysis Services server and it may shut down. If the drillthrough request is issued when no processing operations are occurring, it is successful.

Back to the top

CAUSE

When a drillthrough is requested, the OLAP provider submits a separate drillthrough request to the server for each partition in a cube. When the Analysis Services server receives the drillthrough request, it generates the necessary SQL statement for the drillthrough, passes the statement to the relational data source, and then returns the results to the client. During a Refresh Data processing operation on a cube, Analysis Services makes copies of the existing partitions in a cube and stores data in the partition copies. At commit time, Analysis Services renames the copied partitions and deletes the old partitions. If a drillthrough request is generated by a client when the new partitions are being renamed, the client may detect both the new partition and the old partition and generate a drillthrough request for each partition. If the old partition is deleted after the drillthrough request is received but before the SQL statement is generated, Analysis Services tries to access the deleted partition to generate the SQL statement and this problem occurs.

Back to the top

RESOLUTION

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 (http://support.microsoft.com/kb/290211/ ) How to obtain the latest SQL Server 2000 service pack

Back to the top

Hotfix information

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
   --------------------------------------------------------------
   03-Nov-2003  17:08  8.0.874.0         217,668  Msmdcb80.dll     
   28-Oct-2003  02:58  8.0.0.872       4,059,716  Msmddo80.dll     
   03-Nov-2003  17:08  8.0.874.0       1,032,768  Msmdgd80.dll     
   28-Oct-2003  02:58  8.0.823.0         172,608  Msmdpump.dll     
   28-Oct-2003  02:58  8.0.0.864       9,638,468  Msmdsgn80.dll    
   04-Nov-2003  21:45  8.0.875.0       1,835,588  Msmdsrv.exe      
   03-Nov-2003  17:08  8.0.874.0       2,077,264  Msolap80.dll     
   10-May-2003  08:05  8.0.820.0         213,069  Msolap80.rll

Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

Back to the top

SQL Server 2000 Analysis Services 64-bit

Back to the top

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 (http://support.microsoft.com/kb/290211/ ) How to obtain the latest SQL Server 2000 service pack

Back to the top

Hotfix information

For more information about a hotfix build that is designed to be applied on a server that is running SQL Server 2000 Analysis Services 64-bit, or to find out if a fix is scheduled to be included in SQL Server 2000 Analysis Services 64-bit Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:

831653 (http://support.microsoft.com/kb/831653/ ) Availability of Analysis Services 2000 64-bit Hotfix Build

Back to the top

STATUS

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

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

Back to the top