Select the product you need help with
New AFD connections fail when software that uses TDI drivers is installed on a Windows Server 2008 or Windows Vista SP1 system that is running on a computer that has multiple processorsArticle ID: 961775 - View products that this article applies to. On This PageSYMPTOMSWhen software that uses Transport
Driver Interface (TDI) drivers, such as some antivirus software, is installed
on a Windows Server 2008 system or on Windows Vista Service Pack 1 (SP1)
system, the handle count of the system process keeps increasing. This problem
occurs if the Windows Server 2008 system or the Windows Vista Service Pack 1
(SP1) system is running on a computer that has multiple processors. If this
issue occurs for some time, the computer begins to run out of system resources.
Therefore, any new Ancillary Function Driver for WinSock (AFD) connection to this
computer fails. Additionally, the following problems may occur if the computer is a domain controller:
Log Name: System CAUSEThis problem occurs because of a race condition in which the Tdx.sys driver does
not send a disconnect input/output request packet (IRP) indication to the afd.sys driver. When this occurs, the reference count on the AFD socket is not decremented. Eventually,
the AFD connection is orphaned. The process that owns the orphaned AFD
connection is also orphaned. After the issue occurs for some time, all available ports are consumed. Therefore, many orphaned processes appear. When resources become exhausted, the problem occurs that the "Symptoms" section describes. RESOLUTIONHotfix informationA 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 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.
(http://support.microsoft.com/contactus/?ws=support)
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. PrerequisitesTo apply this hotfix, you must have Windows Vista Service Pack 1 or Windows Server 2008 installed on the computer.Restart requirementYou have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other previously released hotfixes.Registry informationTo use this hotfix, you do not have to make any changes to the registry.File informationThe 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 Vista and Windows Server 2008 file information noteThe .manifest files and the .mum files that are installed in each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.For all supported x86-based versions of Windows Vista and Windows Server 2008Collapse this table
For all supported x64-based versions of Windows Vista and Windows Server 2008Collapse this table
For all supported Itanium-based versions of Windows Server 2008Collapse this table
WORKAROUNDTo work around this problem, use one of the following
methods:
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. MORE INFORMATIONThis problem most commonly occurs on domain controllers
that are running the Microsoft System Center Operations Manager agent. The agent makes repeated local queries to LSASS on port 389. The
queries cause the number of orphaned connections to
increase rapidly. Because of this, the domain controller fails after a few days. Additional file information for Windows Vista and Windows Server 2008Additional files for all supported x86-based versions of Windows Vista and Windows Server 2008Collapse this table
Additional files for all supported x64-based versions of Windows Vista and Windows Server 2008Collapse this table
Additional files for all supported Itanium-based versions of Windows Server 2008Collapse this table
824684
(http://support.microsoft.com/kb/824684/LN/
)
Description of the standard terminology that is used to describe Microsoft software updatesPropertiesArticle ID: 961775 - Last Review: November 27, 2009 - Revision: 3.0 APPLIES TO
| Article Translations |
Back to the top
