Fresh install running in coexistence mode, created test user on exchange 2013 mbx1, can not get autodiscover to work... it keeps returning HTTP error 400 Bad request. Any suggestions ?

[PS] C:\Program Files\Microsoft\Exchange Server\V15\Scripts>Test-OutlookWebServices | fl
Creating a new session for implicit remoting of "Test-OutlookWebServices" command...

RunspaceId          : a3a825b3-f752-4b7d-b461-9cdc263f0398
Source              : MBX1.domain.com
ServiceEndpoint     : mail.domain.com
Scenario            : AutoDiscoverOutlookProvider
ScenarioDescription : Autodiscover: Outlook Provider
Result              : Failure
Latency             : 411
Error               : System.Net.WebException: The remote server returned an error: (400) Bad Request.
                         at System.Net.HttpWebRequest.GetResponse()
                         at
                      Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.InternalInvoke()
                         at Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.Invoke()
Verbose             : [2013-05-06 18:42:58Z] Autodiscover connecting to
                      'https://mail.domain.com/autodiscover/autodiscover.xml'.
                      [2013-05-06 18:42:58Z] Test account: extest_47f5c08502074@domain.com Password: ******
                      [2013-05-06 18:42:58Z] Autodiscover request:
                      User-Agent: MBX1/Test-OutlookWebServices/extest_47f5c08502074@domain.com
                      Content-Type: text/xml; charset=utf-8
                      Host: mail.domain.com
                      [2013-05-06 18:42:58Z] 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>extest_47f5c08502074@domain.com</EMailAddress>
                          <AcceptableResponseSchema>http://schemas.microsoft.com/exchange/autodiscover/outlook/response
                      schema/2006a</AcceptableResponseSchema>
                        </Request>
                      </Autodiscover>
                      [2013-05-06 18:42:58Z] Autodiscover response:
                      Connection: Keep-Alive
                      Content-Length: 11
                      Content-Type: text/html
                      Date: Mon, 06 May 2013 18:42:58 GMT
                      Server: Microsoft-IIS/7.5
                      X-Powered-By: ASP.NET
                      [2013-05-06 18:42:58Z] Autodiscover response:
                      System.Net.WebException: The remote server returned an error: (400) Bad Request.
                         at System.Net.HttpWebRequest.GetResponse()
                         at
                      Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.InternalInvoke()
                         at Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.Invoke()
MonitoringEventId   : 6001

Hello,

It will be more directly to test the autodiscover by the following method:

Manually access the url: https://autodiscover.EmailAddressSuffix/autodiscover/autodiscover.xml via IE and see whether it returns code 600. Code 600 means the autodiscover works fine.

Thanks,

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

Simon, If I access https://cas2013servername/autodiscover/autodiscover.xml using IE I also get this HTTP 400 Bad request response (no XML). Note: doing te same to the cas2010 servers indeed yields XML response containing 600 code.

I have the same issue i guess...

Just to make sure:

Do You have CAS and mailbox roles on the same server?

If yes try to browse to https://cas2013servername:444/autodiscover/autodiscover.xml what do you get?

My CAS and MBX roles are running on different servers.

Browsing to https://mailbox2013servername:444/autodiscover/autodiscover.xml returns the expected XML response with code 600.

There is no response on port 444 of the cas2013server

Let us know if You will manage solve that.

For now no one can point me to the right direction

Hello,

OK. Since the result is fine when accessing from CAS and MBX, it means the autodiscover virtual directory is fine. The issue occurs between the Client side to the Server side.

Id like to ask whether the client have any proxy settings enabled. Or any firewall between them.

Thanks,

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

Simon, you misunderstood....

browsing to https://cas2013servername/autodiscover/autodiscover.xml fails all the time (from local machine from workstation, from other exchange servers.

Browsing to https://mailbox2013servername:444/autodiscover/autodiscover.xml or https://cas2010servername/autodiscover/autodiscover.xml works ok all the time.

So now here is something interesting;

 I ran into the following similar post : http://social.technet.microsoft.com/Forums/en-US/exchangesvrclients/thread/a0b2f287-a5af-48c8-9242-ba64fd16bf13

Decided to have some colleagues test the URL and found that the autodiscover only fails with 400 bad request for my own account and it works OK for many others.

Note: All accounts that I am testing with still have their mailbox on 2010.

And what about outlook client for these colleagues?

When you point it to exchange 2013 cas it works?

Ikariux, I am not ready route outlook client traffic to exchange 2013 untill I can explain and resolve this because autodiscover is so essential to overall functioning of outlook clients.

Just did another complete fresh install of the CAS server...

Test-outlookwebservices (with probe account and a test account which both have mailbox on 2013) = success

Test-outlookwebservices with my own account = Fail on autodiscover with

Error               : System.Net.WebException: The remote server returned an error: (400) Bad Request.
                         at System.Net.HttpWebRequest.GetResponse()
                         at
                      Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.InternalInvoke()
                         at Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.Invoke()

Am pulling my hair out and hoping for someone on this forum to throw me a lifeline.

did a lot more testing, and could only find 1 one account that is failing, all the other colleagues are OK.

So Pointed all traffic to 2013 CAS servers, started moving mailboxes. Everything is working fine EXCEPT for one single account: my own outlook will NOT connect using outlookanywhere and both external as well as internal tests fail with HTTP 400 error on autodiscover. and manual config forcing it to use RPC over HTTP does the same.

This tells me all exchange config is A-OK, and there is some type of AD property/attribute on my account that causes this failure.

Strange. I have tried to create new user in AD with mailbox in Exchange 2010 MBX server. User is not member of any groups and has only default AD attributes set up. Result is the same - when browsing https://2013cas/Autodiscover/autodiscover.xml  - http 400 bad request

Hello,

Then the mailbox should be corrupted. You may backup the data and rebuild the mailbox for the problematic user.

Thanks,

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

When testing this again today I was no longer able to reproduce the error....

I have been able to move my mailbox to exchange 2013 without errors, so doubt that mailbox corruption was a factor here.

Also made many more changes (including setting the internal and external url on virtual directories to be the same) but unfortunately am unable to say exactely what change made the error disappear.

• Marked as answer by adenhaan Wednesday, May 22, 2013 1:57 PM

This is a known issue: https://support.microsoft.com/en-us/kb/2988444

That said, the provided resolution did not work in our environment.