Error code 1450 after you transfer data by using the named pipes protocol between a client computer and a server that are running Windows Vista or Windows Server 2008

Consider the following scenario. You have a client computer that is running Windows Server 2008 or Windows Vista. You also have a server that is running Windows Server 2008 or Windows Vista. You run an application that uses the named pipes protocol to transfer data between the client computer and the server. After interprocess communication (IPC) between the client computer and the server runs for some time, the application is aborted on the client computer. Additionally, you receive the following error code:When this problem occurs, the value of the Pool Nonpaged Bytes performance counter keeps increasing. If you use a memory monitoring tool to monitor the memory pool, you see that the memory leak occurs in the nonpaged pool and in the SmMs tag.


Additionally, if you look at network traces you may see an excessive number of�STATUS_INVALID_PARAMETER responses to SMB2�requests for�QUERY INFORMATION (0x10), Class=FileNetworkOpenInformation'�on named pipe communication (i.e. on samr or srvsvc pipes), example:

Client Request:
Vista-client�SMB2-server�SMB2�SMB2:C�� QUERY INFORMATION (0x10), Class=FileNetworkOpenInformation (34), FID=0xFFFFFFFF003000D5(samr@#90546)

Server Response:
SMB2-server�Vista-client�SMB2�SMB2:R� - NT Status: System - Error, Code = (13) STATUS_INVALID_PARAMETER� QUERY INFORMATION (0x10) , File=samr@#90546



Note This problem does not occur if the server runs Windows XP or Windows Server 2003.

This problem occurs because of a memory leak in the Mrxsmb20.sys file. The memory leak occurs when a query cannot access a named pipe.

To resolve the problem, apply the hotfix on the client computer.

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 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 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: 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.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the �Hotfix Request� page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, your computer must be running one of the following Windows operating systems:

• Windows Vista Service Pack 1 (SP1)
• Windows Vista Service Pack 2 (SP2)
• Windows Server 2008
• Windows Server 2008 Service Pack 2 (SP2)

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfix.

File information

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table.

Windows Vista and Windows Server 2008 file information notes

• 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.

  Version	Product	SR_Level	Service branch
  6.0.600 0 . 16xxx	Windows Vista	RTM	GDR
  6.0.600 0 . 20xxx	Windows Vista	RTM	LDR
  6.0.600 1 . 18xxx	Windows Vista and Windows Server 2008	SP1	GDR
  6.0.600 1 . 22xxx	Windows Vista and Windows Server 2008	SP1	LDR
  6.0.600 2 . 18xxx	Windows Vista and Windows Server 2008	SP2	GDR
  6.0.600 2 . 22xxx	Windows Vista and Windows Server 2008	SP2	LDR

• Service Pack 1 is integrated into the original release of Windows Server 2008.
• The MANIFEST files (.manifest) and MUM files (.mum) installed for each environment are listed separately . MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

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.

For all supported x86-based versions of Windows Server 2008 and of Windows Vista

For all supported x64-based versions of Windows Server 2008 and of Windows Vista

For all supported Itanium-based versions of Windows Server 2008

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: -

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

Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008

Additional files for all supported Itanium-based versions of Windows Server 2008

For more information about IPC, visit the following Microsoft Developer Network (MSDN) Web site:For more information about named pipes, visit the following MSDN Web site: