|
Article ID: 2497453 - View products that this article applies to. Not sure if this is the right fix? We've added this issue to our memory dump diagnostic
(https://home.diagnostics.support.microsoft.com/SelfHelp?knowledgebaseArticleFilter=2027760)
which can confirm.On This PageSymptomsConsider the following scenario:
Note When this issue occurs, you can generate a dump file for the hung process. If you analyze the dump file by using a debugger, the following call stacks is displayed. The call stacks indicate that multiple requests are waiting to receive a connection to the remote host. However, the maximum number of connections to the remote host is reached. Therefore, the requests stop responding until a time out occurs. Child-SP RetAddr Call Site [Child-SP] [RetAddr] System.Threading.WaitHandle.WaitOne(Int64, Boolean) [Child-SP] [RetAddr] System.Net.ConnectionGroup.FindConnectionAuthenticationGroup(System.Net.HttpWebRequest, System.String) [Child-SP] [RetAddr] System.Net.ConnectionGroup.FindConnection(System.Net.HttpWebRequest, System.String) [Child-SP] [RetAddr] System.Net.ServicePoint.SubmitRequest(System.Net.HttpWebRequest, System.String) [Child-SP] [RetAddr] System.Net.HttpWebRequest.SubmitRequest(System.Net.ServicePoint) CauseThis issue occurs because the HttpWebRequest class does not unlock the underlying connections to the remote host if several requests are aborted. When an HttpWebRequest class locks a connection to a remote host that uses the negotiation or NTLM authentication, other requests cannot use the connection until the previous request is completed and the connection is unlocked. However, the previous request may be aborted while the connection is locked. Therefore, the connection resource is not released in the connection group, and no new connections for requests can be distributed when the connection group limit is reached. ResolutionHotfix informationA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may 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.To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website: http://support.microsoft.com/contactus/?ws=support Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesTo apply this hotfix, you must have one of the following products installed on one of the associated operating system:
Restart requirementYou must restart the computer after you apply this hotfix if the affected files are being used.We recommend that you close all instances of applications that use the .NET Framework before you install this hotfix. Hotfix replacement informationThis hotfix does not replace a previously released hotfix.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.For all supported x86-based versions of the .NET Framework 4.0 for Windows XP, for Windows Server 2003, for Windows Vista, for Windows Server 2008, and for Windows 7Collapse this table
For all supported x64-based versions of the .NET Framework 4.0 for Windows XP, for Windows Server 2003, for Windows Vista, for Windows Server 2008, for Windows 7, and for Windows Server 2008 R2Collapse this table
For all supported IA-64-based versions of the .NET Framework 4.0 for Windows Server 2003, for Windows Server 2008, and for Windows Server 2008 R2Collapse this table
For all supported x86-based versions of the .NET Framework 2.0 for Windows Vista SP2 and for Windows Server 2008 SP2Collapse this table
For all supported x64-based versions of the .NET Framework 2.0 for Windows Vista SP2 and for Windows Server 2008 SP2Collapse this table
For all supported IA-64-based versions of the .NET Framework 2.0 for Windows Server 2008 SP2Collapse this table
For all supported x86-based versions of the .NET Framework 2.0 for Windows 7Collapse this table
For all supported x64-based versions of the .NET Framework 2.0 for Windows 7 and for Windows Server 2008 R2Collapse this table
For all supported IA-64-based versions of the .NET Framework 2.0 for for Windows Server 2008 R2Collapse this table
For all supported x86-based versions of the .NET Framework 2.0 for Windows 7 SP1Collapse this table
For all supported x64-based versions of the .NET Framework 2.0 for Windows 7 SP1 and for Windows Server 2008 R2 SP1Collapse this table
For all supported IA-64-based versions of the .NET Framework 2.0 for Windows Server 2008 R2 SP1Collapse this table
StatusMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More informationAdditional file informationAdditional files for x86-based versions of Windows Vista SP2 and of Windows Server 2008 SP2Collapse this table
Additional files for x64-based versions of Windows Vista SP2 and of Windows Server 2008 SP2Collapse this table
Additional files for IA-64-based versions of Windows Server 2008 SP2Collapse this table
Additional files for x86-based versions of Windows 7Collapse this table
Additional files for x64-based versions of Windows 7 and of Windows Server 2008 R2Collapse this table
Additional files for IA-64-based versions of Windows Server 2008 R2Collapse this table
Additional files for x86-based version of Windows 7 SP1Collapse this table
Additional files for x64-based versions of Windows 7 SP1 and of Windows Server 2008 R2 SP1Collapse this table
Additional files for IA-64-based versions of Windows Server 2008 R2 SP1Collapse this table
PropertiesArticle ID: 2497453 - Last Review: October 9, 2014 - Revision: 5.0
|
Contact us for more help |
