Share via

Get-OwaVirtualDirectory failed with error "The task wasn't able to connect to IIS on the server"

  • Article

Question

Monday, October 29, 2018 6:44 AM

Hi,

In our exchange enviroment ,we are unable to perform OWAVirtualDirectory operations. Whenever we try to do  any changes using set-OWAVirtualDirectory powershell command, it got failed with below error. We also tried to change same configuration using Outlook Web Access which also failed with same error. Our version of Exchange server  is Exchange 2013 CU20. Kind request and support to resolve the issue.

[PS] C:\Windows\system32>Get-OwaVirtualDirectory
The task wasn't able to connect to IIS on the server 'exchangecas.tld.domain'. Make sure that the server exists
and can be reached from this computer: The RPC server is unavailable.
    + CategoryInfo          : ReadError: (EXCHANGECAS\owa (Default Web Site):ADObjectId) [Get-OwaVirtualDirectory], II
   SNotReachableException
    + FullyQualifiedErrorId : [Server=MAILBOX1,RequestId=69f10a03-f0b8-48a7-91c6-93a2565efc73,TimeStamp=10/29/2018 6:3
   3:40 AM] [FailureCategory=Cmdlet-IISNotReachableException] E891A3C8,Microsoft.Exchange.Management.SystemConfigurat
  ionTasks.GetOwaVirtualDirectory
    + PSComputerName        : exchangecas.tld.domain

Regards

Ashraf

Ashraf

All replies (2)

Monday, October 29, 2018 11:31 AM âś…Answered

To resolve this issue

  1. Open IIS on the CAS server
  2. Navigate to the PowerShell virtual directory
  3. Select "Advanced Settings" from the Actions pane on the right.
  4. Change the Physical Path settings from"D:\ExchangeServer\V15\FrontEnd\HttpProxy\PowerShell" to "D:\ExchangeServer\V15\ClientAccess\PowerShell" (or what ever directory your exchange installation is in)
  5. Run IISRESET

This was the same on all my CAS servers, and even after reinstalling Windows and Exchange, the physicla path was still set to "D:\ExchangeServer\V15\FrontEnd\HttpProxy\PowerShell" instead of "D:\ExchangeServer\V15\ClientAccess\PowerShell" and I needed to change it.

Helpful link: https://support.microsoft.com/en-us/help/2778897/cannot-access-outlook-on-the-web-or-the-eac-after-you-re-create-the-ow

Best Regards,

Rafiul

Mark if this post is helpful

Monday, October 29, 2018 12:11 PM

Great help

Thanks

The below steps fixed Get-OwaVirtualDirectory in the powershell. But in the Outlook Web Access getting the same error. How can sort it out.

change the Physical Path settings from"D:\ExchangeServer\V15\FrontEnd\HttpProxy\PowerShell" to "D:\ExchangeServer\V15\ClientAccess\PowerShell" (or what ever directory your exchange installation is in)

Ashraf