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

On This Page

Symptoms

Consider the following scenario:
  • You have a third-party proxy server that enables communication only over port 80.
  • You configure a computer that is running one of the following operating systems to use this proxy server for all protocols:
    • Windows 8.1
    • Windows Server 2012 R2
    • Windows 7
    • Windows Server 2008 R2
  • You configure the proxy bypass list to contain settings for internal servers.
  • You enable the Bypass proxy server for local addresses option.
  • You configure Microsoft Outlook 2010 or Microsoft Outlook 2013 to connect to the newest Microsoft Office 365 mailbox (Wave15).
  • You start Outlook, and it tries to connect to Outlook.Office365.com.

In this scenario, it takes two to three minutes to obtain the initial connection.

Cause

This problem occurs because RPC waits for the direct connection to time out before it selects the proxy server. This causes the delay.

Resolution

Update information for Windows 8.1 and Windows Server 2012 R2

To resolve this problem for Windows 8.1 and Windows Server 2012 R2, take both of the following actions:
  • Apply Windows update 2919355.
  • Apply either Outlook 2013 update 2878323 or Outlook 2010 update 2878254, depending on your configuration.
  • Create the EnableForceHttpProxy registry value and set it to 1.

    To create the EnableForceHttpProxy registry value, follow these steps:
    1. Exit Outlook.
    2. Start Registry Editor.

      Swipe in from the right to open the charms, tap or click Search, and then type regedit.exe in the search box. Or, type regedit.exe at the Start screen, and then tap or click regedit in the search results.
    3. Locate and then select the following registry key:

      HKEY_CURRENT_USER\Software\Microsoft\Office\x.0\Outlook\RPC


      Note In this key path, the placeholder x.0represents 15.0 for Outlook 2013 and 14.0 for Outlook 2010.
    4. On the Edit menu, click New, and then click DWORD Value.
    5. Type EnableForceHttpProxy.
    6. On the Edit menu, click Modify.
    7. Type 1, and then click OK.
    8. Exit Registry Editor.
    9. Start Outlook.

Update information for Windows 7 and Windows Server 2008 R2

To resolve this problem for Windows 7 and Windows Server 2008 R2, take both of the following actions:
  • Apply the Windows hotfix that is mentioned in this article.
  • Apply either Outlook 2013 update 2878323 or Outlook 2010 update 2878254, depending on your configuration.
  • Create the EnableForceHttpProxy registry value and set it to 1.

    To create the EnableForceHttpProxy registry value, follow these steps:
    1. Exit Outlook.
    2. Start Registry Editor.

      Click Start, type regedit in the Start Search box, and then press Enter. If you are prompted for an administrator password or for confirmation, type the password, or click Allow.
    3. Locate and then select the following registry key:

      HKEY_CURRENT_USER\Software\Microsoft\Office\x.0\Outlook\RPC


      Note In this key path, the placeholder x.0represents 15.0 for Outlook 2013 and 14.0 for Outlook 2010.
    4. On the Edit menu, click New, and then click DWORD Value.
    5. Type EnableForceHttpProxy.
    6. On the Edit menu, click Modify.
    7. Type 1, and then click OK.
    8. Exit Registry Editor.
    9. Start Outlook.

Hotfix information

A supported hotfix is available from Microsoft Support. 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, go to the following Microsoft website:
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, you must have Service Pack 1 for Windows 7 or Windows Server 2008 R2 installed.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

File information

Collapse this imageExpand this image
assets folding start collapsed
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 7 and Windows Server 2008 R2 file information and 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.
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.1.760 1 . 18xxxWindows 7 and Windows Server 2008 R2SP1GDR
    6.1.760 1 . 22xxxWindows 7 and Windows Server 2008 R2SP1LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • 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 7 and 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 x86-based versions of Windows 7
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Rpchttp.dll6.1.7601.18350139,77624-Dec-201313:49x86
Rpchttp.dll6.1.7601.22550140,80024-Dec-201313:59x86
Rpcrt4.dll6.1.7601.22550653,31224-Dec-201313:59x86
For all supported x64-based versions of Windows 7 and Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Rpchttp.dll6.1.7601.18350187,90424-Dec-201314:13x64
Rpchttp.dll6.1.7601.22550189,44024-Dec-201314:19x64
Rpcrt4.dll6.1.7601.225501,216,00024-Dec-201314:19x64
Rpcrt4.dll6.1.7601.22550664,06424-Dec-201314:00x86
Rpchttp.dll6.1.7601.18350139,77624-Dec-201313:49x86
Rpchttp.dll6.1.7601.22550140,80024-Dec-201313:59x86
For all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Rpchttp.dll6.1.7601.18350397,31224-Dec-201313:17IA-64
Rpchttp.dll6.1.7601.22550400,89624-Dec-201313:23IA-64
Rpcrt4.dll6.1.7601.225502,585,08824-Dec-201313:23IA-64
Rpcrt4.dll6.1.7601.22550664,06424-Dec-201314:00
Rpchttp.dll6.1.7601.18350139,77624-Dec-201313:49x86
Rpchttp.dll6.1.7601.22550140,80024-Dec-201313:59x86

Additional file information for Windows 7 and Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File nameX86_1e004a9b842cc99cf2e30c45da02f52f_31bf3856ad364e35_6.1.7601.22550_none_d00e6642edfd0dcd.manifest
File versionNot applicable
File size697
Date (UTC)24-Dec-2013
Time (UTC)19:05
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_96182bdb3e23a60a186eea6c82317348_31bf3856ad364e35_6.1.7601.22550_none_15d8f0f38b71495a.manifest
File versionNot applicable
File size1,037
Date (UTC)24-Dec-2013
Time (UTC)19:05
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_9dea81ad248986622498e3823478fdc5_31bf3856ad364e35_6.1.7601.18350_none_e55d0f9025b98132.manifest
File versionNot applicable
File size696
Date (UTC)24-Dec-2013
Time (UTC)19:05
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-rpc-http_31bf3856ad364e35_6.1.7601.18350_none_a1d0fb6f9dba2c74.manifest
File versionNot applicable
File size8,958
Date (UTC)24-Dec-2013
Time (UTC)14:18
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-rpc-http_31bf3856ad364e35_6.1.7601.22550_none_a25a9a20b6d7c965.manifest
File versionNot applicable
File size8,958
Date (UTC)24-Dec-2013
Time (UTC)14:30
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-rpc-local_31bf3856ad364e35_6.1.7601.22550_none_b65c4c47bc982f16.manifest
File versionNot applicable
File size59,061
Date (UTC)24-Dec-2013
Time (UTC)14:28
SHA-1 hashNot applicable
MD5 hashNot applicable
Additional files for all supported x64-based versions of Windows 7 and Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_1913b371af66966563572f5345807773_31bf3856ad364e35_6.1.7601.22550_none_f2fa5b555f38635e.manifest
File versionNot applicable
File size1,386
Date (UTC)24-Dec-2013
Time (UTC)19:05
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_396f05c09dad7fc3bff0d8ca6ad0832f_31bf3856ad364e35_6.1.7601.22550_none_bfaacf2ecbd94359.manifest
File versionNot applicable
File size1,726
Date (UTC)24-Dec-2013
Time (UTC)19:05
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_67139939801802df8eacad7cea9a19c6_31bf3856ad364e35_6.1.7601.18350_none_c0961e48f995c75e.manifest
File versionNot applicable
File size700
Date (UTC)24-Dec-2013
Time (UTC)19:05
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_7c8130b8de898b5c3082958a3a70f178_31bf3856ad364e35_6.1.7601.18350_none_82d2ebf288a0758e.manifest
File versionNot applicable
File size1,040
Date (UTC)24-Dec-2013
Time (UTC)19:05
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_9dea81ad248986622498e3823478fdc5_31bf3856ad364e35_6.1.7601.18350_none_417bab13de16f268.manifest
File versionNot applicable
File size698
Date (UTC)24-Dec-2013
Time (UTC)19:05
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_b1cc2de8936bcfa414e7cf73109f483f_31bf3856ad364e35_6.1.7601.22550_none_385ed92010921933.manifest
File versionNot applicable
File size701
Date (UTC)24-Dec-2013
Time (UTC)19:05
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_f3e733f95214e5bd3cfcdb801cd4cae7_31bf3856ad364e35_6.1.7601.22550_none_279c3085535c54bd.manifest
File versionNot applicable
File size698
Date (UTC)24-Dec-2013
Time (UTC)19:05
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_microsoft-windows-rpc-http_31bf3856ad364e35_6.1.7601.18350_none_fdef96f356179daa.manifest
File versionNot applicable
File size8,962
Date (UTC)24-Dec-2013
Time (UTC)14:44
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_microsoft-windows-rpc-http_31bf3856ad364e35_6.1.7601.22550_none_fe7935a46f353a9b.manifest
File versionNot applicable
File size8,962
Date (UTC)24-Dec-2013
Time (UTC)14:48
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_microsoft-windows-rpc-local_31bf3856ad364e35_6.1.7601.22550_none_127ae7cb74f5a04c.manifest
File versionNot applicable
File size59,065
Date (UTC)24-Dec-2013
Time (UTC)14:46
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameWow64_microsoft-windows-rpc-local_31bf3856ad364e35_6.1.7601.22550_none_1ccf921da9566247.manifest
File versionNot applicable
File size59,071
Date (UTC)24-Dec-2013
Time (UTC)14:12
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-rpc-http_31bf3856ad364e35_6.1.7601.18350_none_a1d0fb6f9dba2c74.manifest
File versionNot applicable
File size8,958
Date (UTC)24-Dec-2013
Time (UTC)14:18
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-rpc-http_31bf3856ad364e35_6.1.7601.22550_none_a25a9a20b6d7c965.manifest
File versionNot applicable
File size8,958
Date (UTC)24-Dec-2013
Time (UTC)14:30
SHA-1 hashNot applicable
MD5 hashNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameIa64_75175420d5272a253a19fcd227505646_31bf3856ad364e35_6.1.7601.18350_none_7b9ec5c0624d3282.manifest
File versionNot applicable
File size1,038
Date (UTC)24-Dec-2013
Time (UTC)19:05
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameIa64_af677668fe2c90b4c4cdc771433cf50b_31bf3856ad364e35_6.1.7601.22550_none_1558dc0246044100.manifest
File versionNot applicable
File size1,723
Date (UTC)24-Dec-2013
Time (UTC)19:05
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameIa64_microsoft-windows-rpc-http_31bf3856ad364e35_6.1.7601.18350_none_a1d29f659db83570.manifest
File versionNot applicable
File size8,960
Date (UTC)24-Dec-2013
Time (UTC)14:00
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameIa64_microsoft-windows-rpc-http_31bf3856ad364e35_6.1.7601.22550_none_a25c3e16b6d5d261.manifest
File versionNot applicable
File size8,960
Date (UTC)24-Dec-2013
Time (UTC)14:17
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameIa64_microsoft-windows-rpc-local_31bf3856ad364e35_6.1.7601.22550_none_b65df03dbc963812.manifest
File versionNot applicable
File size59,063
Date (UTC)24-Dec-2013
Time (UTC)14:19
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameWow64_microsoft-windows-rpc-local_31bf3856ad364e35_6.1.7601.22550_none_1ccf921da9566247.manifest
File versionNot applicable
File size59,071
Date (UTC)24-Dec-2013
Time (UTC)14:12
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-rpc-http_31bf3856ad364e35_6.1.7601.18350_none_a1d0fb6f9dba2c74.manifest
File versionNot applicable
File size8,958
Date (UTC)24-Dec-2013
Time (UTC)14:18
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-rpc-http_31bf3856ad364e35_6.1.7601.22550_none_a25a9a20b6d7c965.manifest
File versionNot applicable
File size8,958
Date (UTC)24-Dec-2013
Time (UTC)14:30
SHA-1 hashNot applicable
MD5 hashNot applicable
Collapse this imageExpand this image
assets folding end collapsed

Status

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

More information

This hotfix adds the following non-user-configurable registry key:

Registry location:
HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc

DWORD name: ConnectionOptionsFlag
DWORD value: 00000001


Note Changing this registry key will not change the RPC behavior. This key is added only to indicate the presence of a new HTTP connection option.

The delay may still occur for connections to shared folders. This is because a shared folder is not added as an Exchange mailbox account. Therefore, Outlook is unable to determine if it is located on an Exchange Online mailbox.

References

Learn about the terminology that Microsoft uses to describe software updates.

Properties

Article ID: 2916915 - Last Review: April 22, 2014 - Revision: 8.0
Applies to
  • Windows 8.1
  • Windows 8.1 Enterprise
  • Windows 8.1 Pro
  • Windows Server 2012 R2 Datacenter
  • Windows Server 2012 R2 Essentials
  • Windows Server 2012 R2 Foundation
  • Windows Server 2012 R2 Standard
  • Windows 7 Professional
  • Windows 7 Enterprise
  • Windows 7 Ultimate
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Foundation
  • Windows Server 2008 R2 Standard
  • Microsoft Outlook 2013
  • Microsoft Outlook 2010
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbexpertiseinter kbsurveynew kbbug KB2916915

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