Article ID: 922769 - Last Review: October 9, 2011 - Revision: 3.0

An "event ID 516" audit record may be incorrectly logged when an access attempt to a named pipe occurs in Windows Server 2003 or in Windows XP

Hotfix Download Available
View and request hotfix downloads

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

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

Back to the top

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 (http://support.microsoft.com/kb/889100/ ) How to obtain the latest service pack for Windows Server 2003

Hotfix information

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:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

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.

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

Collapse this tableExpand this table

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

Collapse this tableExpand this table

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

Back to the top

Windows XP

Hotfix information

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

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.

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

Collapse this tableExpand this table

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

Collapse this tableExpand this table

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

Back to the top

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.

Back to the top