Hi everyone,

I am currently experiencing issues when running the HCW, which throws the following error at the very end:

[02/06/2015 15:09:21]    INFO : Task='Configure MRS Proxy Settings' Step='NeedsConfiguration' START
[02/06/2015 15:09:21]    INFO : Session=OnPrem Cmdlet=Get-WebServicesVirtualDirectory START
[02/06/2015 20:19:07]   ERROR : System.Management.Automation.RemoteException: An IIS directory entry couldn't be created. The error message is The remote procedure call failed.
                                . HResult = -2147023170
[02/06/2015 20:19:07]    INFO : Session=OnPrem Cmdlet=Get-WebServicesVirtualDirectory FINISH Time=18586211.3298ms
[02/06/2015 20:19:07]   ERROR : Subtask NeedsConfiguration execution failed: Configure MRS Proxy Settings
                                Execution of the Get-WebServicesVirtualDirectory cmdlet has thrown an exception. This may indicate invalid parameters in your hybrid configuration settings.
                                An IIS directory entry couldn't be created. The error message is The remote procedure call failed.
                                . HResult = -2147023170
                                   at Microsoft.Exchange.Management.Hybrid.RemotePowershellSession.RunCommand(String cmdlet, SessionParameters parameters, Boolean ignoreNotFoundErrors)
[02/06/2015 20:19:07]    INFO : Task='Configure MRS Proxy Settings' Step='NeedsConfiguration' FINISH Result=False Time=18586211.3298ms

We currently have a deployment of Exchange 2007 and 2013 servers across the world (coexistence between the two is working fine). At the moment, I am trying to configure 3 Exchange 2013 servers in London as our Hybrid servers (these servers are multi-role and also host users mailboxes).

Manually running Get-WebServicesVirtualDirectory takes ages to run as it is normal in global deployments.

Initially, Exchange 2007 servers were not members of the Exchange Trusted Subsystem group (http://support.microsoft.com/kb/2995725/en-us). However, after fixing this, the issue remains.

All requirements for hybrid are in place (certificate, virtual directories on the hybrid servers are configured correctly and available externally, DNS, etc). I ran the Hybrid Configuration Diagnostic tool but none of the warnings are relevant for this.

Any help is much appreciated! Thank you so much.

Best regards,
Nuno

Hi Nuno,

According to your description, I know that it returns error "An IIS directory entry couldn't be created. The error message is The remote procedure call failed.HResult = -2147023170" when you run Get-WebServicesVirtualDirectory cmdlet in Exchange 2007 and 2013 coexistence.

I have saw a customer have the same issue, and he fix this by re-building EWS Virtural Directory. I suggest try to re-build the EWS VD for testing.

Thanks

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

Hi,

Any update?

Thanks

Hi Mavis,

Apologies for the delay in replying to you...

Recreating the EWS VD didn't help I'm afraid. However, I think I might have found out what is causing this cmdlet to take so long to run. Basically, every time I run a Get-WebServicesVirtualDirectory or a Get-OwaVirtualDirectory, for example, I get the following error:

DCOM was unable to communicate with the computer <server>.domain.local using any of the configured protocols; requested by PID     3cc8 (c:\windows\system32\inetsrv\w3wp.exe).

I do get the data from the cmdlets back, but receive this error every time. I think this is what is causing the cmdlets to take ages to run, which is probably causing the Hybrid wizard to fail. Another error I am now getting is:

ERROR : Subtask Configure execution failed: Configure MRS Proxy Settings
                                Execution of the Get-WebServicesVirtualDirectory cmdlet has thrown an exception. This may indicate invalid parameters in your hybrid configuration settings.
                                Processing data from remote server <server> failed with the following error message: <s:Envelope xml:lang="en-GB" xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:x="http://schemas.xmlsoap.org/ws/2004/09/transfer" xmlns:e="http://schemas.xmlsoap.org/ws/2004/08/eventing" xmlns:n="http://schemas.xmlsoap.org/ws/2004/09/enumeration" xmlns:w="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd" xmlns:p="http://schemas.dmtf.org/wbem/wsman/1/wsman/fault">http://schemas.microsoft.com/wbem/wsman/1/wsman.xsd"><s:Header><a:Action>http://schemas.dmtf.org/wbem/wsman/1/wsman/fault

I have spent hours troubleshooting these DCOM errors but have gone nowhere!... Firewalls are disabled, DCOM is enabled in all servers, all appears to be fine!

Any ideas anyone? Thank you once again.

Best regards,

Nuno

Hi Nuno,

I notice that you said, everything works fine except getting this error message.

Please try to restart IIS Admin Service.

Thanks