A Windows Server 2003-based file server may return file identifiers (Fids) that have the 0xffff value under heavy stress

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

On This Page

SYMPTOMS

A Windows Server 2003-based file server may return file identifiers (Fids) that have the 0xffff value under heavy stress. These file identifiers are not valid and make the file share operation fail.

For example, when you move lots of shared files through the network, the operation stops, and some files cannot be moved.

CAUSE

This problem occurs because the file server does not comply with the file identifier generation algorithm.

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 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:
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, the computer must have Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2) installed.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released 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 SP1, x86-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Srv.sys5.2.3790.3308362,49617-Mar-200910:55x86
Windows Server 2003 SP2, x86-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Srv.sys5.2.3790.4476358,91217-Mar-200912:19x86
Windows Server 2003 SP1, Itanium-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Srv.sys5.2.3790.33081,112,06417-Mar-200904:18IA-64
Windows Server 2003 SP2, Itanium-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Srv.sys5.2.3790.44761,113,08817-Mar-200904:22IA-64
Windows Server 2003 and Windows XP, x64-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Srv.sys5.2.3790.3308675,32817-Mar-200904:18x64
Windows Server 2003 SP2 and Windows XP SP2, x64-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Srv.sys5.2.3790.4476648,70417-Mar-200904:26x64

STATUS

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

MORE INFORMATION

If you monitor the network traffic when this problem occurs, you may obtain a network trace that resembles the following:
<IP address> <IP address> SMB	SMB:R; Nt Create Andx, FID = 0xFFFF (\test.bat@#30)
<IP address> <IP address>	SMB	SMB:C; Read Andx, FID = 0xFFFF (\test.bat@#30), 20 bytes at Offset 0
<IP address> <IP address>	SMB	SMB:R; Read Andx, FID = 0xFFFF (\test.bat@#30), 20 bytes
For more information about the file identifier generation algorithm, visit the following Microsoft Web site:
http://msdn.microsoft.com/en-us/library/cc246243.aspx
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

Properties

Article ID: 967176 - Last Review: October 7, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Keywords: 
kbautohotfix kbexpertiseadvanced kbfix kbsurveynew kbqfe KB967176

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