Exchange 2013 CU7 OWA 400 Bad Request after successful login RRS feed

  • Question

  • Scenario: Exchange 2007/2013 Migration

    One Exchange 2007 Server [removed]

    One Exchange 2013 Server Std, Windows 2012
    All mailboxes moved to 2013 - November 27-30 2014
    All public folders moved to 2013 - December 2, 2014

    Exchange 2007 is still running and has not been removed from the domain, yet. [update]

    Exchange 2007 removed from domain - 12-13-14

    SSL Certs are current for: Autodiscover.ExtDom.com, ex13.ExtDom.com, ex13.IntDom.com

    Applied CU6 (Dec 3, 2014) to fix Mobile access issues. Since applying CU6, OWA does not work with the exception of mobile browsers (Chrome - Nexus 7) or Safari 5.1.7 on Windows 7. These browsers get the OWA 2010 theme (Yellow).

    User logs into OWA with Domain\UserName and PWD(IE). After clicking Sign In, page returns Bad Request. No errors logged in w3scv logs.

    [update] CU7 applied 12-11-2014

    All users can connect using Outlook 2013 or Mobile (iPhone & Android)

    Exchange Admin Center (ECP) still works!

    Browsers tested: IE10 (windows 7 x64),Chrome 39.0.2171.71m, Opera 26.0, FireFox 34.0.5, Safari 5.1.7


    • https://ex13.ExtDom.com/owa

    • https://ex13.IntDom.com/owa

    • https://ex13.ExtDom.com/owa?ExchClientVer=15

    • https://ex13.IntDom.com/owa?ExchClientVer=15

    • https://localhost/owa (on Ex 2013 server)

    • https://localhost/owa?ExchClientVer=15 (on Ex 2013 Server)

    Fixes attempted:

    • remove | create Virtual Directories for OWA

    • Change authentication through Exchange PowerShell - Integrated/Basic from FBA/Basic

      • reverted since change didn’t work.

    • Run UpdateCas.ps1

    • Run UpdateConfigFiles.ps1

    • IISReset (iisReset /NoForce fails)

    OWA (Default Web Site) displays as Version 15.0 (Build 995.29) in EAC. [update] Build 1044.25 (CU7)

    Links used for troubleshooting:






    Tuesday, December 23, 2014 6:10 PM

All replies

  • Hi,

    Does it work if you disable the FBA and only use the basic authentication?

    Please also let us know the authentication settings on the Default Web site.


    Simon Wu
    TechNet Community Support

    Wednesday, December 24, 2014 9:01 AM
  • thanks for the reply. sorry for the delay, off for the holidays.

    I've tried disabling FBA and using only Windows Auth. After getting the dialog to log in and successfully authenticating, I still get the Bad Request error/page.

    As of now, the Default Web Site auth settings are (through EAC): Basic Authentication and FBA (Domain\User Name).

    These settings worked before applying CU6 and CU7. Also, OWA for non standard browsers does work (nexus tablet Safari 5.1.7 (windows).


    Monday, December 29, 2014 1:46 PM
  • Dear Chris,

    I am facing similar issue, I installed cu7 from scratch and after login to ecp or owa it says HTTP 500 error.

    Any help will be highly appreciated.

    This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented  the webpage from displaying. 


    Wednesday, July 15, 2015 6:08 AM