It's been a while since we last blogged about this Outlook feature that most users feel is an error, the RPC Dialog Box. You might get a popup error that will say:
Outlook is retrieving data from the Microsoft Exchange Server <Server name>. You can cancel the request or minimize this message to the Windows taskbar until Outlook closes the message automatically.There are many potential causes or combinations of areas that need to be addressed to properly diagnose and correct this issue. First, please keep in mind that the RPC Dialog Box is something that works off a timer. We have 5 to 8 seconds (depending upon Outlook version, 5 seconds in Outlook 2002 and 8 seconds in Outlook 2003 and 2007) to get an RPC request on the network, to the server, the server to respond, get its response on the network and the client to receive. With that being said, I call this a 10,000 foot problem. There is not necessarily a specific event generated within the application that you can just point your finger to. The idea behind troubleshooting these types of issues is you need to build a funnel to rule out what is not causing them. It's basically a process of elimination. The troubleshooting steps that I have outlined below are for what I would call a "remote client". This does not necessarily mean remote clients are connected via a VPN, it just means that you may be in another building, campus location, or on a different network segment. The affected clients are not "local" to the Exchange server. Typically if the RPC Dialog Box affected all users in your environment, I would also be looking a data from the server, along with the network and the client configuration. In troubleshooting a remote client scenario, it has already been pre-determined that "local" users are not impacted, and it is only users at a separate or external location. I can then narrow the 10,000 foot problem to let's say 5,000 feet. First I want to know about connectivity and the topology itself. There are some simple utilities that I run to acquire the information needed: 1. From the Outlook client workstation use Tracert to determine how many hops from the impacted Outlook Client to the Exchange Server? What devices do the IP Addresses map to? 258495 XCLN: Troubleshooting Client Connectivity Issues Using Command Line Utilities http://support.microsoft.com/default.aspx?scid=kb;EN-US;258495 I want to know what each networking device is relative to the IP's that are returned. Are any of these devices firewalls and do they have a "Session time out" setting similar to our value for TCPKeepAliveTime? Our defaults are 2 hours as documented in: 324270 How to harden the TCP/IP stack against denial of service attacks in Windows Server 2003 http://support.microsoft.com/default.aspx?scid=kb;EN-US;324270 2. From the Outlook client workstation test for a Black Hole Router by issuing a ping command with a packet size: Ping <exchange server_name> or <Exchange server ip address> -f -l 1472 By "pinging" with a packet size, I'm looking to see if there are any segments that have smaller MTU sizes configured. The return value if this is occurring would come back as:
Packet needs to be fragmented but DF setYou can find more information in the Knowledge Base: 314825 How to Troubleshoot Black Hole Router Issues http://support.microsoft.com/default.aspx?scid=kb;EN-US;314825 3. Does your Network include a WAN Accelerator? Can you bypass the device, or (depending on vendor) either exclude MAPI or RPC traffic? WAN Accelerators generally come in 2 flavors: Compress the compressed, or pattern matching. RPC is already compressed and the re-compressed data does not necessarily have any large performance gains based on independent testing. You can read more on the web on independent testing that has been done. I've also seen products that that will keep Outlook sessions open for users. If we exceed limits on sessions that are set in Exchange automatically, you will see event IDs 9646 on the server. These events are another subject that I'll cover in a later blog post to follow. 4. Are the remote users using Outlook in Cached Exchange Mode? If not, can we place the user in Cached Mode as a troubleshooting step? Yes, this will download to ost the first time and may take a few minutes however this sort of scenario is what cached mode is designed for. 5. Network Card. Configurations and settings need to be confirmed. These steps are to be taken on the affected workstation. (Note: these instructions are for how to obtain the settings in Windows XP, but these settings should be checked for any OS):
- Are there any External DNS Servers listed in the Primary or Secondary DNS Entries?
- Is your Local Area Connection at the top of the binding order? Start > Control Panel > Network Connections > Advanced > Advanced Settings - Make sure the in the connections tab the Local Area Connection is on top. Click OK.
- What card is installed and what driver? Local Area Connection > Right Click > Properties > Select the Configure Button > Select the Driver Tab. What is the Date and Version?
- Now Select the Advanced tab > In the Property Window, is TCP Checksum Offloading enabled? Please see screen shot below. In this instance the value for Checksum Offloading is not set. It can be listed as any of the following:
RX Checksum Offloading TX Checksum Offloading TCP Checksum Offloading Alternatively, you can also disable this in the registry: 904946 You experience intermittent communication failure between computers that are running Windows XP or Windows Server 2003 http://support.microsoft.com/default.aspx?scid=kb;EN-US;904946Since a good portion of Outlook deployments are done via imaged builds, I check the following bindings and protocol registry keys to confirm they are correct: 6. Check the RPC Binding order on the Outlook Client: 163576 XGEN: Changing the RPC Binding Order http://support.microsoft.com/default.aspx?scid=kb;EN-US;163576 Here is what your registry key should look like:


Updated Jul 01, 2019
Version 2.0The_Exchange_Team
Microsoft
Joined April 19, 2019
Exchange Team Blog
You Had Me at EHLO.