Article ID: 919092 - View products that this article applies to.
In a Microsoft Exchange Server organization, Microsoft Office Outlook 2003 users receive the following error message when the users connect to an Exchange server by using RPC over HTTP:
Additionally, the following errors are logged in the Internet Information Services (IIS) logs on the RPC proxy server:
Date Time IP Address RPC_IN_DATA /rpc/rpcproxy.dll FQDN.companyname.com:6002 443 domain\username IP Address MSRPC 404 2 1260 Date Time IP Address RPC_OUT_DATA /rpc/rpcproxy.dll FQDN.companyname.com:6002 443 domain\username IP Address MSRPC 404 2 1260
This problem occurs if the RPC proxy server extensions do not load correctly.
To resolve this problem, use one of the following methods:
Method 1:Use the Exchange Remote Connectivity Analyzer to help diagnose and resolve client connectivity issues.
Exchange Remote Connectivity Analyzer is a Web-based troubleshooting and diagnostic tool that helps identify the point of failure for Internet-based Exchange Server client connectivity scenarios. The tool simulates all the activities a client must perform to connect, and then isolate the exact point of failure. In many cases, it points out known configuration issues and provide suggested steps for resolution. The connectivity testing across the Internet from outside your organization is performed by a Web site hosted in a Microsoft datacenter. To use this tool, visit the following Web site:
Method 2: Try to resolve the issue manually by completing the steps
You can verify in IIS Manager that the path of the Rpcproxy.dll file is valid. Additionally, verify that the file is located in the correct path and that the file is registered correctly. To do this, follow these steps.
Step 1: Verify the location of the Rpcproxy.dll file
Step 2: Verify the registered path in IIS Manager
Step 3: Replace and register the Rpcproxy.dll fileIf you receive the error message that is mentioned in the "Symptoms" section, the Rpcproxy.dll file may be corrupted. Or, the Rpcproxy.dll file may not be registered correctly. This problem may occur even though the path is specified correctly in the properties of the RPC proxy server extension object. To resolve this problem, follow these steps:
Article ID: 919092 - Last Review: August 28, 2013 - Revision: 2.0