none
Test-OWAConnectivity fails- cannot find InternalURL Property

    Question

  • Despite the fact that I have already set the OWA Virtual Directory InternalURL both via GUI and via CLI it cannot find it for some reason. This error is coming up on a number of cmdlets like Test-CalendarConnectivity as well. I am the domain admin user FYI.

    PS C:\Users\ops> Get-OwaVirtualDirectory -Server NYCMail01 | Select InternalURL
    InternalUrl
    https://nycmail01.mycompany.net/owa

    PS C:\Users\ops> Test-OwaConnectivity
    WARNING: The test couldn't test the internal URL of this virtual directory, because the InternalURL property isn't set.

    CasServer  LocalSite     Scenario        Result  Latency(MS) Error
    ---------  ---------     --------        ------  ----------- -----
    NYCMAIL01  NY-Site       Logon           Skipped             The test couldn't test
                                                                 the internal URL of
                                                                 this virtual directory,
                                                                 because the InternalURL
                                                                 property isn't set.
    Test-OwaConnectivity : The Service Endpoint "ExchangeLoginUrl" was not found. This Endpoint gets created during setup,
    but it has been deleted.
    At line:1 char:1
    + Test-OwaConnectivity
    + ~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [Test-OwaConnectivity], ServiceEndpointNotFoundException
        + FullyQualifiedErrorId : 75120715,Microsoft.Exchange.Monitoring.TestOwaConnectivity

    In addition I could not find any record of "ExchangeLoginURL" whatsoever when searching google/bing.

    Any help would be appreciated.

    -John


    • Edited by jkmancuso Monday, July 29, 2013 7:42 PM
    Monday, July 29, 2013 7:35 PM

Answers

  • It is causing our monitoring to fail so it's pretty important for this to work. Test-CalendarConnectivity is failing as well and is not deprecated.

    I have contacted MSFT support and they are having the exact same issue on their side with these cmdlets on Exchange 2013 CU1. Also the issue exists on CU2 as well. Update to follow...



    Wednesday, July 31, 2013 6:47 PM

All replies

  • Can you browse it from IIS on your Exchange server(default site - owa)?Try with http and https.

    You mentioned internally,so external works fine?

    Monday, July 29, 2013 10:02 PM
  • Yes, on https.

    no, on http.

    This is expected behavior I believe. Also i can view owa just fine from my local machine as well. Have not started working on the external portion yet.

    The problem is the powershell checks are failing because of this and also I believe this InternalURL issue may cause a larger problem later so I do not want to dismiss this just because owa appears to be working.

    Monday, July 29, 2013 11:18 PM
  • Anyone have any thoughts on this error?
    Tuesday, July 30, 2013 11:15 AM
  • Hi John,

    From your description, we know that you have already set the OWA Virtual Directory InternalURL. However, the result of Test-OwaConnectivity cmdlet occurs warning” the InternalURL property isn't set.”

    OWA (Default Web Site) properties which contain InternalURL property are stored in the Configuration partition of AD. There can be several DCs in the domain. It may be the information synchronization between DCs that results this problem.

    With my consideration, we can try the following steps to solve it:

    • Try to restart IIS service by running iisreset /noforce from a command prompt window.
    • Use Test-OwaConnectivity cmdlet in the following format (force to save the configuration to one specific DC):

    Test-OwaConnectivity -ClientAccessServer: NYCMail01 DomainController XXXX

    Hope it can help you.

    Best regards

    Tuesday, July 30, 2013 1:38 PM
  • 1. I have restarted IIS and restarted the box. No luck.

    2. I have tried the following command with each Domain Controller but no luck there as well.

    Test-OwaConnectivity -ClientAccessServer: NYCMail01 DomainController NYCDC01

    3. Also I checked the AD schema:

    dn: CN=owa (Default Web Site),CN=HTTP,CN=Protocols,CN=NYCMAIL01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=MyCompany,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mycompany,DC=net

    Attribute: msExchInternalHostName, Value: https://nycmail01.mycompany.net/owa

    Is this perhaps a known bug in 2013 CU1?

    Tuesday, July 30, 2013 3:04 PM
  • Is there any user impact ?

    From your responds, it concludes that it’s not IIS error. And your OWA configuration in AD is complete. In other words, the Internal URL has taken effect and you can use it.

    In Exchange 2013, the Test-OwaConnectivity cmdlet has been deprecated and will be removed from a future release. For more information, you can click the following link:

    http://technet.microsoft.com/en-us/library/aa997682.aspx

    John, since we can find the internal url properly in ADSIEDT, I think the InternalURL setting has taken effect. We can feel free to ignore the report by test-OWAconnectivity.

    Thanks


    • Edited by winni_days Wednesday, July 31, 2013 12:34 PM
    Wednesday, July 31, 2013 12:33 PM
  • It is causing our monitoring to fail so it's pretty important for this to work. Test-CalendarConnectivity is failing as well and is not deprecated.

    I have contacted MSFT support and they are having the exact same issue on their side with these cmdlets on Exchange 2013 CU1. Also the issue exists on CU2 as well. Update to follow...



    Wednesday, July 31, 2013 6:47 PM