Exchange Owa Error 400
Contents |
360 games PC games exchange 2013 ecp http 400 bad request Windows games Windows phone games Entertainment All Entertainment
400 Outlook Web App Options Exchange 2013
Movies & TV Music Business & Education Business Students & educators the remote server returned an error (400) bad request. c# Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet
Remote Server Returned Error 400 Bad Request
Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All the remote server returned an error 400 bad request httpwebrequest Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
Neal (Exclaimer) Sales & Marketing Manager GROUP SPONSORED BY EXCLAIMER TECHNOLOGY IN
/owa/auth.owa Bad Request
THIS DISCUSSION Microsoft 492098 Followers Follow Microsoft Windows Server
The Remote Server Returned An Error (400) Bad Request. Wcf
Microsoft Windows Server 2012 Microsoft Exchange Server 2013 Join the Community! Creating your the remote server returned an error 400 bad request at system net httpwebrequest getresponse account only takes a few minutes. Join Now Scenario: Exchange 2007/2013 Coexistence One Exchange 2007 Server One Exchange 2013 Server Std, Windows 2012 All mailboxes https://support.microsoft.com/en-us/kb/2988444 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. 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 https://community.spiceworks.com/topic/683470-exchange-2013-owa-400-bad-request 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. 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 Attempted: 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. Links used for troubleshooting: http://community.spiceworks.com/topic/514617-exchange-2013-unable-to-login-to-owa-ecp https://social.technet.microsoft.com/Forums/ie/en-US/f8aa95d4-19e4-483c-8c4b-b039ab0d0127/400-bad-re... http://tecfused.com/2013/09/23/exchange-2013-ecp-double-login-error-400/ https://social.technet.microsoft.com/Forums/lync/en-US/c25ce81c-76ea-471a-93ae-eeaf9e5015ac/exch
AD Connect) VMWare Workstation: The VMware Authorization Service is not running Block xmlrpc.php attacks with fail2ban + iptables wordpress Recent Commentshayden kirk on PHP Fatal error: Uncaught Error: Call to http://www.tecfused.com/2013/09/exchange-2013-ecp-double-login-error-400/ undefined function xml_parser_create()4oo4 on PHP Fatal error: Uncaught Error: Call to undefined function http://msexchangeguru.com/2013/10/30/http-redirect-owa-ecp/ xml_parser_create()Richard on Storage Spaces and Parity - Slow write speedsden on Installing Disk Cleanup (cleanmgr.exe) Server 2008 and Server 2012bviktor on Storage Spaces and Parity - Slow write speedsArchives September 2016 August 2016 June 2016 April 2016 January 2016 December 2015 November 2015 September 2015 July 2015 June 2015 March 2015 November 2014 bad request October 2014 August 2014 July 2014 April 2014 January 2014 September 2013 August 2013 July 2013 May 2013 April 2013 March 2013 February 2013 June 2012 April 2012 March 2012 November 2011 June 2011 May 2011 April 2010 March 2010 September 2009 April 2009 March 2009 February 2009 Categories Backup Cisco copyright Exchange Fixes Games Google IBM IIS ISA/TMG Layer3 Lenovo Licensing Microsoft Networking News Office Outlook remote server returned Programming Recovery Reviews SBS Security Server Sharepoint Sophos Storage Tips Uncategorized Veeam Virtualization VMWare Windows Wordpress Meta Log in Entries RSS Comments RSS WordPress.org Exchange 2013: ECP double login, error 400 After an upgrade of Exchange 2013 from CU1 to CU2 we could no longer access the ECP part of Exchange. OWA worked fine. We got a blank screen with bad request, error 400. After a lot of searching, it looks like the upgrade for Exchange wipes out the web.config file which has all the settings for authentication on ECP. See the following: Be aware that this is incorrect after an upgrade. Set the authentication of basic to true again to ensure the setting is correct (note form based authentication is turned off because we use TMG). Also make sure your internal and external url for the ECP directory is reset, as this is also wiped. This is a known bug. See KB2871485. Share this:Click to share on Twitter (Opens in new window)Click to share on Facebook (Opens in new window)Click to share on Google+ (Opens in new window)Like this:Like Loading... Related Posted on September 23, 2013Author hayden kirkCategories Exchange, ISA/TMG, MicrosoftTags 400, auth.owa, ecp, KB2871485, owa.auth Leave a Reply
troubleshooting notes » Exchange 2013: HTTP redirection issues with ECP virtual directory - /owa/ecp When you try to access ECP on Exchange 2013, browser redirects to /owa/ecp and shows "Bad Request" You will see this if HTTP redirection is applied on Default website and those settings got replicated to all Virtual directories underneath. Let's look at How to enable HTTP redirect on Exchange 2013. To enable HTTP to HTTPS redirection on exchange 2013, on IIS VDir highlight Default website and click HTTP Redirect: Change the settings as shown: The issue addressed in this article will happen if the ECP Vdir has an HTTP redirect set on it: Let's recap the SSL Settings and HTTP redirect settings for all Virtual directories in Exchange 2013 and ensure it is set properly: Vitual Directory SSL enabled HTTP Redirect Default website NO Yes aspnet_client Yes NO Autodiscover Yes NO ecp Yes NO EWS Yes NO owa Yes NO Microsoft-Server-ActiveSync Yes NO OAB Yes NO PowerShell NO NO Rpc Yes NO Ratish Nair Microsoft MVP | Exchange Server Team @MSExchangeGuru Keywords: Exchange server 2013 owa redirection issue, exchange 2013 ECP redirects to /owa/ecp Posted October 30th, 2013 under CAS, Exchange 2013. RSS 2.0 feed. Leave a response, or trackback. 15 Responses to "Exchange 2013: HTTP redirection issues with ECP virtual directory - /owa/ecp" Mali stane Says: March 2nd, 2014 at 4:53 pm Exchange 2013 Sp1 Coexistence with Exchange 2010 SP3 CU5 HTTP 500 I`m trying to make working OWA coexistence between Exchange 2013 SP1 and Exchange 2010 SP3 CU5. When user login in to OWA where his mailbox is located on Exchange 2013 server it logon successful and owa opened. When i try to login to the same url with user whose mailbox is located on Exchange 2010 server i get Error http 50 The website cannot display the page : HTTP 500 »https://URLEXCHANGE2013/owa/a