Applications or services that rely on local named pipes encounter a connectivity failure in Windows Server 2008 SP2 or in Windows Vista SP2

Article translations Article translations
Article ID: 2551685 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You have a computer that is running Windows Server 2008 Service Pack (SP2) or Windows Vista Service Pack (SP2).
  • You specify the dwPipeMode parameter to the PIPE_REJECT_REMOTE_CLIENTS flag when you use the CreateNamedPipe() function to create a server-side named pipe.
  • You try to make a local connection to the server-side named pipe on the computer.
In this scenario, the local connection fails and returns error code 231 (ERROR_PIPE_BUSY). Additionally, applications or services that rely on local named pipes may experience connectivity failures.

Note
 This issue was introduced by hotfix package 954442. Because hotfix package 954442 is included in Service Pack 2 for Windows Server 2008 and for Windows Vista, most customers experience the issue after they install Service Pack 2 for Windows Server 2008 or for Windows Vista.

CAUSE

This issue occurs because the Named Pipe File System driver (npfs.sys) does not correctly handle local named pipe client connection requests.

RESOLUTION

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 the problem that is described in this article. 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 exist, 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 website:
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 Windows Vista Service Pack 2 (SP2) or Windows Server 2008 Service Pack 2 (SP2). For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:
935791 How to obtain the latest Windows Vista service pack
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849 How to obtain the latest service pack for Windows Server 2008

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Vista and Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system to which each hotfix applies.
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.0.600 2 . 22xxxWindows Vista and Windows Server 2008SP2LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are very important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Npfs.sys6.0.6002.2264735,32819-May-201113:25x86
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Npfs.sys6.0.6002.2264744,54419-May-201114:07x64
For all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Npfs.sys6.0.6002.22647110,59219-May-201113:50IA-64

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 CreateNamedPipe function, visit the following Microsoft website:
CreateNamedPipe function
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
954442 Applications or services that rely on the Named Pipe File System may encounter latency or time-out issues when many connections are made to a named pipe in Windows Server 2008 or in Windows Vista SP1
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 file information

Additional file information for Windows Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008
Collapse this tableExpand this table
File nameUpdate.mum
File versionNot applicable
File size3,078
Date (UTC)19-May-2011
Time (UTC)18:06
PlatformNot applicable
File nameX86_3c35b4eff73009ce4a323704fa7d0e56_31bf3856ad364e35_6.0.6002.22647_none_95e4790babaf7f46.manifest
File versionNot applicable
File size692
Date (UTC)19-May-2011
Time (UTC)18:06
PlatformNot applicable
File nameX86_microsoft-windows-npfs_31bf3856ad364e35_6.0.6002.22647_none_a8bd65163349325a.manifest
File versionNot applicable
File size5,031
Date (UTC)19-May-2011
Time (UTC)15:59
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008
Collapse this tableExpand this table
File nameAmd64_8bd078f424bcd7f56c60261e18ee00dd_31bf3856ad364e35_6.0.6002.22647_none_a516380b5ecd205e.manifest
File versionNot applicable
File size696
Date (UTC)19-May-2011
Time (UTC)18:06
PlatformNot applicable
File nameAmd64_microsoft-windows-npfs_31bf3856ad364e35_6.0.6002.22647_none_04dc0099eba6a390.manifest
File versionNot applicable
File size5,035
Date (UTC)19-May-2011
Time (UTC)16:26
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size3,102
Date (UTC)19-May-2011
Time (UTC)18:06
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameIa64_9aaa91a6e3be0e8125213ac29506035d_31bf3856ad364e35_6.0.6002.22647_none_4bcf9c3404af22e7.manifest
File versionNot applicable
File size694
Date (UTC)19-May-2011
Time (UTC)18:06
PlatformNot applicable
File nameIa64_microsoft-windows-npfs_31bf3856ad364e35_6.0.6002.22647_none_a8bf090c33473b56.manifest
File versionNot applicable
File size5,033
Date (UTC)19-May-2011
Time (UTC)15:57
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,255
Date (UTC)19-May-2011
Time (UTC)18:06
PlatformNot applicable

Properties

Article ID: 2551685 - Last Review: June 15, 2011 - Revision: 1.0
APPLIES TO
  • Windows Server 2008 Service Pack 2, when used with:
    • Windows Server 2008 Datacenter
    • Windows Server 2008 Datacenter without Hyper-V
    • Windows Server 2008 Enterprise
    • Windows Server 2008 Enterprise without Hyper-V
    • Windows Server 2008 for Itanium-Based Systems
    • Windows Server 2008 Foundation
    • Windows Server 2008 Standard
    • Windows Server 2008 Standard without Hyper-V
    • Windows Web Server 2008
  • Windows Vista Service Pack 2, when used with:
    • Windows Vista Business
    • Windows Vista Business 64-bit Edition
    • Windows Vista Enterprise
    • Windows Vista Enterprise 64-bit Edition
    • Windows Vista Home Basic
    • Windows Vista Home Basic 64-bit Edition
    • Windows Vista Home Premium
    • Windows Vista Home Premium 64-bit Edition
    • Windows Vista Starter
    • Windows Vista Ultimate
    • Windows Vista Ultimate 64-bit Edition
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseadvanced KB2551685

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com