Microsoft KB Archive/921306

From BetaArchive Wiki

Article ID: 921306

Article Last Modified on 10/11/2007



APPLIES TO

  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003 SP1




SYMPTOMS

On a computer that is running Microsoft Windows Server 2003, a software program may send bad data that logs a Windows Management Instrumentation (WMI) event. In this situation, you randomly receive a 0x00000050 error message.

CAUSE

This problem occurs because of an issue in the Ntoskrnl.exe file.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100 How to obtain the latest service pack for Windows Server 2003


Hotfix Information

Prerequisites

No prerequisites are required.

Restart Requirement

You must restart your computer after you apply this hotfix.

Hotfix Replacement Information

This hotfix does not replace any other hotfixes.

File Information

The English version of this hotfix has the file attributes (or later) 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. Windows Server 2003, x86-based versions

File name File version File size Date Time Platform
Ntkrnlmp.exe 5.2.3790.544 2,240,512 13-Jun-2006 10:02 Not Applicable
Ntkrnlpa.exe 5.2.3790.544 2,068,992 13-Jun-2006 09:38 x86
Ntkrpamp.exe 5.2.3790.544 2,113,024 13-Jun-2006 09:38 Not Applicable
Ntoskrnl.exe 5.2.3790.544 2,206,720 13-Jun-2006 10:01 x86
Srv.sys 5.2.3790.324 355,840 04-May-2005 00:47 x86

Windows Server 2003, x86-based versions with Service Pack 1

File name File version File size Date Time Platform SP requirement
Ntkrnlmp.exe 5.2.3790.2726 2,458,112 16-Jun-2006 10:02 Not Applicable SP1
Ntkrnlpa.exe 5.2.3790.2726 2,270,208 16-Jun-2006 09:37 x86 SP1
Ntkrpamp.exe 5.2.3790.2726 2,310,656 15-Jun-2006 22:28 Not Applicable SP1
Ntoskrnl.exe 5.2.3790.2726 2,418,688 16-Jun-2006 10:02 x86 SP1

Windows Server 2003, x64-based versions with Service Pack 1

File name File version File size Date Time Platform SP requirement
Ntkrnlmp.exe 5.2.3790.2726 4,626,432 15-Jun-2006 22:28 x64 SP1
Ntoskrnl.exe 5.2.3790.2726 4,481,024 15-Jun-2006 22:28 x64 SP1

Windows Server 2003, Itanium-based versions

File name File version File size Date Time Platform
Ntkrnlmp.exe 5.2.3790.544 5,619,200 15-Jun-2006 22:24 IA-64
Srv.sys 5.2.3790.324 994,304 15-Jun-2006 22:24 IA-64

Windows Server 2003, Itanium-based versions with Service Pack 1

File name File version File size Date Time Platform
Ntkrnlmp.exe 5.2.3790.2726 6,502,912 15-Jun-2006 22:28 IA-64


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article. This problem was first corrected in Windows Server 2003 Service Pack 2.

MORE INFORMATION

For more information, 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: Content Maintenance 58662

Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver kbwinserv2003sp2fix KB921306