This topic is among a series of steps to help you troubleshoot an unsuccessful RPC over HTTP connection. This article explains how to verify that the RPC Proxy Server Extension is loading properly.
If Outlook clients experience connection problems after you configure all the required settings for RPC over HTTP on the server side, it may be because theÂ RPC Proxy Server Extension is not loading correctly. When clients experience this kind of connection problem in Outlook, they receive an error message that is similar to the following:
To verify that the RPC Proxy Server Extension is Loading Properly
- On the Exchange Server, clickÂ Start, point toÂ Administrative Tools, and then clickÂ Internet Information Services (IIS) Manager on your RPC proxy server.
- Under the icon for your RPC proxy server, clickÂ Web Service Extensions.
- In the right pane, clickÂ RPC Proxy Server Extension, and then clickÂ Properties.
- Confirm that the path of theÂ Rpcproxy.dll file is correct. The correct location is the following:
For example, the correct location could be the following:
Examine the path entry carefully because it could be incorrectly set to the following:
For example, the current location could be set to the following:
This incorrect path can appear to be correct at a quick glance.
Additionally, if you experience this issue, the following 404 error is logged in the IIS log on your RPC proxy server:
2004-01-01 13:13:31 220.127.116.11 RPC_IN_DATA /rpc/rpcproxy.dll FQDN.company.com:6002 443 domain\username 18.104.22.168 MSRPC 404 2 1260