• Home
  • Articles
    • Office 365
    • Exchange
    • Skype for Business (Lync)
    • Active Directory
    • Windows
    • Sharepoint
    • Joomla
    • Linux
    • Other
    • Blackberry
  • Project: Nagios Monitoring
    • First steps
    • NSCP installation
    • Scripts
    • FAQs
  • Links
  • Home
  • About
  • Imprint
Toggle navigation
Admin Enclave
  • Home
  • Articles
    • Office 365
    • Exchange
    • Skype for Business (Lync)
    • Active Directory
    • Windows
    • Sharepoint
    • Joomla
    • Linux
    • Other
    • Blackberry
  • Project: Nagios Monitoring
    • First steps
    • NSCP installation
    • Scripts
    • FAQs
  • Links
Home
/
Articles
/
Office 365
/
Data-Articles
/
Website Articles
/
Articles
/
Exchange
/
Troubleshooting connection issues from users migrated from Exchange 2010 to Exchange 2013/2016

Troubleshooting connection issues from users migrated from Exchange 2010 to Exchange 2013/2016

Bastian W.Sep 06, 2016Articles \ Exchange

Abstract: You migrated from Exchange 2010/2013 to 2016, but AutoDiscovery is not working correctly for migrated users.

Environment:

- Two exchange environments (Exchange 2010 and 2013 or Exchange 2016)

- The namespace is already moved over and Exchange 2016 is proxy the connections (to Exchange 2010/2013)

 

Troubleshooting 01:

- You created a user on Exchange 2010/2013, the use is able to work without any issues (via the Exchange 2016 proxy).

- You created a user on Exchange 2016, the user is able to work without any issues on the same PC as the Exchange 2010/2013 user.

- You moved a Exchange 2010/2013 user over to Exchange 2016. The mailbox is moved without issues, the user got a "Microsoft Exchange administrator has made a change that requires you quit and restart Outlook" as expected.

- If you restart Outlook as required the client still couldn´t connect.

Solution 01: Make sure that Outlook is up to date (keep noted that Exchange 2016 do not support Office 2007) as written in KB 2934750. Especially KB 2965295 for Office 2010 must be installed.

 

Troubleshooting 02:

If solution 01 didn´t solve the issue, then check if the "auto discovery" is working as expected

01a.) Reset the Outlook profile (so that we have a fresh new one to avoid any issues)

01b.) Enable Outlook Logging (as mentioned in KB 2862843) via:

Subkey: HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Options\Mail
DWORD: EnableLogging
Value: 1

For different versions make sure you use 15.0 instead of 12.0 for example.

01c.) Start Outlook 2010 until you see the issue

01d.) Search for %temp% and check the olkdisc.log in the user temp folder and if you do see some issues (see below)

As an alternate troubleshooting you use a working Outlook client and use the "Test E-Mail Configuration" hidden option. Use the email address from a affected user and select only the "UseAutoDiscovery"

Both (logging and the 'Test E-Mail Configuration') will produce a similar result as seen below:

Thread    Tick Count    Date/Time    Description
Account Configuration Version 14.0.7172.0
376 0x0066C3BD 09/07/16 18:36:02 Start AD lookup for e-mail address
376 0x0066C514 09/07/16 18:36:03 AD lookup for e-mail address Succeeded (0x00000000)
376 0x0066C524 09/07/16 18:36:03 +++++++++++++++++++++++++++++++
376 0x0066C524 09/07/16 18:36:03 AUTODISCOVER GET SETTINGS BEGIN
376 0x0066C524 09/07/16 18:36:03 SMTP=Exchange2010.Test@de.contoso.com
376 0x0066C591 09/07/16 18:36:03 Attempting URL https://owa.int.contoso.com/Autodiscover/Autodiscover.xml found through SCP
376 0x0066C591 09/07/16 18:36:03 Autodiscover to https://owa.int.contoso.com/Autodiscover/Autodiscover.xml starting
376 0x0066C5CF 09/07/16 18:36:03 GetLastError=0; httpStatus=401.
376 0x0066C5CF 09/07/16 18:36:03 AutoDiscover disabled auth schemes:
376 0x0066C5CF 09/07/16 18:36:03 <NONE>
376 0x0066C5CF 09/07/16 18:36:03 AutoDiscover supported auth schemes:
376 0x0066C5CF 09/07/16 18:36:03 Negotiate
376 0x0066C5CF 09/07/16 18:36:03 NTLM
376 0x0066C5CF 09/07/16 18:36:03 Basic
376 0x0066C5CF 09/07/16 18:36:03 AutoDiscover attempting Auto-Negotiate with Desktop Credentials.
376 0x0066C5CF 09/07/16 18:36:03 AutoDiscover USING pcreds->dwAuthScheme:
376 0x0066C5CF 09/07/16 18:36:03 Negotiate
376 0x0066C63D 09/07/16 18:36:03 GetLastError=0; httpStatus=302.
376 0x0066C63D 09/07/16 18:36:03 Autodiscover to https://owa.int.contoso.com/Autodiscover/Autodiscover.xml Failed (0x800C8204)
376 0x0066C63D 09/07/16 18:36:03 Autodiscover URL redirection to https://owa.int.contoso.com:443/Autodiscover/Exchange2010.Test..de.contoso.com/Autodiscover.xml
376 0x0066C63D 09/07/16 18:36:03 Autodiscover to https://owa.int.contoso.com:443/Autodiscover/Exchange2010.Test..de.contoso.com/Autodiscover.xml starting
376 0x0066C66B 09/07/16 18:36:03 GetLastError=0; httpStatus=401.
376 0x0066C66B 09/07/16 18:36:03 AutoDiscover disabled auth schemes:
376 0x0066C66B 09/07/16 18:36:03 <NONE>
376 0x0066C66B 09/07/16 18:36:03 AutoDiscover supported auth schemes:
376 0x0066C66B 09/07/16 18:36:03 Negotiate
376 0x0066C66B 09/07/16 18:36:03 NTLM
376 0x0066C66B 09/07/16 18:36:03 Basic
376 0x0066C66B 09/07/16 18:36:03 AutoDiscover attempting Auto-Negotiate with Desktop Credentials.
376 0x0066C66B 09/07/16 18:36:03 AutoDiscover USING pcreds->dwAuthScheme:
376 0x0066C66B 09/07/16 18:36:03 Negotiate
376 0x0066C6D9 09/07/16 18:36:03 GetLastError=0; httpStatus=302.
376 0x0066C6D9 09/07/16 18:36:03 Autodiscover to https://owa.int.contoso.com:443/Autodiscover/Exchange2010.Test..de.contoso.com/Autodiscover.xml Failed (0x800C8204)
376 0x0066C6D9 09/07/16 18:36:03 Autodiscover to https://de.contoso.com/autodiscover/autodiscover.xml starting
376 0x0066C6D9 09/07/16 18:36:03 GetLastError=12007; httpStatus=0.
376 0x0066C6D9 09/07/16 18:36:03 Autodiscover to https://de.contoso.com/autodiscover/autodiscover.xml Failed (0x800C8203)
376 0x0066C6D9 09/07/16 18:36:03 Autodiscover to https://autodiscover.de.contoso.com/autodiscover/autodiscover.xml starting
376 0x006718FE 09/07/16 18:36:24 GetLastError=12002; httpStatus=0.
376 0x006718FE 09/07/16 18:36:24 AutoDiscover internet timeout against URL https://autodiscover.de.contoso.com/autodiscover/autodiscover.xml
376 0x0067BD28 09/07/16 18:37:06 GetLastError=12002; httpStatus=0.
376 0x0067BD28 09/07/16 18:37:06 AutoDiscover internet timeout against URL https://autodiscover.de.contoso.com/autodiscover/autodiscover.xml
376 0x0067BD28 09/07/16 18:37:06 Autodiscover to https://autodiscover.de.contoso.com/autodiscover/autodiscover.xml Failed (0x800C8203)
376 0x0067BD28 09/07/16 18:37:06 Local autodiscover for de.contoso.com starting
376 0x0067BD28 09/07/16 18:37:06 Local autodiscover for de.contoso.com Failed (0x8004010F)
376 0x0067BD28 09/07/16 18:37:06 Redirect check to http://autodiscover.de.contoso.com/autodiscover/autodiscover.xml starting
376 0x0067BD47 09/07/16 18:37:06 Autodiscover URL redirection to https://oaw.emea.contoso.com/AutoDiscover/autodiscover.xml
376 0x0067BD47 09/07/16 18:37:06 Autodiscover to https://oaw.emea.contoso.com/AutoDiscover/autodiscover.xml starting
376 0x0067C12E 09/07/16 18:37:07 GetLastError=12029; httpStatus=0.
376 0x0067C12E 09/07/16 18:37:07 Autodiscover to https://oaw.emea.contoso.com/AutoDiscover/autodiscover.xml Failed (0x800C8203)
376 0x0067C12E 09/07/16 18:37:07 Srv Record lookup for http://autodiscover.de.contoso.com/autodiscover/autodiscover.xml Failed (0x800C8203)
376 0x0067C12E 09/07/16 18:37:07 Srv Record lookup for de.contoso.com starting
376 0x0067C13D 09/07/16 18:37:07 Autodiscover URL redirection to https://oaw.emea.contoso.com/autodiscover/autodiscover.xml
376 0x0067C13D 09/07/16 18:37:07 Autodiscover to https://oaw.emea.contoso.com/autodiscover/autodiscover.xml starting
376 0x0067C533 09/07/16 18:37:08 GetLastError=12029; httpStatus=0.
376 0x0067C533 09/07/16 18:37:08 Autodiscover to https://oaw.emea.contoso.com/autodiscover/autodiscover.xml Failed (0x800C8203)
376 0x0067C533 09/07/16 18:37:08 Srv Record lookup for de.contoso.com Failed (0x800C8203)
376 0x0067C533 09/07/16 18:37:08 AUTODISCOVER GET SETTINGS END
376 0x0067C533 09/07/16 18:37:08 -----------------------------

What you see here is that the internal AutoDiscovery entry performs an redirect (for example the first 0x800C8204 error) while a working Exchange 2016 user produce the following:

Thread    Tick Count    Date/Time    Description
Account Configuration Version 14.0.7172.0
2840 0x0047C514 09/07/16 18:02:11 Start AD lookup for e-mail address
2840 0x0047C83F 09/07/16 18:02:12 AD lookup for e-mail address Succeeded (0x00000000)
2840 0x0047C83F 09/07/16 18:02:12 +++++++++++++++++++++++++++++++
2840 0x0047C83F 09/07/16 18:02:12 AUTODISCOVER GET SETTINGS BEGIN
2840 0x0047C83F 09/07/16 18:02:12 SMTP=Exchange2016.User@de.contoso.com
2840 0x0047C938 09/07/16 18:02:12 Attempting URL https://owa.int.contoso.com/Autodiscover/Autodiscover.xml found through SCP
2840 0x0047C938 09/07/16 18:02:12 Autodiscover to https://owa.int.contoso.com/Autodiscover/Autodiscover.xml starting
2840 0x0047C977 09/07/16 18:02:12 GetLastError=0; httpStatus=401.
2840 0x0047C977 09/07/16 18:02:12 AutoDiscover disabled auth schemes:
2840 0x0047C977 09/07/16 18:02:12 <NONE>
2840 0x0047C977 09/07/16 18:02:12 AutoDiscover supported auth schemes:
2840 0x0047C977 09/07/16 18:02:12 Negotiate
2840 0x0047C977 09/07/16 18:02:12 NTLM
2840 0x0047C977 09/07/16 18:02:12 Basic
2840 0x0047C977 09/07/16 18:02:12 AutoDiscover attempting Auto-Negotiate with Desktop Credentials.
2840 0x0047C977 09/07/16 18:02:12 AutoDiscover USING pcreds->dwAuthScheme:
2840 0x0047C977 09/07/16 18:02:12 Negotiate
2840 0x0047CA03 09/07/16 18:02:12 GetLastError=0; httpStatus=200.
2840 0x0047CA03 09/07/16 18:02:12 Autodiscover XML Received
2840 ---BEGIN XML---

This is because of the reason that the Exchange Server 2013 or 2016 continues to proxy the autodiscover request to Exchange Server 2010. Exchange Server 2010 responds with a 302 redirect back to Exchange Server 2013 or 2016 (depending on the upgrade) which caused the 0x800C8204 error. According to the Microsoft (as seen here or here) the 0x800C8204 means "a redirect was received to a more accurate location" which explains the seen issue above.

Solution 02:

As written in KB 3097392 the MSExchangeAutodiscoverAppPool needs to be restarted on the affected Exchange 2016 server (keep noted if you have a cluster you need to perform that on all of them)

Restart-WebAppPool MSExchangeAutodiscoverAppPool

You might wish to run that on a periodic state (e.g. every 30min). If you wish to do that check the follow URL.

 

Note:

If this issue is affecting users who are connected via ActiveSync try to recycle the Sync App pool via (as reported here)

Restart-WebAppPool MSExchangeSyncAppPool

 

 

CrossReference:

https://blogs.technet.microsoft.com/rmilne/2015/04/29/office-365-autodiscover-lookup-process/

Comments (5)

Thye
Thye
  1. about 3 years ago
  2. #198
This comment was minimized by the moderator on the site

Can't thank you enough for posting this. We had the exact issue as described here which was fixed by restarting the AutoDiscover webapp.

  1. Reply
Tim
Tim
  1. about 3 years ago
  2. #336
This comment was minimized by the moderator on the site

You saved my day! Thank you so much.

  1. Reply
Bastian W
Bastian W    Tim
  1. about 2 years ago
  2. #442
This comment was minimized by the moderator on the site

You are welcome

  1. Reply
Gorlegg
Gorlegg
  1. about 2 years ago
  2. #440
This comment was minimized by the moderator on the site

You are the man! Thank you for saving my Friday! :-)

  1. Reply
Bastian W
Bastian W    Gorlegg
  1. about 2 years ago
  2. #441
This comment was minimized by the moderator on the site

You are welcome :-)

  1. Reply
There are no comments posted here yet

Leave your comments

Abstract: You migrated from Exchange 2010/2013 to 2016, but AutoDiscovery is not working correctly for migrated users.

Environment:

- Two exchange environments (Exchange 2010 and 2013 or Exchange 2016)

- The namespace is already moved over and Exchange 2016 is proxy the connections (to Exchange 2010/2013)

 

Troubleshooting 01:

- You created a user on Exchange 2010/2013, the use is able to work without any issues (via the Exchange 2016 proxy).

- You created a user on Exchange 2016, the user is able to work without any issues on the same PC as the Exchange 2010/2013 user.

- You moved a Exchange 2010/2013 user over to Exchange 2016. The mailbox is moved without issues, the user got a "Microsoft Exchange administrator has made a change that requires you quit and restart Outlook" as expected.

- If you restart Outlook as required the client still couldn´t connect.

Solution 01: Make sure that Outlook is up to date (keep noted that Exchange 2016 do not support Office 2007) as written in KB 2934750. Especially KB 2965295 for Office 2010 must be installed.

 

Troubleshooting 02:

If solution 01 didn´t solve the issue, then check if the "auto discovery" is working as expected

01a.) Reset the Outlook profile (so that we have a fresh new one to avoid any issues)

01b.) Enable Outlook Logging (as mentioned in KB 2862843) via:

Subkey: HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Options\Mail
DWORD: EnableLogging
Value: 1

For different versions make sure you use 15.0 instead of 12.0 for example.

01c.) Start Outlook 2010 until you see the issue

01d.) Search for %temp% and check the olkdisc.log in the user temp folder and if you do see some issues (see below)

As an alternate troubleshooting you use a working Outlook client and use the "Test E-Mail Configuration" hidden option. Use the email address from a affected user and select only the "UseAutoDiscovery"

Both (logging and the 'Test E-Mail Configuration') will produce a similar result as seen below:

Thread    Tick Count    Date/Time    Description
Account Configuration Version 14.0.7172.0
376 0x0066C3BD 09/07/16 18:36:02 Start AD lookup for e-mail address
376 0x0066C514 09/07/16 18:36:03 AD lookup for e-mail address Succeeded (0x00000000)
376 0x0066C524 09/07/16 18:36:03 +++++++++++++++++++++++++++++++
376 0x0066C524 09/07/16 18:36:03 AUTODISCOVER GET SETTINGS BEGIN
376 0x0066C524 09/07/16 18:36:03 SMTP=Exchange2010.Test@de.contoso.com
376 0x0066C591 09/07/16 18:36:03 Attempting URL https://owa.int.contoso.com/Autodiscover/Autodiscover.xml found through SCP
376 0x0066C591 09/07/16 18:36:03 Autodiscover to https://owa.int.contoso.com/Autodiscover/Autodiscover.xml starting
376 0x0066C5CF 09/07/16 18:36:03 GetLastError=0; httpStatus=401.
376 0x0066C5CF 09/07/16 18:36:03 AutoDiscover disabled auth schemes:
376 0x0066C5CF 09/07/16 18:36:03 <NONE>
376 0x0066C5CF 09/07/16 18:36:03 AutoDiscover supported auth schemes:
376 0x0066C5CF 09/07/16 18:36:03 Negotiate
376 0x0066C5CF 09/07/16 18:36:03 NTLM
376 0x0066C5CF 09/07/16 18:36:03 Basic
376 0x0066C5CF 09/07/16 18:36:03 AutoDiscover attempting Auto-Negotiate with Desktop Credentials.
376 0x0066C5CF 09/07/16 18:36:03 AutoDiscover USING pcreds->dwAuthScheme:
376 0x0066C5CF 09/07/16 18:36:03 Negotiate
376 0x0066C63D 09/07/16 18:36:03 GetLastError=0; httpStatus=302.
376 0x0066C63D 09/07/16 18:36:03 Autodiscover to https://owa.int.contoso.com/Autodiscover/Autodiscover.xml Failed (0x800C8204)
376 0x0066C63D 09/07/16 18:36:03 Autodiscover URL redirection to https://owa.int.contoso.com:443/Autodiscover/Exchange2010.Test..de.contoso.com/Autodiscover.xml
376 0x0066C63D 09/07/16 18:36:03 Autodiscover to https://owa.int.contoso.com:443/Autodiscover/Exchange2010.Test..de.contoso.com/Autodiscover.xml starting
376 0x0066C66B 09/07/16 18:36:03 GetLastError=0; httpStatus=401.
376 0x0066C66B 09/07/16 18:36:03 AutoDiscover disabled auth schemes:
376 0x0066C66B 09/07/16 18:36:03 <NONE>
376 0x0066C66B 09/07/16 18:36:03 AutoDiscover supported auth schemes:
376 0x0066C66B 09/07/16 18:36:03 Negotiate
376 0x0066C66B 09/07/16 18:36:03 NTLM
376 0x0066C66B 09/07/16 18:36:03 Basic
376 0x0066C66B 09/07/16 18:36:03 AutoDiscover attempting Auto-Negotiate with Desktop Credentials.
376 0x0066C66B 09/07/16 18:36:03 AutoDiscover USING pcreds->dwAuthScheme:
376 0x0066C66B 09/07/16 18:36:03 Negotiate
376 0x0066C6D9 09/07/16 18:36:03 GetLastError=0; httpStatus=302.
376 0x0066C6D9 09/07/16 18:36:03 Autodiscover to https://owa.int.contoso.com:443/Autodiscover/Exchange2010.Test..de.contoso.com/Autodiscover.xml Failed (0x800C8204)
376 0x0066C6D9 09/07/16 18:36:03 Autodiscover to https://de.contoso.com/autodiscover/autodiscover.xml starting
376 0x0066C6D9 09/07/16 18:36:03 GetLastError=12007; httpStatus=0.
376 0x0066C6D9 09/07/16 18:36:03 Autodiscover to https://de.contoso.com/autodiscover/autodiscover.xml Failed (0x800C8203)
376 0x0066C6D9 09/07/16 18:36:03 Autodiscover to https://autodiscover.de.contoso.com/autodiscover/autodiscover.xml starting
376 0x006718FE 09/07/16 18:36:24 GetLastError=12002; httpStatus=0.
376 0x006718FE 09/07/16 18:36:24 AutoDiscover internet timeout against URL https://autodiscover.de.contoso.com/autodiscover/autodiscover.xml
376 0x0067BD28 09/07/16 18:37:06 GetLastError=12002; httpStatus=0.
376 0x0067BD28 09/07/16 18:37:06 AutoDiscover internet timeout against URL https://autodiscover.de.contoso.com/autodiscover/autodiscover.xml
376 0x0067BD28 09/07/16 18:37:06 Autodiscover to https://autodiscover.de.contoso.com/autodiscover/autodiscover.xml Failed (0x800C8203)
376 0x0067BD28 09/07/16 18:37:06 Local autodiscover for de.contoso.com starting
376 0x0067BD28 09/07/16 18:37:06 Local autodiscover for de.contoso.com Failed (0x8004010F)
376 0x0067BD28 09/07/16 18:37:06 Redirect check to http://autodiscover.de.contoso.com/autodiscover/autodiscover.xml starting
376 0x0067BD47 09/07/16 18:37:06 Autodiscover URL redirection to https://oaw.emea.contoso.com/AutoDiscover/autodiscover.xml
376 0x0067BD47 09/07/16 18:37:06 Autodiscover to https://oaw.emea.contoso.com/AutoDiscover/autodiscover.xml starting
376 0x0067C12E 09/07/16 18:37:07 GetLastError=12029; httpStatus=0.
376 0x0067C12E 09/07/16 18:37:07 Autodiscover to https://oaw.emea.contoso.com/AutoDiscover/autodiscover.xml Failed (0x800C8203)
376 0x0067C12E 09/07/16 18:37:07 Srv Record lookup for http://autodiscover.de.contoso.com/autodiscover/autodiscover.xml Failed (0x800C8203)
376 0x0067C12E 09/07/16 18:37:07 Srv Record lookup for de.contoso.com starting
376 0x0067C13D 09/07/16 18:37:07 Autodiscover URL redirection to https://oaw.emea.contoso.com/autodiscover/autodiscover.xml
376 0x0067C13D 09/07/16 18:37:07 Autodiscover to https://oaw.emea.contoso.com/autodiscover/autodiscover.xml starting
376 0x0067C533 09/07/16 18:37:08 GetLastError=12029; httpStatus=0.
376 0x0067C533 09/07/16 18:37:08 Autodiscover to https://oaw.emea.contoso.com/autodiscover/autodiscover.xml Failed (0x800C8203)
376 0x0067C533 09/07/16 18:37:08 Srv Record lookup for de.contoso.com Failed (0x800C8203)
376 0x0067C533 09/07/16 18:37:08 AUTODISCOVER GET SETTINGS END
376 0x0067C533 09/07/16 18:37:08 -----------------------------

What you see here is that the internal AutoDiscovery entry performs an redirect (for example the first 0x800C8204 error) while a working Exchange 2016 user produce the following:

Thread    Tick Count    Date/Time    Description
Account Configuration Version 14.0.7172.0
2840 0x0047C514 09/07/16 18:02:11 Start AD lookup for e-mail address
2840 0x0047C83F 09/07/16 18:02:12 AD lookup for e-mail address Succeeded (0x00000000)
2840 0x0047C83F 09/07/16 18:02:12 +++++++++++++++++++++++++++++++
2840 0x0047C83F 09/07/16 18:02:12 AUTODISCOVER GET SETTINGS BEGIN
2840 0x0047C83F 09/07/16 18:02:12 SMTP=Exchange2016.User@de.contoso.com
2840 0x0047C938 09/07/16 18:02:12 Attempting URL https://owa.int.contoso.com/Autodiscover/Autodiscover.xml found through SCP
2840 0x0047C938 09/07/16 18:02:12 Autodiscover to https://owa.int.contoso.com/Autodiscover/Autodiscover.xml starting
2840 0x0047C977 09/07/16 18:02:12 GetLastError=0; httpStatus=401.
2840 0x0047C977 09/07/16 18:02:12 AutoDiscover disabled auth schemes:
2840 0x0047C977 09/07/16 18:02:12 <NONE>
2840 0x0047C977 09/07/16 18:02:12 AutoDiscover supported auth schemes:
2840 0x0047C977 09/07/16 18:02:12 Negotiate
2840 0x0047C977 09/07/16 18:02:12 NTLM
2840 0x0047C977 09/07/16 18:02:12 Basic
2840 0x0047C977 09/07/16 18:02:12 AutoDiscover attempting Auto-Negotiate with Desktop Credentials.
2840 0x0047C977 09/07/16 18:02:12 AutoDiscover USING pcreds->dwAuthScheme:
2840 0x0047C977 09/07/16 18:02:12 Negotiate
2840 0x0047CA03 09/07/16 18:02:12 GetLastError=0; httpStatus=200.
2840 0x0047CA03 09/07/16 18:02:12 Autodiscover XML Received
2840 ---BEGIN XML---

This is because of the reason that the Exchange Server 2013 or 2016 continues to proxy the autodiscover request to Exchange Server 2010. Exchange Server 2010 responds with a 302 redirect back to Exchange Server 2013 or 2016 (depending on the upgrade) which caused the 0x800C8204 error. According to the Microsoft (as seen here or here) the 0x800C8204 means "a redirect was received to a more accurate location" which explains the seen issue above.

Solution 02:

As written in KB 3097392 the MSExchangeAutodiscoverAppPool needs to be restarted on the affected Exchange 2016 server (keep noted if you have a cluster you need to perform that on all of them)

Restart-WebAppPool MSExchangeAutodiscoverAppPool

You might wish to run that on a periodic state (e.g. every 30min). If you wish to do that check the follow URL.

 

Note:

If this issue is affecting users who are connected via ActiveSync try to recycle the Sync App pool via (as reported here)

Restart-WebAppPool MSExchangeSyncAppPool

 

 

CrossReference:

https://blogs.technet.microsoft.com/rmilne/2015/04/29/office-365-autodiscover-lookup-process/

Comments (5)

Thye
Thye
  1. about 3 years ago
  2. #198
This comment was minimized by the moderator on the site

Can't thank you enough for posting this. We had the exact issue as described here which was fixed by restarting the AutoDiscover webapp.

  1. Reply
Tim
Tim
  1. about 3 years ago
  2. #336
This comment was minimized by the moderator on the site

You saved my day! Thank you so much.

  1. Reply
Bastian W
Bastian W    Tim
  1. about 2 years ago
  2. #442
This comment was minimized by the moderator on the site

You are welcome

  1. Reply
Gorlegg
Gorlegg
  1. about 2 years ago
  2. #440
This comment was minimized by the moderator on the site

You are the man! Thank you for saving my Friday! :-)

  1. Reply
Bastian W
Bastian W    Gorlegg
  1. about 2 years ago
  2. #441
This comment was minimized by the moderator on the site

You are welcome :-)

  1. Reply
There are no comments posted here yet

Leave your comments

  1. Posting comment as a guest.
Attachments (0 / 3)
Share Your Location

2016 - MS ExchangeExchange 2016

Follow me on Twitter

Recent Posts

  • How to connect a Osram On/Off Plug with Phoscon/deCONZ

    Friday, 20 March 2020
  • Update TPM Firmware on Windows 10 1909

    Saturday, 15 February 2020
  • Switch your PC from BIOS to UEFI

    Tuesday, 07 January 2020
  • WLAN 6 (AX) released

    Monday, 23 September 2019
  • Use deCONZ to perform an OTA firmware update of OSRAM devices

    Saturday, 23 March 2019

Tags

Exchange 20162016 - MS ExchangeServer 2015Hardening2016 - MS Skype for Business Server 2017 - MS WindowsWindows Server 2012Windows2017 - MS ExchangeExchange 20132016 - MS Windows2013Exchange2017 - MS Skype for Business Server 2016 - MS SharepointRaspberry PiMicrosoftOpenHABHomeMatic2017 - MS Sharepoint

Archive

      • How to connect a Osram On/Off Plug with Phoscon/deCONZ
      • Update TPM Firmware on Windows 10 1909
      • Upgrade the BIOS from an ReadyNAS device
      • Switch your PC from BIOS to UEFI
      • WLAN 6 (AX) released
      • [ReSolved] Get-MailboxRestoreRequest matches multiple entries and couldn´t be performed
      • Use deCONZ to perform an OTA firmware update of OSRAM devices
      • Remove the Transparent Data Encryption (TDE) from a SQL DB
      • Install OpenHAB 2.4.x on Raspberry Pi (on Debian 9 - Stretch)
      • Windows 10 Driver for HP EliteBook 2570p Notebook-PC
      • Windows 10 Driver for HP EliteBook 850 G1 Notebook
      • Windows 10 Driver for HP EliteBook 8570p Notebook
      • Windows 10 Driver for IBM Thinkpad T560 Notebook
      • Windows 10 Driver for HP EliteBook 850 G5 Notebook
      • Windows 10 Driver for Lenovo T560 Notebook
      • Add an additional Sharepoint Admin to every Site Collection via Powershell
      • Do not install .NET Framework 4.7.2 on Exchange Servers yet
      • [Resolved] Unable to Migrate User to O365 due to "Target user 'XYZ' already has a primary mailbox"
      • Migrate SharePoint Elements to SharePoint Online
      • Microsoft Exchange OU picker is empty when creating new user or group
      • Exchange Online Powershell failed to connect when using MFA
      • Move-DatabasePath caused a "WMI exception occurred on server XY: Quota violation"
      • Privacy Policy
      • D:\AdvancedDataGovernanceLogs created on Exchange 2016
      • After May 2018 security update "An authentication error occurred" using RDP
      • Find out which .NET Framework version is installed
      • Install OpenHAB 2.0.x on Raspberry Pi (on Debian 9 - Stretch)
      • Convert a *.pfx certificate into *.pem
      • Changing last modified and creation date or time via PowerShell
      • Multidimensional arrays in Powershell
      • HowTo create an Enterprise Wiki on SharePoint Online
      • Attention: Microsoft Office 365 will disable support for TLS 1.0 and 1.1
      • [RESOLVED] Graphics Card issue when installing BlueStacks inside VMWare
      • How to create a pkcs12 file with a ordered certificate chain?
      • Publish an S/Mime certificate to AD via Powershell
      • [RESOLVED] iOS accounts needs permission to access resources in your organization that only an admin can grant
      • [RESOLVED] Exchange 2016 CU X failed to install error 1619
      • Headless Raspberry Pi WLAN Configuration
      • How to remove all partitions on an USB stick / SD card
      • How to generate a notifications once Handbreak finished its current work?
      • Enable TLS 1.1 and TLS 1.2 as a default secure protocols in WinHTTP
      • Security Hardening: Upgrade Diffie-Hellman Prime to 2048 bit on Windows Server
      • Change a SSL Certificate on Windows Server 2012 R2 Web Application Proxy
      • Add Windows Updates to a Windows 7 SP1 image
      • When using Import-Module you got an unblock file error
      • [Resolved] Exchange admin got the error "User profile cannot be loaded" when using RDP
      • Google Chrome browser to deprecate trust in existing Symantec-issued certificates
      • [RESOLVED] Error ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY when using Google Chome and OWA
      • Cumulative Update 6 for Exchange Server 2016 released
      • Windows Phone 8.1 will reach EOL on the 2017-07-11
      • .NET Framework 4.7.* and Microsoft Exchange Server
      • Disable weak cipher (e.g. 3DES, SSLv3, MD5, ...) suites in Java
      • [RESOLVED] "Could not find stored procedure" after installing SfB Server Updates
      • [RESOLVED] None of the network adapters are bound to the netmon driver.
      • [Resolved] No connectivity with any of Web Conferencing Edge Servers - Event 41026
      • Raspberry Pi - Connect to multiple wireless networks (WLAN) automatically
      • From 0 to Raspberry Pi (start with Raspberry Pi)
      • [RESOLVED] Exchange 2016 IIS not usable after installation from CU5
      • Microsoft Exchange 2007 reached end of life today
      • .NET Framework 4.7 released but not yet supported on Exchange 2016
      • .NET Framework 4.7 released but not yet supported on Skype for Business
      • Using Quest ActiveRoles Management Shell to add/update all users from a OU inside an AD group
      • [RESOLVED] Can´t install Office Web Apps Server because it requires .NET 4.5
      • Cumulative Update 5 for Exchange Server 2016 released
      • Using the Skype for Business device update service
      • Enable XA transactions on Microsoft SQL 2012
      • [RESOLVED] The Open Procedure for service XXX in DLL "C:\Windows\System32\XXX.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code
      • WES7 is crashing on VMWare Workstation
      • WES7 / WES8 OS deployment issue on VMWare Workstation
      • [RESOLVED] Growing amount of missing disk space on Microsoft Exchange
      • Disabling TLS 1.0 on Microsoft Sharepoint
      • Reset the content index on an MS Exchange DAG environment
      • Deploy the Statistics Manager for Skype for Business Server
      • HowTo add own formats to the TinyMCE Editor in Joomla?
      • Create a Kerberos authentication account in Skype for Business
      • Hardening Microsoft Exchange 2016 Server
      • Hardening Microsoft SharePoint 2016 Server
      • Hardening Microsoft Skype for Business Server
      • [Workaround] "Screen presenting isn't supported with this contact" with SfB MAC
      • [RESOLVED] Black or frozen screen during screensharing in Skype for Business 2016
      • Exchange Windows OS Hardening: Disable SSL 2.0/3.0 & PCT 1.0 & weak ciphers
      • SfB Windows OS Hardening: Disable SSL 2.0/3.0 & PCT 1.0 & weak ciphers
      • SharePoint Windows OS Hardening: Disable SSL 2.0/3.0 & PCT 1.0 & weak ciphers
      • Configure https for Windows Remote Management (WinRM) on Windows 2012 R2
      • Configure https for Windows Remote Management (WinRM) on Windows 2012 R2
      • Configure https for Windows Remote Management (WinRM) on Windows 2012 R2
      • Hardening Skype for Business Server
      • [RESOLVED] You do not have the permission to send the message on behalf of the specified user
      • Copy Windows Installation DVD to ISO
      • [RESOLVED] The remote certificate is invalid according to the validation procedure.
      • Prevent that the Skype for Business client will open when the user click on an meeting URL
      • Test GroupPolicy (*.admx templates) locally without AD
      • Implementing the Skype for Business Call Quality Dashboard
      • Configure / Finetune the Microsoft Exchange search / indexing feature
      • Disable content indexing on all DBs on an Exchange DAG
      • HowTo: create Search Sharepoint 2013 Foundation Application via Powershell
      • Migrate from Exchange 2010 to Exchange 2016
      • Enable TLS 1.2 on Windows 2012 R2
      • Download Skype for Business for MAC
      • [RESOLVED] Exchange 2013/2016 hub transport Mail.que file large in size
      • How to get only a subset from a 2 GB big logfile?
      • Add the Internet Explorer 11 and Updates to a Windows 7 SP1 image
      • [RESOLVED] MSExchange Mailbox Replication error 1006 (database doesn't exist)
      • Nagios Core 3.x installation guide on Debian 8.x (Jessie)
      • Move Exchange 2010/2013 user to Exchange 2016
      • [RESOLVED]: "Whole calendar" greyed out when publishing a calendar via Outlook on a webdav server
      • SfB Windows OS Hardening: Disable the "X-AspNet-Version" header
      • Exchange Windows OS Hardening: Disable the "X-AspNet-Version" header
      • SharePoint Windows OS Hardening: Disable the "X-AspNet-Version" header
      • Powershell: Clean (Remove) all completed Exchange Mailbox move requests
      • HP Data Protector isn´t able to browse an Exchange 2016 DAG
      • Powershell: Get a list from all Exchange users, where the latest logon time is older then 270 days
      • Usefull links
      • Hardening Microsoft Exchange 2013 Server
      • [Solution] Skype for Business Error: This message wan´t send to Firstname LastName
      • Step-By-Step: Configuring Office Online Server with Skype for Business
      • Troubleshooting connection issues from users migrated from Exchange 2010 to Exchange 2013/2016
      • Skype for Business Server DB update needed after patch management
      • How to check the progress of the ‘Shrink Database’ task in SQL Server 2012
      • Build an MS Exchange Throttling Policy to remove inactive mobile device partnerships
      • Exchange Windows OS Hardening: Disable NTFS 8 Dot 3
      • SfB Windows OS Hardening: Disable NTFS 8 Dot 3
      • SharePoint Windows OS Hardening: Disable NTFS 8 Dot 3
      • Windows OS Hardening: Disable NTFS 8 Dot 3
      • [RESOLVED] Centralized Logging Service Agent Error while moving cache files to network share.
      • [RESOLVED] MS Web Application Proxy used with SfB caused a Error 502
      • Manage the SSL certificate on Exchange 2016 via Powershell
      • [RESOLVED] How to fix damaged or corrupt Health Mailbox on Exchange 2016
      • [RESOLVED] "The client and server cannot communicate, because they do not possess a common algorithm"
      • Homematic IP Schalt und Steckdose mit CCU 2 verbinden / anlernen
      • Exchange 2010 to Exchange 2016 Co-Existence migration OWA redirect not working
      • Factory reset HomeMatic IP devices
      • Factory reset / Werksreset von HomeMatic IP Geräten
      • Pairing / Using Homematic IP Pluggable Switch and Meter with an CCU2
      • [Resolved] A Skype for business user isn´t able to join meeting via invitation link
      • Installation von BluePy auf dem Raspberry Pi
      • Install BluePy on Raspberry Pi
      • Released: Microsoft Exchange 2016 CU 2
      • Install OpenHAB 1.x on Raspberry Pi
      • Installieren von OpenHAB 1.x auf dem Raspberry Pi
      • Rebalance Mailbox Databases in an Exchange Server DAG via TaskManager
      • Fix a failed and suspended content index state on MS Exchange
      • Howto send an email using telnet
      • Hardening Windows Server (Basic Steps)
      • [RESOLVED] No DNS servers could be retrieved from network adapter 00000000-0000-0000-0000-000000000000
      • [RESOLVED] Setup can't use the domain controller because it belongs to Active Directory site
      • Use MS Web Application Proxy as reverse proxy (and ADFS) with Skype for business
      • [RESOLVED] Error message 0x80094004 when completing a certification request on IIS
      • [RESOLVED] Unable to collect NUMA physical memory utilization data. The first four bytes (DWORD) of the Data section contains the status code.
      • Get all Exchange user inclusive details from a list of AD groups
Admin Enclave

The Admin enclave delivers the latest news, quick tips, useful tricks, and in-depth tutorials for IT pros working with IT solutions (e.g. Microsoft Sharepoint, Microsoft Exchange, Microsoft Skype for Business, Joomla, ...).

Follow Us

Recent Posts

  • How to connect a Osram On/Off Plug with Phoscon/deCONZ

    Friday, 20 March 2020
  • Update TPM Firmware on Windows 10 1909

    Saturday, 15 February 2020
  • Switch your PC from BIOS to UEFI

    Tuesday, 07 January 2020
  • WLAN 6 (AX) released

    Monday, 23 September 2019
  • Use deCONZ to perform an OTA firmware update of OSRAM devices

    Saturday, 23 March 2019

Popular Posts

  • How to fix “The program can’t start because MSVCR110.dll is missing from your computer.” error on Windows

    Sunday, 07 April 2013
  • [RESOLVED] You do not have the permission to send the message on behalf of the specified user

    Wednesday, 16 November 2016
  • [RESOLVED] Exchange 2013/2016 hub transport Mail.que file large in size

    Thursday, 13 October 2016
  • [RESOLVED] The Open Procedure for service XXX in DLL "C:\Windows\System32\XXX.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code

    Wednesday, 08 March 2017
  • [RESOLVED] "The client and server cannot communicate, because they do not possess a common algorithm"

    Wednesday, 13 July 2016
© 2012 - 2021 admin-enclave.com | Disclaimer | Privacy Policy | Imprint | Articles by year