FIX: You may not be able to capture user dump files in SQL Server 2000 Analysis Services (899024)


The information in this article applies to:

  • Microsoft SQL Server 2000 Analysis Services
Microsoft distributes 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
  • Whether you must restart the computer after you apply the hotfix package
  • Whether the hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes after you apply the hotfix package
  • The files that are contained in the hotfix package

SYMPTOMS

To determine the cause of some problems in Microsoft SQL Server, you may have to capture user dump files. However, you may not be able to capture these files in SQL Server 2000 Analysis Services.

For a list of all publicly released SQL Server 2000 Post-Service Pack 3a hotfixes, see the following article in the Microsoft Knowledge Base:

810185 SQL Server 2000 hotfix update for SQL Server 2000 Service Pack 3 and 3a

RESOLUTION

This hotfix adds a mechanism to capture user dump files when a particular error condition is experienced.

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

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

  • Microsoft SQL Server 2000 Service Pack 3 (SP3)

    For information about how to obtain SQL Server 2000 SP3, see the following article in the Microsoft Knowledge Base:

    290211 How to obtain the latest SQL Server 2000 service pack

  • If you are applying the Microsoft SQL Server 2000 Service Pack 4 (SP4) based version of this hotfix, the server must already be running SP4 for Analysis Services.
  • If you are applying the SP3-based version of this hotfix, the server must already be running SP3 for Analysis Services.

Restart information

You do not have to restart the server after you apply this hotfix. The Analysis Services service is automatically stopped and restarted as part of the hotfix installation process.

Registry information

You must make changes to the registry.

The new mechanism is controlled by four new entries in the registry. These registry entries are located under the following registry key:

HKLM\Software\Microsoft\OLAP Server\CurrentVersion

The four new registry entries are the following:
  • MiniDumpErrorListPFMsg
  • MiniDumpErrorListPFStatus
  • MiniDumpErrorListPFError
  • MiniDumpErrorListSysError
These registry entries are all string types.

The registry values are read every 60 seconds. They accept error values in either base 10 format or hexadecimal format.
Except for the character x, any non-numeric character is treated as a separator for a list of multiple values.
  • 0x40000000 = all informational
  • 0x80000000 = all warnings
  • 0xc0000000 = all errors
  • 0x00000000 = do nothing (placeholder)
  • 0xffffffff = -1 = everything

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 tool in Control Panel.SQL Server 2000 32-bit version for Service Pack 4
File nameFile versionFile sizeDateTimePlatform
Updatelauncher.exe5.2.3790.12888,70402-Sep-200505:23x86
Spupdsvc.exe6.1.22.525,82402-Sep-200505:21x64
Tempcatsign.cdfNot Applicable60402-Sep-200505:44Not Applicable
Msmddo80.dll8.0.0.21574,090,65602-Sep-200501:52x86
Msmdsgn80.dll8.0.0.21579,646,15302-Sep-200501:51x86
Msmdsrv.exe8.0.2157.01,970,17602-Sep-200501:00x86
Msolap80.dll8.0.2157.02,120,40802-Sep-200501:52x86
Sqlstpcustomdll.dll1.0.128.01,367,04002-Sep-200505:20x64
Sqlstpcustomdll.rllNot Applicable25,08802-Sep-200505:20Not Applicable
Spupdsvc.exe6.1.22.522,75201-Sep-200522:17x86
Tempcatsign.cdfNot Applicable60302-Sep-200505:41Not Applicable
Msmddo80.dll8.0.0.21574,090,65602-Sep-200501:52x86
Msmdsgn80.dll8.0.0.21579,646,15302-Sep-200501:51x86
Msmdsrv.exe8.0.2157.01,970,17602-Sep-200501:00x86
Msolap80.dll8.0.2157.02,120,40802-Sep-200501:52x86
Sqlstpcustomdll.dll1.0.128.0943,10401-Sep-200522:17x86
Sqlstpcustomdll.rllNot Applicable24,57601-Sep-200522:17Not Applicable
SQL Server 2000 32-bit version for Service Pack 3
File nameFile versionFile sizeDateTimePlatform
Tempcatsign.cdfNot Applicable95525-May-200500:32Not Applicable
Msdmine.dll8.0.1026.01,380,94425-May-200500:01x86
Msmdcb80.dll8.0.1026.0221,76025-May-200500:01x86
Msmddo80.dll8.0.0.10264,076,10425-May-200500:01x86
Msmdgd80.dll8.0.1026.01,036,86425-May-200500:01x86
Msmdpump.dll8.0.1026.0172,60825-May-200500:01x86
Msmdsgn.rll8.0.1026.0446,52424-May-200523:43Not Applicable
Msmdsgn80.dll8.0.0.10269,642,57225-May-200500:01x86
Msmdsrv.exe8.0.1026.01,856,06825-May-200500:01x86
Msmdvldm.exe8.0.1026.01,401,40825-May-200500:01x86
Msolap80.dll8.0.1026.02,089,55225-May-200500:01x86
Msolap80.rll8.0.1026.0213,06824-May-200522:35Not Applicable
SQL Server 2000 64-bit version for Service Pack 3
File nameFile versionFile sizeDateTimePlatform
Osql.exe2000.80.962.057,90425-May-200518:21x86
Sqlrun.mspNot Applicable11,996,67226-May-200523:31Not Applicable
Note Because of file dependencies, the most recent hotfix or feature that contains these files may 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 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

Modification Type:MinorLast Reviewed:7/25/2006
Keywords:kbfix kbbug kbHotfixServer kbQFE kbpubtypekc KB899024 kbAudITPRO kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.