Microsoft KB Archive/922769

From BetaArchive Wiki

Article ID: 922769

Article Last Modified on 10/11/2007



APPLIES TO

  • Microsoft Windows Server 2003, 64-Bit Enterprise Edition
  • Microsoft Windows Server 2003 R2 Enterprise x64 Edition
  • Microsoft Windows Server 2003 R2 Standard x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows XP Professional 64-Bit Edition (Itanium)
  • Microsoft Windows XP Professional x64 Edition




SYMPTOMS

The following audit record may be incorrectly logged in the local Security log in Microsoft Windows Server 2003 or in Microsoft Windows XP:

EventID 516
 

Internal resources allocated for the queuing of audit messages have been exhausted, leading to the loss of some audits. 

       Number of audit messages discarded:      1

This symptom may occur when the following conditions are true:

  • The “Audit object Access” policy is enabled.
  • An access attempt to a named pipe occurs. This named pipe has a system access control list (SACL) in its security descriptor.
  • Windows makes an access control determination for this access attempt.

Instead of event ID 516, you expect the following “object open" audit record (event ID 560) to be logged. Event ID 560 indicates success or failure. Whether a success or a failure is logged depends on the outcome of the access control determination.

EventID 560
 

Object Open:

       Object Server:       Security

       Object Type:  NamedPipe

       Object Name:  \AuditTest

       Handle ID:    1884

       Operation ID: {0,223884}

       Process ID:   1384

       Image File Name:     C:\NamedPipeAudit.exe

       Primary User Name:   Administrator

       Primary Domain:      W03SA

       Primary Logon ID:    (0x0,0x880B)

       Client User Name:    -

       Client Domain:       -

       Client Logon ID:     -

       Accesses:     READ_CONTROL 

                     SYNCHRONIZE 

                     ReadData (or ListDirectory) 

                     WriteData (or AddFile) 

                     AppendData (or AddSubdirectory or CreatePipeInstance) 

                     ReadEA 

                     WriteEA 

                     ReadAttributes 

                     WriteAttributes 

                     

       Privileges:   -

       Restricted Sid Count:      0

       Access Mask:  0x12019F

RESOLUTION

Windows Server 2003

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

To apply this hotfix, you must be running a version of one of the following operating systems:

  • Windows Server 2003 x64 with Service Pack 1 (SP1)
  • Windows Server 2003 IA-64 with Service Pack 1 (SP1)
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 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.

Windows Server 2003 and Windows XP IA-64 versions

File name File version File size Date Time Platform
Npfs.sys 5.2.3790.2750 103,424 19-Jul-2006 13:32 IA-64

Windows Server 2003 and Windows XP x64 versions

File name File version File size Date Time Platform
Npfs.sys 5.2.3790.2750 56,832 19-Jul-2006 13:32 x64

Windows XP

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only 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 Windows XP service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer 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

To apply this hotfix, you must be running a version of one of the following operating systems:

  • Windows XP x64
  • Windows XP IA-64
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 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.

Windows Server 2003 and Windows XP IA-64 versions

File name File version File size Date Time Platform
Npfs.sys 5.2.3790.2750 103,424 19-Jul-2006 13:32 IA-64

Windows Server 2003 and Windows XP x64 versions

File name File version File size Date Time Platform
Npfs.sys 5.2.3790.2750 56,832 19-Jul-2006 13:32 x64


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. 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: Auditing Named Pipes 64-bit IA64 Common Criteria CC

Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver kbwinserv2003presp2fix kbwinserv2003sp2fix KB922769