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.
This article describes the following about this hotfix release:
The issues that are fixed by the hotfix package
The prerequisites for installing the hotfix package
Whether you must restart the computer after you install the hotfix package
Whether the hotfix package is replaced by any other hotfix package
Whether you must make any registry changes
The files that are contained in the hotfix package
Consider the following scenario. You have an application that connects to an instance of Microsoft SQL Server 2000 Analysis Services by using Microsoft OLE DB Provider for OLAP Services 8.0 (Msolap80.dll). In the application, you try to obtain property sets that are supported by the provider. One of the property sets contains more than 64 properties. On the computer, you use the Page Heap tool (Pageheap.exe) to troubleshoot heap corruption issues for the application process. You run the following command on the computer:
Pageheap.exe /p /enable ProcessName /full
In this scenario, you experience one or more of the following symptoms when you run the application:
You receive incorrect data from Analysis Services.
An access violation occurs.
A minidump file is generated in the Analysis Services log folder.
For example, you may experience this problem after you run the command when you use ProClarity Analytics Server.
This problem occurs because the Microsoft OLE DB Provider for OLAP Services 8.0 uses an 8-byte bitmap for each property set to count the supported properties.
An access violation may occur when the following conditions are true:
A property set contains more than 64 properties.
The application reads the data beyond the allocated buffer.
Note This problem does not occur when write operations occur. Typically, this access violation only occurs in rare cases in which the buffer is located on a page boundary and the next page is not available.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
To apply this hotfix, you must have SQL Server 2000 Service Pack 4 installed. 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 How to obtain the latest SQL Server 2000 service pack
You do not have to restart the computer after you apply this hotfix.
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 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.
To work around this problem, run the following command:
Pageheap.exe /p /disable ProcessName /full
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 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 software update terminology, 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