You install the Active Directory Federation Services (AD FS) 2.0 on a computer that is running Windows Server 2008 R2 or Windows Server 2008 Service Pack 2 (SP2).
Some clients send many HTTP SOAP requests for the metadata of the AD FS 2.0 service to the "/adfs/services/trust/mex" SOAP Metadata Exchange endpoint for AD FS 2.0.
In this scenario, memory is leaked until garbage collection occurs if the HTTP SOAP requests fail. Additionally, the Metadata Exchange endpoint may stop responding, and then the client receives an instance of the "500" error code from the AD FS 2.0 server.
Note After a garbage collection occurs, the Metadata Exchange endpoint may stop responding again if client errors build up.
This issue occurs because AD FS 2.0 leaks memory when a HTTP SAOP request to the "/adfs/services/trust/mex" Metadata Exchange endpoint fails. Therefore, the endpoint may be unable to process any new requests after a while.
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.
To apply this hotfix, you must be running Windows Server 2008 R2 or Windows Server 2008 Service Pack 2 (SP2). Additionally, you must have Active Directory Federation Services (AD FS) 2.0 installed.
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The English (United States) 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 Server 2008 R2 or Windows Server 2008 file information notes
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 R2 and for Windows Server 2008" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. 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