PascalLavallee
asked on
Exchange 2003/2010 coexistence: Outlook Anywhere test fails with RPC_S_SERVER_UNAVAILABLE error
Hi,
We are running an Exchange 2003/2010 environment with one back-end EX2003 and one CAS/HUB/MBX 2010 server. I created a new mailbox on EX2010. when I run ExRCA Outlook Anywhere (RPC over HTTP) for the EX2010 mailbox user and specifiy the server settings manually, the test fails with the following error:
Attempting to ping RPC endpoint 6001 (Exchange Information Store) on server server.domain.com. The attempt to ping the endpoint failed.
Additional Details
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
I confirmed I can telnet server from the LAN to port 6001,6002 & 6004.
Do you have any suggestions?
PL
We are running an Exchange 2003/2010 environment with one back-end EX2003 and one CAS/HUB/MBX 2010 server. I created a new mailbox on EX2010. when I run ExRCA Outlook Anywhere (RPC over HTTP) for the EX2010 mailbox user and specifiy the server settings manually, the test fails with the following error:
Attempting to ping RPC endpoint 6001 (Exchange Information Store) on server server.domain.com. The attempt to ping the endpoint failed.
Additional Details
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
I confirmed I can telnet server from the LAN to port 6001,6002 & 6004.
Do you have any suggestions?
PL
ASKER
Thank you demazter for your comment.
As it turns out, the RPC Proxy was not responding because the FQDN was missing from the ValidPorts_Auto_Exchange registry entry (under HKLM\Software\Microsoft\Rp c\RpcProxy ). I added mail.domain.com:6001-6002; mail.domai n.com:6004 to the list and it works.
My problem now is that the registry entry reverses back to what it was a few minutes earlier and breaks RPC Proxy. I'm sure I'm missing something about Windows 2008 R2 security here. How can I make my registry entry change stick?
As it turns out, the RPC Proxy was not responding because the FQDN was missing from the ValidPorts_Auto_Exchange registry entry (under HKLM\Software\Microsoft\Rp
My problem now is that the registry entry reverses back to what it was a few minutes earlier and breaks RPC Proxy. I'm sure I'm missing something about Windows 2008 R2 security here. How can I make my registry entry change stick?
There is no reason why you should have to add this manually!
If exchange isn't configured correctly this tells me it either hasn't been insatalled properly or there are pre-requisites missing.
Exchange works out of the box, I have done hundreds of instals and never had to make manual registry changes to make it work.
There is a reason there is a procedure and process for installing these products.
If exchange isn't configured correctly this tells me it either hasn't been insatalled properly or there are pre-requisites missing.
Exchange works out of the box, I have done hundreds of instals and never had to make manual registry changes to make it work.
There is a reason there is a procedure and process for installing these products.
ASKER
I used Microsoft Exchange Pre-Deployment Analyzer and Microsoft Exchange Server Deployment Assistant. I selected a Custom install and followed Microsoft recommendations. I configured split DNS and internal/external URLs with the Exchange Management Shell.
I used Microsoft Exchange Best Practices Analyzer to fix one issue with a connector.
I'm not sure why the RPC over HTTP is giving me trouble but the registry fix was actually suggested by ExRCA (although the link applies to Ex2003 it did not work until I updated the 2008 registry entry)
http://technet.microsoft.com/en-us/library/dd439392(EXCHG.80).aspx
I'm glad you never had problems with the RPC over HTTP in your hundreds of instals.
Would you know how to make this work? RPC is not responding because ExRCA is trying by using mail.domain.com and RPC is only listing SERVER & SERVER.DOMAIN.INTERNAL on its port list.
I used Microsoft Exchange Best Practices Analyzer to fix one issue with a connector.
I'm not sure why the RPC over HTTP is giving me trouble but the registry fix was actually suggested by ExRCA (although the link applies to Ex2003 it did not work until I updated the 2008 registry entry)
http://technet.microsoft.com/en-us/library/dd439392(EXCHG.80).aspx
I'm glad you never had problems with the RPC over HTTP in your hundreds of instals.
Would you know how to make this work? RPC is not responding because ExRCA is trying by using mail.domain.com and RPC is only listing SERVER & SERVER.DOMAIN.INTERNAL on its port list.
Right click on the server in Exchange Management Consol under Server configuration. Select properties. Under Outlook Anywhere what URL do you have defined?
ASKER
mail.domain.com
ASKER
This is what a get-outlookanywhere | fl shows:
RunspaceId : 89349ebf-67c8-4cc9-90c1-e6 82d4dbc33a
ServerName : server
SSLOffloading : False
ExternalHostname : mail.domain.com
ClientAuthenticationMethod : Basic
IISAuthenticationMethods : {Basic}
XropUrl :
MetabasePath : IIS://server.domain.intern al/W3SVC/1 /ROOT/Rpc
Path : C:\Windows\System32\RpcPro xy
ExtendedProtectionTokenChe cking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
Server : server
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
Name : Rpc (Default Web Site)
DistinguishedName : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols ,CN=server ,CN=Server s,CN=Excha nge Admin
istrative Group (FYDIBOHF23SPDLT),CN=Admin istrative Groups,CN=domain Partners,CN=M
icrosoft Exchange,CN=Services,CN=Co nfiguratio n,DC=domai n,DC=inter nal
Identity : server\Rpc (Default Web Site)
Guid : 3b78aa2e-d5d8-453c-a7be-21 34446fbad8
ObjectCategory : domain.internal/Configurat ion/Schema /ms-Exch-R pc-Http-Vi rtual-Dire ctory
ObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirect ory}
WhenChanged : 3/21/2011 1:54:21 PM
WhenCreated : 3/19/2011 7:03:31 AM
WhenChangedUTC : 3/21/2011 6:54:21 PM
WhenCreatedUTC : 3/19/2011 12:03:31 PM
OrganizationId :
OriginatingServer : server.domain.internal
IsValid : True
RunspaceId : 89349ebf-67c8-4cc9-90c1-e6
ServerName : server
SSLOffloading : False
ExternalHostname : mail.domain.com
ClientAuthenticationMethod
IISAuthenticationMethods : {Basic}
XropUrl :
MetabasePath : IIS://server.domain.intern
Path : C:\Windows\System32\RpcPro
ExtendedProtectionTokenChe
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
Server : server
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
Name : Rpc (Default Web Site)
DistinguishedName : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols
istrative Group (FYDIBOHF23SPDLT),CN=Admin
icrosoft Exchange,CN=Services,CN=Co
Identity : server\Rpc (Default Web Site)
Guid : 3b78aa2e-d5d8-453c-a7be-21
ObjectCategory : domain.internal/Configurat
ObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirect
WhenChanged : 3/21/2011 1:54:21 PM
WhenCreated : 3/19/2011 7:03:31 AM
WhenChangedUTC : 3/21/2011 6:54:21 PM
WhenCreatedUTC : 3/19/2011 12:03:31 PM
OrganizationId :
OriginatingServer : server.domain.internal
IsValid : True
ASKER
Any more comments from the experts?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Also if in a co-existence you should really have a separate CAS only server.