Hello everyone Im facing a problem with Exchange Server 2007 Sp1 regarding Outlook Anywhere and RPC over HTTP transport. Symptons: - Outlook clients (2003 and 2007) never send or receive e-mail using Outlook Anywhere, keeps on Trying connection to Exchange Server - The connection status (right clicking Outlook icon) to HTTPS keeps as Connecting - Error 0x80040115 is showed after a long time - This behavior happens both internally (from local Exchanges network) and externally (Internet clients) - It also happens with all e-mail accounts in the Exchange organization The environment: - Using a certificate issued by the local Root CA (Active Directory) for the internal hostname of the Exchange Server. The certificate also contains Alternative Names for all hostnames needed, such as: autodiscover.domain.local, autodiscover.domain.com (external), owa.domain.local and owa.domain.com (for OWA, ActiveSync, RPC over HTTP and everything else). The root CA certificate was already imported by all Outlook Anywhere clients and its trusted, no error is presented. - OWA and ActiveSync works (send and receive) perfectly using the same URL of Outlook Anywhere both internally and externally - Autodiscover also works perfectly by right clicking Outlook taskbar icon and testing it - In Exchange Management Shell, TestOutlookWebServices also works perfectly (all SUCCESS), even for the RPC/HTTPS component - Rpcping successfully contacts the RPC server over HTTP from both internal and external clients - Outlook log (OPMLog) does not show any connection attempt when using Outlook Anywhere - The Rpc virtual directory is configured with: Basic authentication only, and to require SSL connections with 128 bit certificates. - Already tried reinstalling the RPC over HTTP Windows component. Actually, this was done several times without any success. - Also, already tried reinstalling the whole client access component of Exchange. Problem continued. - Also tried several permissive combinations of file security settings of c:\Windows\System32\Rpc\rpcproxy.dll, including Allow Everyone Full Control - Tried disabling IPV6 in registry (according to a few workarounds around the internet) and also by keeping it enabled and adding an internal ipv6. Same thing. Ive got completely out of ideas. Any other suggestion will be greatly appreciated. [PS] C:\Windows\System32>Test-OutlookWebServices Id Type Message -- ---- ------- 1003 Information Prestes a testar a Des... 1007 Information Testando servidor fs01... 1019 Information Encontrado um ponto de... 1006 Information O servio de Descobert... 1016 Success [EXCH]-Servio AS cont... 1015 Success [EXCH]-Servio OAB con... 1014 Success [EXCH]-Servio UM cont... 1016 Success [EXPR]-Servio AS cont... 1015 Success [EXPR]-Servio OAB con... 1014 Success [EXPR]-Servio UM cont... 1017 Success [EXPR]-Servio RPC/HTT... 1006 Success O servio de Descobert... [PS] C:\Windows\System32> [PS] C:\Windows\System32>Get-OutlookAnywhere ServerName : FS01 SSLOffloading : False ExternalHostname : owa.domain.com ClientAuthenticationMethod : Basic IISAuthenticationMethods : {Basic} MetabasePath : IIS://fs01.domain.local/W3SVC/1/ROOT/Rpc Path : C:\Windows\System32\RpcProxy Server : FS01 AdminDisplayName : ExchangeVersion : 0.1 (8.0.535.0) Name : Rpc (Owa - 80 e 443) DistinguishedName : CN=Rpc (Owa - 80 e 443),CN=HTTP,CN=Protocols,CN=FS 01,CN=Servers,CN=Exchange Administrative Group (FY DIBOHF23SPDLT),CN=Administrative Groups,CN=My Company,CN=Microsoft Exchange,CN=Services,CN=Config uration,DC=domain,DC=local Identity : FS01\Rpc (Owa - 80 e 443) Guid : a161c040-a191-4e4d-85ba-da2e5f5d7320 ObjectCategory : domain.local/Configuration/Schema/ms-Exch-Rp c-Http-Virtual-Directory ObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtual Directory} WhenChanged : 31/05/2009 23:16:06 WhenCreated : 31/05/2009 22:05:32 OriginatingServer : fs01.domain.local IsValid : True [PS] C:\Windows\System32> [PS] C:\Windows\System32>Get-OutlookProvider | fl CertPrincipalName : Server : TTL : 1 AdminDisplayName : ExchangeVersion : 0.1 (8.0.535.0) Name : EXCH DistinguishedName : CN=EXCH,CN=Outlook,CN=AutoDiscover,CN=Client Access,CN=My Company,CN=Microsoft Exchange,CN=Services,CN=Configuratio n,DC=domain,DC=local Identity : EXCH Guid : e5b0cc0b-1b10-4aaf-b191-1b05e08d7de1 ObjectCategory : domain.local/Configuration/Schema/ms-Exch-Auto-Discov er-Config ObjectClass : {top, msExchAutoDiscoverConfig} WhenChanged : 03/06/2009 09:39:58 WhenCreated : 12/05/2009 20:17:51 OriginatingServer : fs01.domain.local IsValid : True CertPrincipalName : Server : TTL : 1 AdminDisplayName : ExchangeVersion : 0.1 (8.0.535.0) Name : EXPR DistinguishedName : CN=EXPR,CN=Outlook,CN=AutoDiscover,CN=Client Access,CN=My Company,CN=Microsoft Exchange,CN=Services,CN=Configuratio n,DC=domain,DC=local Identity : EXPR Guid : cd00804b-30db-4946-aa2c-9b40b62067cc ObjectCategory : domain.local/Configuration/Schema/ms-Exch-Auto-Discov er-Config ObjectClass : {top, msExchAutoDiscoverConfig} WhenChanged : 03/06/2009 09:40:02 WhenCreated : 12/05/2009 20:17:51 OriginatingServer : fs01.domain.local IsValid : True CertPrincipalName : Server : TTL : 1 AdminDisplayName : ExchangeVersion : 0.1 (8.0.535.0) Name : WEB DistinguishedName : CN=WEB,CN=Outlook,CN=AutoDiscover,CN=Client Access,CN=My Company,CN=Microsoft Exchange,CN=Services,CN=Configuration ,DC=domain,DC=local Identity : WEB Guid : 56e3ef22-0319-49d0-a6ca-20ff45570cea ObjectCategory : domain.local/Configuration/Schema/ms-Exch-Auto-Discov er-Config ObjectClass : {top, msExchAutoDiscoverConfig} WhenChanged : 03/06/2009 10:16:17 WhenCreated : 12/05/2009 20:17:51 OriginatingServer : fs01.domain.local IsValid : True [PS] C:\Windows\System32>

Hi, Would you please let me know some basic information: 1. How many Exchange Servers are deployed? Whether the Client Access Server and Mailbox Server roles are installed on same server? 2. Whether GC Servers are installed on Mailbox Server or on a separate server? Please attempt the following method to troubleshoot the issue: 1. On the internal client, access following URL: https://owa.domain.com/rpc/rpcproxy.dll Please ensure no certificate related error is encountered and you should get blank page after providing credential 2. Please disable IPV6 according to following article: Outlook Anywhere Client Connectivity Issue Because of TCP/IPv6 http://technet.microsoft.com/en-us/library/cc671176.aspx 3. From your description, you have used the RPCPing to test the connectivity to RPC Proxy Server. I would like to know whether you have use RPCPing to tool to test the connectivity to back end Mailbox Server: Note: I suggest you run the tool on the CAS server to bypass firewall. How to use the RPC Ping utility to troubleshoot connectivity issues with the Exchange over the Internet feature in Outlook 2007 and in Outlook 2003 http://support.microsoft.com/kb/831051/en-us 4. From your description The connection status (right clicking Outlook icon) to HTTPS keeps as Connecting, would you please let me know the Server and Type the Outlook attempts to connect. Mike

Hey MikeThanks for your answer. Here it goes:1. Only one Exchange Server with everything installed on it, mailboxes, client access, etc.2. The Exchange Server is also the only DC in the network and it holds the GC role.Regarding the troubleshooting steps:1. The URL works (it get's blank) after asking for a domain username and password (basic auth is configured in IIS).2. Update rollups 4, 7 and 8 are installed on the server. The article mentions the procedure is not required with them. Also, this was something i've already tried in the past to solve the issue. BUT, i did it again anyway by following your adviseand the problem still persists.3. Rpcping works locally (from the CAS server)and even from external networks (crossing the firewall):C:\>rpcping -t ncacn_http -s fs01.domain.local -o RpcProxy=owa.domain.com -P "firstname.lastname,domain.local,*" -I "firstname.lastname,domain.local,*" -H 1 -u 10 -a connect -F 3 -v 3 -E -R noneRPCPing v2.12. Copyright (C) Microsoft Corporation, 2002OS Version is: 6.0, Service Pack 1Enter password for server:Enter password for RPC/HTTP proxy: RPCPinging proxy server owa.domain.com with Echo Request PacketSending ping to serverResponse from server received: 200Pinging successfully completed in 4634 ms4. The Connection Status box shows this:Server: Type: Con: Status:fs01.domain.local Public Folders TCP/IP Connectingfs01.domain.localEmail HTTPSConnectingfs01.domain.local Email --- ConnectingRegards,Rodrigo

Hi Rodrigo, Thanks for your response and detailed information. Regarding the RPCPing command, I would like to explain that if you use -E argument, this argument restricts the connectivity test to the RPC Proxy server only. It only means that the client is able to connect to RPC Proxy server. We need to use following commands to test the connectivity to Mailbox Server and GC: The port 6001 is listened by the Information Store Service: RpcPing t ncacn_http s ExchangeMBXServer o RpcProxy=RpcProxyServer P user,domain,password I user,domain,password H 1 F 3 a connect u 10 v 3 e 6001 The port 6002 is listened by DS Referral service RpcPing t ncacn_http s ExchangeMBXServer o RpcProxy=RpcProxyServer P user,domain,password I user,domain,password H 1 F 3 a connect u 10 v 3 e 6002 The port 6004 is listened by DS Proxy Service RpcPing t ncacn_http s ExchangeMBXServer o RpcProxy=RpcProxyServer P user,domain,password I user,domain,password H 1 F 3 a connect u 10 v 3 e 6004 Please let me know whether you can run above three commands with no error. In addition, for the Exchange Server which installed GC, you need to add following registry key: http://technet.microsoft.com/en-us/library/bb124159(EXCHG.65).aspx Mike

Hey MikeFor all services (IS, MBX and DS's) Rpcping kept waiting indefinitely, without any response or error after inputting the password. Rpcping was executed from the internal network. Only hitting ^C gave me the prompt back.C:\>rpcping -t ncacn_http -s fs01.domain.local -o RpcProxy=owa.domain.com -P "firstname.lastname,domain.local,*" -I "firstname.lastname,domain.local,*" -H 1 -F 3 -a connect -u 10 -v 3 -e 6001RPCPing v2.12. Copyright (C) Microsoft Corporation, 2002OS Version is: 6.0, Service Pack 1Enter password for server:Enter password for RPC/HTTP proxy:^CBy using Network Monitor from the workstation, i can see that there is SSL data being exchanged with the server. I can see the whole SSL negotiation, certificate exchange, one packet from the workstation to the server, another response back from the server and nothing more. Nada, not a single packet is sent toor received from the server.The setting regarding "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters\NSPI interface protocol sequences" was already there.Odd.Rodrigo

Hi Rodrigo, 1. I would like to know whether you run the RPCPing tool on the Exchange CAS server directly to test the issue. 2. In addition, please run following command to check whether the ports are listened: netstat -ano |findstr 6001 netstat -ano |findstr 6002 netstat -ano |findstr 6004 If all the three ports are listened, please use tasklist |findstr proccesid command to check whether correct process listened the ports. The store.exe should listen the 6001 port. The lsass.exe process should listen the 6002 port. The mad.exe process should listen the 6004 port. In addition, both IPv4 and IPv6 ports should be listened. 3. Please check whether the valid ports registry key is configured correctly: HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy\ValidPorts The validports key contains all the servers/ports that RPCProxy is allowed to talk to. You should get the key like below: mbx1:6001-6002;mbx1:6004;mbx1.contoso.com:6001-6002;mbx1.contoso.com:6004 For more information: How does Outlook Anywhere work (and not work)? http://msexchangeteam.com/archive/2008/06/20/449053.aspx Mike

Mike1. Yes, i did. Same behavior:C:\>rpcping -t ncacn_http -s fs01.domain.local -o RpcProxy=owa.domain.com -P "firstname.lastname,domain.local,*" -I "firstname.lastname,domain.local,*" -H 1 -F 3 -a connect -u 10 -v 3 -e 6001RPCPing v6.0. Copyright (C) Microsoft Corporation, 2002-2006Digite a senha para server:Digite a senha para RPC/HTTP proxy: (I'm sorry the server language is Brazilian Portuguese) 8-S 2. The output of netstatC:\Users\Administrador>netstat -ano |findstr 6001 TCP 0.0.0.0:6001 0.0.0.0:0 LISTENING 216 TCP 192.168.0.2:6001 192.168.0.2:46985 ESTABLISHED 216 TCP 192.168.0.2:46985 192.168.0.2:6001 ESTABLISHED 5528 TCP [::]:6001 [::]:0 LISTENING 216 C:\Users\Administrador>netstat -ano |findstr 6002 TCP 0.0.0.0:6002 0.0.0.0:0 LISTENING 1308 TCP [::]:6002 [::]:0 LISTENING 1308 C:\Users\Administrador>netstat -ano |findstr 6004 TCP 0.0.0.0:6004 0.0.0.0:0 LISTENING 524 TCP [::]:6004 [::]:0 LISTENING 524 C:\Users\Administrador>C:\Users\Administrador>tasklist |findstr 216store.exe 216 Services 0 67.896 Kmsdtc.exe 5216 Services 0 8.920 K C:\Users\Administrador>tasklist |findstr 5528w3wp.exe 5528 Services 0 19.132 K C:\Users\Administrador>tasklist |findstr 1308mad.exe 1308 Services 0 24.580 K C:\Users\Administrador>tasklist |findstr 524lsass.exe 524 Services 0 39.792 K C:\Users\Administrador>Looks like there is something wrong here, right? According to your last post, lsass should be listening on port 6002 and mad on 6004. What i have is exactly the opposite: lsass on 6004 and mad on 6002.3. My valid ports are:FS01:6001-6002;FS01:6004;fs01.domain.local:6001-6002;fs01.domain.local:6004They are all referring the internal DNS domain name (domain.local) and not the external (domain.com), which is the one configured in Outlook Anywhere clients: https://owa.domain.com. Would that be correct?Rodrigo

And another piece of information:rpcping does not actually hangs, after a really looooong time it shows this error:Exception 1818 (0x0000071A)Number of records is: 1ProcessID is 5264System Time is: 6/19/2009 16:59:24:29Generating component is 14Status is 1818Detection location is 1390Flags is 0NumberOfParameters is 1Long val: 900000Rodrigo

And another info... I guess this problem is related to something inside IIS6. This (Outlook Anywhere) actually worked when i've installed Windows 2008 and Exchange from scratch (a few months ago). I mean, everything worked fine with the Default Web Site. Obviously, at that time nothing was configured or customized inside Exchange (hostnames, certificates, etc.). Also, the IIS configuration had to be changed due to the implementation of a Sharepoint server: i had to remove the Default Web Site (because everything was configured on it, Owa, Rpc, Sharepoint, etc.) and create specific websites for Owa (plus Rpc, Activesync, and everything related to Exchange) and Sharepoint. Maybe something was missing during this splitting process. Rodrigo

Hi Rodrigo, Thanks for your response and detailed information. 2. I would like to explain the lsass.exe process should listen to port 6004 and the mad.exe process should listen to port 6002. Therefore, your situation is correct. Sorry for my typing error in previous post. 3. Yes, the Valid Ports registry key is configured correctly. At this time, please let me know: 1. Whether 1818 error only occurs when ping the 6001 (Information Store) or all the ports (6001, 6002 and 6004) 2. If you telnet to the 6001, 6002 and 6004 from the CAS server, whether you are able to get a response like ncacn_http/1.0 3. Please enable IIS log and httper log on the CAS server, when running RPCPing command, you should get information like below in IIS log: 2009-06-22 07:47:57 W3SVC1 192.168.1.1 RPC_IN_DATA /rpc/rpcproxy.dll mb.lab.com:6001 443 lab\administrator 192.168.1.7 MSRPC 200 0 64 2009-06-22 07:47:57 W3SVC1 192.168.1.1 RPC_OUT_DATA /rpc/rpcproxy.dll mb.lab.com:6001 443 lab\administrator 192.168.1.7 MSRPC 200 0 64 If any other error is received, please post the result here. Mike

Hey Mike1. It occurs with all three ports. Same error, always.2. Yes, it works with all three ports. I'm getting "ncacn_http/1.0" as a response for telnet sessions initiated from both the CAS server and externally (!).3. Ok. Here is the log:#Software: Microsoft Internet Information Services 7.0#Version: 1.0#Date: 2009-06-19 16:25:12#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status time-taken2009-06-19 16:25:12 192.168.0.2 POST /EWS/Exchange.asmx SoapAction=GetUserOofSettingsResponse;MailboxRPCRequests=17;MailboxRPCLatency=35;ADRequests=6;ADLatency=31;TimeInGetUserOOFSettings=1004; 443 DOMAIN\firstname.lastname 192.168.0.61 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6425;+Pro) 200 0 0 85632009-06-19 16:26:25 192.168.0.2 RPC_IN_DATA /rpc/rpcproxy.dll fs01.domain.local:6001 443 - 192.168.0.2 MSRPC 404 13 0 12372009-06-19 16:34:13 192.168.0.2 POST /EWS/Exchange.asmx SoapAction=GetUserOofSettingsResponse;MailboxRPCRequests=10;MailboxRPCLatency=12;ADRequests=3;ADLatency=16;TimeInGetUserOOFSettings=30; 443 DOMAIN\firstname.lastname192.168.0.61 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6425;+Pro) 200 0 0 332009-06-19 16:44:41 192.168.0.2 RPC_IN_DATA /rpc/rpcproxy.dll fs01.domain.local:6001 443 - 192.168.0.61 MSRPC 404 13 0 122009-06-19 16:44:41 192.168.0.2 RPC_OUT_DATA /rpc/rpcproxy.dll fs01.domain.local:6001 443 domain.local\firstname.lastname 192.168.0.61 MSRPC 401 1 64 922009-06-19 16:44:52 192.168.0.2 RPC_IN_DATA /rpc/rpcproxy.dll fs01.domain.local:6001 443 - 192.168.0.61 MSRPC 404 13 0 102009-06-19 16:44:52 192.168.0.2 RPC_OUT_DATA /rpc/rpcproxy.dll fs01.domain.local:6001 443 domain.local\firstname.lastname 192.168.0.61 MSRPC 401 1 64 882009-06-19 16:44:59 192.168.0.2 RPC_IN_DATA /rpc/rpcproxy.dll fs01.domain.local:6001 443 - 192.168.0.61 MSRPC 404 13 0 102009-06-19 16:46:53 192.168.0.2 POST /Autodiscover/Autodiscover.xml - 443 - 192.168.0.51 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6425;+Pro) 401 2 5 4212009-06-19 16:46:57 192.168.0.2 POST /EWS/Exchange.asmx - 443 - 192.168.0.51 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6425;+Pro) 401 2 5 92009-06-19 16:47:00 192.168.0.2 GET /OAB/3fb23fd4-0675-45fd-a951-83d17d2e5940/oab.xml - 443 - 192.168.0.51 Microsoft+BITS/7.0 401 2 5 422009-06-19 16:47:07 192.168.0.2 GET /OAB/3fb23fd4-0675-45fd-a951-83d17d2e5940/oab.xml - 443 - 192.168.0.51 Microsoft+BITS/7.0 401 2 5 12009-06-19 17:04:12 192.168.0.2 POST /EWS/Exchange.asmx SoapAction=GetUserOofSettingsResponse;MailboxRPCRequests=10;MailboxRPCLatency=16;ADRequests=3;ADLatency=16;TimeInGetUserOOFSettings=34; 443 DOMAIN\firstname.lastname 192.168.0.61 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6425;+Pro) 200 0 0 382009-06-19 17:05:12 192.168.0.2 POST /autodiscover/autodiscover.xml - 443 DOMAIN\firstname.lastname 192.168.0.61 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6425;+Pro) 200 0 0 152009-06-19 17:17:16 192.168.0.2 GET /OAB/3fb23fd4-0675-45fd-a951-83d17d2e5940/oab.xml - 443 - 192.168.0.51 Microsoft+BITS/7.0 401 2 5 282009-06-19 17:17:18 192.168.0.2 GET /OAB/3fb23fd4-0675-45fd-a951-83d17d2e5940/oab.xml - 443 - 192.168.0.51 Microsoft+BITS/7.0 401 2 5 2Rodrigo

Something is definitely not right:2009-06-19 16:44:41 192.168.0.2 RPC_IN_DATA /rpc/rpcproxy.dll fs01.domain.local:6001 443 - 192.168.0.61 MSRPC 404 13 0 122009-06-19 16:44:41 192.168.0.2 RPC_OUT_DATA /rpc/rpcproxy.dll fs01.domain.local:6001 443 domain.local\firstname.lastname 192.168.0.61 MSRPC 401 1 64 92For RPC_IN i'm getting 404.13, "Content Too Large", is that correct?And for RPC_OUT i'm getting 401.1, "Unauthorized". Invalid credentials, whaaaat???Rodrigo

FOUND THE ERROR.Thanks a lot Mike for pointing me to the IIS logs. I've found this page after searching for the 404.13 error: http://exchangets.fr/spip.php?article10My applicationHost.config did not have this:requestLimits maxAllowedContentLength="2147483648"Now, rpcping works like a charm: C:\>rpcping -t ncacn_http -s fs01.domain.local -o RpcProxy=owa.domain.com -P "user,domain.local,*" -I "user,domain.local,*" -H 1 -u 10 -a connect -F 3 -v 3 -e 6001 RPCPing v2.12. Copyright (C) Microsoft Corporation, 2002 OS Version is: 6.0, Service Pack 1 Enter password for server:Enter password for RPC/HTTP proxy:Completed 1 calls in 484 ms 2 T/S or 484.000 ms/TCheers,Rodrigo

Hi Rodrigo, Thanks for your response. I am glad to know the RPCPing issue could be solved by referring to KB942074. At this time, please let me know whether the Outlook Anywhere works on the internal client. If Outlook Anywhere works in internal client, please go ahead and check whether it works on external clients. Mike

Hey MikeYes, Outlook Anywhere now works both internally and externally. Thanks.Please allow to me to discuss KB942074 a bit:the Resolution topic mentions this as step 4:4. Remove the maxAllowedContentLength property. Or, add a value that matches the size of the Content-Length header that the client sends as part of the request. By default, the value of the maxAllowedContentLength property is 30000000. Actually, the KB seem to be wrong in some way. By following the instruction toRemove the maxAllowedContentLength property i would have exactly the same situation as before, where RPC over HTTP was not working. My IIS7 applicationhost.config did not have any reference to this maxAllowedContentLenght statement before a manual intervention.And another thing, therewas some situation in IIS that probably created the problem with RPC. I remember doing these things in the past:- Installing Windows Sharepoint Services 3- Moving Sharepoint to specific IIS websites (removing from Default Web Site)- Removing all Exchange virtual directories- Creating a specific website for OWA and all other Exchange components (Activesync, Autodiscover, etc.) and including RPC virtual directories- Uninstalling and reinstalling both Exchange CAS and Windows RPC over HTTP- Uninstalling and reinstalling the whole Application Server (IIS7)- Doing those things over and over again not necessarily in that order(...and expecting different results - which is the proper definiton of crazyness :-))Someway, somehow the maxAllowedContentLenght got lost in the middle of all of that. Outlook Anywhere worked out-of-the-box, with a brand new Exchange installation on this same server. But problems started when i needed to split things (Exchange and Sharepoint) in different websites and remove the Default Web Site.Rodrigo

<requestFiltering><requestLimits maxAllowedContentLength="2147483648" /></requestFiltering>This works for me.For some reason i do not have that in my applicationHost.config file.After adding that lines rpcping works fine.Thanks a lot RoFz .You saved me :)