FIX: SQL Server 2000 Analysis Services may unexpectedly close when you process a cube by using a custom Decision Support Object application and you query the cube in parallel by using one or more threads

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

Microsoft SQL Server 2000 Analysis Services may unexpectedly close when all the following conditions are true:

• You process a cube by using Analysis Manager or a custom Decision Support Object (DSO) application.
• The cube contains one or more custom dimension security definitions for a role.
• An application client that belongs to a custom dimension security role uses one or more threads to query the cube in parallel.

This problem occurs because SQL Server 2000 Analysis Services evaluates and caches the security context that applies to a client connection when the client connects to Analysis Services. After a cube is fully processed, the cached security contexts for the client connection must be cleared and re-evaluated before the next request for the client connection occurs. When the cached security contexts are not correctly cleared, and the cached security contexts create an invalid pointer for one or more of the cached security contexts, you experience the problem that is mentioned in the "Symptom" section.

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 Analysis Services 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 Microsoft SQL Server 2000 Analysis Services Service Pack 4 (SP4) installed to apply this hotfix.

For more information about how to obtain SQL Server 2000 Analysis Services Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:

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 after you apply this hotfix.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article describes. 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 32-bit versions

SQL Server 2000 Analysis Services 64-bit version

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.

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