To resolve this issue, apply the following hotfix on the web server. After you install this hotfix, the time-out for IP-HTTPS connections is changed to 30 minutes (1800 seconds).
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 this specific problem.
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, submit a request to 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.Prerequisites
To apply this hotfix, you must be running one of the following operating systems:
- Windows Server 2008 R2
- Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry information
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
To change the
EntityBody timer to a value other than 30 minutes, follow these steps:
- Click Start, type regedit in the Start Search box, and then press ENTER.
- Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\IPHLPSVC\Parameters\IPHTTPS\IPHTTPSInterface - Click Edit, point to New, and then click DWORD Value.
- Type HttpEntityBodyTimeout, and then press ENTER.
- Click Edit, and then click Modify.
- Type a value that is from 120-7200.
Note The
HttpEntityBodyTimeout entry is for the
EntityBody timer and is in units of seconds.
Restart requirement
You must restart the computer after you apply this hotfix.Hotfix replacement information
This hotfix does not replace a previously released hotfix.File information
The global 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 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
- 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.1.760 0. 16xxx | Windows Server 2008 R2 | RTM | GDR |
6.1.760 0. 20xxx | Windows Server 2008 R2 | RTM | LDR |
6.1.760 1. 21xxx | Windows Server 2008 R2 | SP1 | LDR |
- 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" 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 x64-based versions of Windows Server 2008 R2
File name | File version | File size | Date | Time | Platform |
---|
Iphlpsvc.dll | 6.1.7600.20967 | 569,344 | 14-May-2011 | 07:34 | x64 |
Iphlpsvcmigplugin.dll | 6.1.7600.16385 | 60,416 | 14-Jul-2009 | 01:41 | x64 |
Iphlpsvc.dll | 6.1.7601.21728 | 570,368 | 14-May-2011 | 07:11 | x64 |
Iphlpsvcmigplugin.dll | 6.1.7600.16385 | 60,416 | 14-Jul-2009 | 01:41 | x64 |
Iphlpsvcmigplugin.dll | 6.1.7600.20967 | 51,200 | 14-May-2011 | 06:32 | x86 |
Iphlpsvcmigplugin.dll | 6.1.7601.21728 | 51,200 | 14-May-2011 | 07:40 | x86 |
For all supported IA-64–based versions of Windows Server 2008 R2
File name | File version | File size | Date | Time | Platform |
---|
Iphlpsvc.dll | 6.1.7600.20967 | 980,480 | 14-May-2011 | 06:19 | IA-64 |
Iphlpsvcmigplugin.dll | 6.1.7600.16385 | 133,632 | 14-Jul-2009 | 01:46 | IA-64 |
Iphlpsvc.dll | 6.1.7601.21728 | 982,016 | 14-May-2011 | 06:14 | IA-64 |
Iphlpsvcmigplugin.dll | 6.1.7600.16385 | 133,632 | 14-Jul-2009 | 01:46 | IA-64 |
Iphlpsvcmigplugin.dll | 6.1.7600.20967 | 51,200 | 14-May-2011 | 06:32 | x86 |
Iphlpsvcmigplugin.dll | 6.1.7601.21728 | 51,200 | 14-May-2011 | 07:40 | x86 |