D'arcy Delorey
asked on
Outlook Autodiscover Failing for Single User
Outlook Autodisover is failing for a single user in our domain, Outlook won't resolve the server to connect.
If I run the following powershell command here is what I get:
Test-OutlookWebServices -Identity User@domain.com -MailboxCredential (get-credential)
Source ServiceEndpoint Scenario Result Latency
(MS)
------ --------------- -------- ------ -------
SRVEX13.domain.com autodiscover.domain.com Autodiscover: Outlook Provider Failure 159
SRVEX13.domain.com Exchange Web Services Skipped 0
SRVEX13.domain.com Availability Service Skipped 0
SRVEX13.domain.com Offline Address Book Skipped 0
If I run it against other users, I get success across the board.
Full Error is here:
RunspaceId : 2661e5f6-6ad2-4204-bd5a-4d d5ce92a4c5
Source : SRVEX13.domain.com
ServiceEndpoint : autodiscover.domain.com
Scenario : AutoDiscoverOutlookProvide r
ScenarioDescription : Autodiscover: Outlook Provider
Result : Failure
Latency : 114
Error : Microsoft.Exchange.Managem ent.Tasks. ServiceVal idatorExce ption: The Autodiscover response did not return a URL for Exchange Web Services. Response details:
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User>
<DisplayName>User</Display Name>
<LegacyDN>/o=ORG/ou=Exchan ge Administrative Group (FYDIBOHF23SPDLT)/cn=Recip ients/cn=U ser</Legac yDN>
<AutoDiscoverSMTPAddress>U ser@domain .com</Auto DiscoverSM TPAddress>
<DeploymentId>e3c75af6-a0b 6-422c-aa2 1-c807481e b678</Depl oymentId>
</User>
<Account>
<AccountType>email</Accoun tType>
<Action>settings</Action>
<MicrosoftOnline>False</Mi crosoftOnl ine>
<Protocol>
<Type>WEB</Type>
<Internal>
<OWAUrl AuthenticationMethod="Basi c, Fba">https://mail.domain.com/owa/</OWAUrl>
</Internal>
<External>
<OWAUrl AuthenticationMethod="Fba" >https://mail.domain.com/owa/</OWAUrl>
</External>
</Protocol>
</Account>
</Response>
</Autodiscover>
Verbose : [2016-07-22 16:14:57Z] Autodiscover connecting to 'https://autodiscover.domain.com/Autodiscover/Autodiscover.xml'.
[2016-07-22 16:14:57Z] Test account: User@domain.com Password: ******
[2016-07-22 16:14:57Z] Autodiscover request:
User-Agent: SRVEX13/Test-OutlookWebSer vices/User @domain.co m
Content-Type: text/xml; charset=utf-8
Authorization: Negotiate TlRMTVNTUAADAAAAGAAYAJQAAA A+AT4BrAAA AAAAAABYAA AAKgAqAFgA AAASABIAgg AAABAAEADq AQAAFYKI4g YDgCUAAAAP HCzAzgFNsP UMWilan2gG 2mEAZABtAF 8AZABkAGUA bABvAHI
AZQB5AEAAbgB0AHAAYwAuAGMAb wBtAEgAUgB TAFIAVgBFA FgAMQAzAAA AAAAAAAAAA AAAAAAAAAA AAAAAAAAAA LwAcJiiv4J hVUPJrnLNc KkBAQAAAAA AAPTsVjA05 NEBlZt9i/r oCPkAAAAAA gAIAE4AVAB QAEMAAQASA Fk
ASwBTAFIAVgBFAFgAMQAzAAQAE ABuAHQAcAB jAC4AYwBvA G0AAwAkAFk ASwBTAFIAV gBFAFgAMQA zAC4AbgB0A HAAYwAuAGM AbwBtAAUAE ABuAHQAcAB jAC4AYwBvA G0ABwAIAPT sVjA05NEBB gAEAAIAAAA IADAAMAAAA AA
AAAAAAAAAAEAAADCjn39tC5Wkv kL6GYaipL/ gLodxt8yUE NMy6UDEJU3 DCgAQAAAAA AAAAAAAAAA AAAAAAAAJA DQASABUAFQ AUAAvAGEAd QB0AG8AZAB pAHMAYwBvA HYAZQByAC4 AbgB0AHAAY wAuAGMAbwB tAAAAAAAAA AA
AAAAAAEvYKBfS/OoFxZk76p75l Rk=
Host: autodiscover.domain.com
Cookie: ClientId=E43B873C7C624E1F9 58835195A0 0BC5B
Content-Length: 453
Expect: 100-continue
[2016-07-22 16:14:57Z] Autodiscover request:
<?xml version="1.0"?>
<Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/requestschema/2006">
<Request>
<EMailAddress>User@domain. com</EMail Address>
<AcceptableResponseSchema> http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a</Acceptab leResponse Schema>
</Request>
</Autodiscover>
[2016-07-22 16:14:57Z] Autodiscover response:
request-id: 3a68e909-f467-495a-a72d-77 29b6465b40
X-CalculatedBETarget: srvex13.domain.com
X-DiagInfo: SRVEX13
X-BEServer: SRVEX13
Persistent-Auth: true
X-FEServer: SRVEX13
Content-Length: 1060
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Date: Fri, 22 Jul 2016 16:14:57 GMT
Set-Cookie: X-BackEndCookie=S-1-5-21-2 660971776- 2703906875 -190374780 0-6170=u56 Lnp2ejJqBm Z7NxpqdzMj SnJnMy9LLn svG0sbNz5v SzcfOy5vIy 8adypzKgYH Nz87J0s/H0 s3Oq87Jxc7 LxcrI;
expires=Sun, 21-Aug-2016 16:14:57 GMT; path=/Autodiscover; secure; HttpOnly
Server: Microsoft-IIS/8.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
[2016-07-22 16:14:57Z] Autodiscover response:
<?xml version="1.0" encoding="utf-8"?>
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User>
<DisplayName>User</Display Name>
<LegacyDN>/o=Org/ou=Exchan ge Administrative Group (FYDIBOHF23SPDLT)/cn=Recip ients/cn=U ser</Legac yDN>
<AutoDiscoverSMTPAddress>U ser@domain .com</Auto DiscoverSM TPAddress>
<DeploymentId>e3c75af6-a0b 6-422c-aa2 1-c807481e b678</Depl oymentId>
</User>
<Account>
<AccountType>email</Accoun tType>
<Action>settings</Action>
<MicrosoftOnline>False</Mi crosoftOnl ine>
<Protocol>
<Type>WEB</Type>
<Internal>
<OWAUrl AuthenticationMethod="Basi c, Fba">https://mail.domain.com/owa/</OWAUrl>
</Internal>
<External>
<OWAUrl AuthenticationMethod="Fba" >https://mail.domain.com/owa/</OWAUrl>
</External>
</Protocol>
</Account>
</Response>
</Autodiscover>
[2016-07-22 16:14:57Z] Autodiscover response:
Microsoft.Exchange.Managem ent.Tasks. ServiceVal idatorExce ption: The Autodiscover response did not return a URL for Exchange Web Services. Response details:
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User>
<DisplayName>User</Display Name>
<LegacyDN>/o=Org/ou=Exchan ge Administrative Group (FYDIBOHF23SPDLT)/cn=Recip ients/cn=U ser</Legac yDN>
<AutoDiscoverSMTPAddress>U ser@domain .com</Auto DiscoverSM TPAddress>
<DeploymentId>e3c75af6-a0b 6-422c-aa2 1-c807481e b678</Depl oymentId>
</User>
<Account>
<AccountType>email</Accoun tType>
<Action>settings</Action>
<MicrosoftOnline>False</Mi crosoftOnl ine>
<Protocol>
<Type>WEB</Type>
<Internal>
<OWAUrl AuthenticationMethod="Basi c, Fba">https://mail.domain.com/owa/</OWAUrl>
</Internal>
<External>
<OWAUrl AuthenticationMethod="Fba" >https://mail.domain.com/owa/</OWAUrl>
</External>
</Protocol>
</Account>
</Response>
</Autodiscover>
MonitoringEventId : 6001
Things I've tried so far:
Disabling the Mailbox and reconnecting to user account to recreate all exchange user properties
Clearing the msExchDelegateListBL attribute. It was clear I added a delegate mailbox and then removed it to test as well.
Ensure the LegacyExchangeDN was pointing to right place.
I'm out of options, any suggestions?
If I run the following powershell command here is what I get:
Test-OutlookWebServices -Identity User@domain.com -MailboxCredential (get-credential)
Source ServiceEndpoint Scenario Result Latency
(MS)
------ --------------- -------- ------ -------
SRVEX13.domain.com autodiscover.domain.com Autodiscover: Outlook Provider Failure 159
SRVEX13.domain.com Exchange Web Services Skipped 0
SRVEX13.domain.com Availability Service Skipped 0
SRVEX13.domain.com Offline Address Book Skipped 0
If I run it against other users, I get success across the board.
Full Error is here:
RunspaceId : 2661e5f6-6ad2-4204-bd5a-4d
Source : SRVEX13.domain.com
ServiceEndpoint : autodiscover.domain.com
Scenario : AutoDiscoverOutlookProvide
ScenarioDescription : Autodiscover: Outlook Provider
Result : Failure
Latency : 114
Error : Microsoft.Exchange.Managem
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User>
<DisplayName>User</Display
<LegacyDN>/o=ORG/ou=Exchan
<AutoDiscoverSMTPAddress>U
<DeploymentId>e3c75af6-a0b
</User>
<Account>
<AccountType>email</Accoun
<Action>settings</Action>
<MicrosoftOnline>False</Mi
<Protocol>
<Type>WEB</Type>
<Internal>
<OWAUrl AuthenticationMethod="Basi
</Internal>
<External>
<OWAUrl AuthenticationMethod="Fba"
</External>
</Protocol>
</Account>
</Response>
</Autodiscover>
Verbose : [2016-07-22 16:14:57Z] Autodiscover connecting to 'https://autodiscover.domain.com/Autodiscover/Autodiscover.xml'.
[2016-07-22 16:14:57Z] Test account: User@domain.com Password: ******
[2016-07-22 16:14:57Z] Autodiscover request:
User-Agent: SRVEX13/Test-OutlookWebSer
Content-Type: text/xml; charset=utf-8
Authorization: Negotiate TlRMTVNTUAADAAAAGAAYAJQAAA
AZQB5AEAAbgB0AHAAYwAuAGMAb
ASwBTAFIAVgBFAFgAMQAzAAQAE
AAAAAAAAAAEAAADCjn39tC5Wkv
AAAAAAEvYKBfS/OoFxZk76p75l
Host: autodiscover.domain.com
Cookie: ClientId=E43B873C7C624E1F9
Content-Length: 453
Expect: 100-continue
[2016-07-22 16:14:57Z] Autodiscover request:
<?xml version="1.0"?>
<Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/requestschema/2006">
<Request>
<EMailAddress>User@domain.
<AcceptableResponseSchema>
</Request>
</Autodiscover>
[2016-07-22 16:14:57Z] Autodiscover response:
request-id: 3a68e909-f467-495a-a72d-77
X-CalculatedBETarget: srvex13.domain.com
X-DiagInfo: SRVEX13
X-BEServer: SRVEX13
Persistent-Auth: true
X-FEServer: SRVEX13
Content-Length: 1060
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Date: Fri, 22 Jul 2016 16:14:57 GMT
Set-Cookie: X-BackEndCookie=S-1-5-21-2
expires=Sun, 21-Aug-2016 16:14:57 GMT; path=/Autodiscover; secure; HttpOnly
Server: Microsoft-IIS/8.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
[2016-07-22 16:14:57Z] Autodiscover response:
<?xml version="1.0" encoding="utf-8"?>
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User>
<DisplayName>User</Display
<LegacyDN>/o=Org/ou=Exchan
<AutoDiscoverSMTPAddress>U
<DeploymentId>e3c75af6-a0b
</User>
<Account>
<AccountType>email</Accoun
<Action>settings</Action>
<MicrosoftOnline>False</Mi
<Protocol>
<Type>WEB</Type>
<Internal>
<OWAUrl AuthenticationMethod="Basi
</Internal>
<External>
<OWAUrl AuthenticationMethod="Fba"
</External>
</Protocol>
</Account>
</Response>
</Autodiscover>
[2016-07-22 16:14:57Z] Autodiscover response:
Microsoft.Exchange.Managem
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User>
<DisplayName>User</Display
<LegacyDN>/o=Org/ou=Exchan
<AutoDiscoverSMTPAddress>U
<DeploymentId>e3c75af6-a0b
</User>
<Account>
<AccountType>email</Accoun
<Action>settings</Action>
<MicrosoftOnline>False</Mi
<Protocol>
<Type>WEB</Type>
<Internal>
<OWAUrl AuthenticationMethod="Basi
</Internal>
<External>
<OWAUrl AuthenticationMethod="Fba"
</External>
</Protocol>
</Account>
</Response>
</Autodiscover>
MonitoringEventId : 6001
Things I've tried so far:
Disabling the Mailbox and reconnecting to user account to recreate all exchange user properties
Clearing the msExchDelegateListBL attribute. It was clear I added a delegate mailbox and then removed it to test as well.
Ensure the LegacyExchangeDN was pointing to right place.
I'm out of options, any suggestions?
Make sure the user object is configured to Inherit permissions. This is done by enabled advanced view in ADUC, then going to the security tab on the object. Advanced security window will let you determine if inheritance is enabled. If it isn't, then the Exchange servers will have difficulty reading the exchange properties needed to determine the right mailbox server to use for his account. I would look at that first, since it is a very common issue. Let us know the result.
ASKER
Inheritance is indeed enabled and I can see the various Exchange permissions applied to user object.
A couple of other thoughts I should have included.
- User can access mailbox through OWA no problem, just not Outlook
- This is a returning user who was reenabled. Exchange migration from 2007 to 2013 took place while user was away - though the LegacyExchangeDN and msExchHomeServerName are correctly listed.
A couple of other thoughts I should have included.
- User can access mailbox through OWA no problem, just not Outlook
- This is a returning user who was reenabled. Exchange migration from 2007 to 2013 took place while user was away - though the LegacyExchangeDN and msExchHomeServerName are correctly listed.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I discovered the solution on my own through troubleshooting.