The 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.
Exchange Server 2007, Microsoft, Exchange 2007, Otullok, RPC, Troubleshooting, Knowledgebase, Tips, Tricks