Microsoft KB Archive/899024

From BetaArchive Wiki

Article ID: 899024

Article Last Modified on 11/21/2006



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:

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 name File version File size Date Time Platform
Updatelauncher.exe 5.2.3790.1288 8,704 02-Sep-2005 05:23 x86
Spupdsvc.exe 6.1.22.5 25,824 02-Sep-2005 05:21 x64
Tempcatsign.cdf Not Applicable 604 02-Sep-2005 05:44 Not Applicable
Msmddo80.dll 8.0.0.2157 4,090,656 02-Sep-2005 01:52 x86
Msmdsgn80.dll 8.0.0.2157 9,646,153 02-Sep-2005 01:51 x86
Msmdsrv.exe 8.0.2157.0 1,970,176 02-Sep-2005 01:00 x86
Msolap80.dll 8.0.2157.0 2,120,408 02-Sep-2005 01:52 x86
Sqlstpcustomdll.dll 1.0.128.0 1,367,040 02-Sep-2005 05:20 x64
Sqlstpcustomdll.rll Not Applicable 25,088 02-Sep-2005 05:20 Not Applicable
Spupdsvc.exe 6.1.22.5 22,752 01-Sep-2005 22:17 x86
Tempcatsign.cdf Not Applicable 603 02-Sep-2005 05:41 Not Applicable
Msmddo80.dll 8.0.0.2157 4,090,656 02-Sep-2005 01:52 x86
Msmdsgn80.dll 8.0.0.2157 9,646,153 02-Sep-2005 01:51 x86
Msmdsrv.exe 8.0.2157.0 1,970,176 02-Sep-2005 01:00 x86
Msolap80.dll 8.0.2157.0 2,120,408 02-Sep-2005 01:52 x86
Sqlstpcustomdll.dll 1.0.128.0 943,104 01-Sep-2005 22:17 x86
Sqlstpcustomdll.rll Not Applicable 24,576 01-Sep-2005 22:17 Not Applicable
SQL Server 2000 32-bit version for Service Pack 3
File name File version File size Date Time Platform
Tempcatsign.cdf Not Applicable 955 25-May-2005 00:32 Not Applicable
Msdmine.dll 8.0.1026.0 1,380,944 25-May-2005 00:01 x86
Msmdcb80.dll 8.0.1026.0 221,760 25-May-2005 00:01 x86
Msmddo80.dll 8.0.0.1026 4,076,104 25-May-2005 00:01 x86
Msmdgd80.dll 8.0.1026.0 1,036,864 25-May-2005 00:01 x86
Msmdpump.dll 8.0.1026.0 172,608 25-May-2005 00:01 x86
Msmdsgn.rll 8.0.1026.0 446,524 24-May-2005 23:43 Not Applicable
Msmdsgn80.dll 8.0.0.1026 9,642,572 25-May-2005 00:01 x86
Msmdsrv.exe 8.0.1026.0 1,856,068 25-May-2005 00:01 x86
Msmdvldm.exe 8.0.1026.0 1,401,408 25-May-2005 00:01 x86
Msolap80.dll 8.0.1026.0 2,089,552 25-May-2005 00:01 x86
Msolap80.rll 8.0.1026.0 213,068 24-May-2005 22:35 Not Applicable
SQL Server 2000 64-bit version for Service Pack 3
File name File version File size Date Time Platform
Osql.exe 2000.80.962.0 57,904 25-May-2005 18:21 x86
Sqlrun.msp Not Applicable 11,996,672 26-May-2005 23:31 Not 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



Additional query words: registry crash dump OLAP troubleshoot troubleshooting

Keywords: kbfix kbbug kbpubtypekc kbhotfixserver kbqfe KB899024