Owa Error 400 Exchange 2007
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: HTTP 400 Bad Request Error for OWA Previous Versions of Exchange > Exchange Previous Versions - Outlook, OWA, exchange 2013 owa 400 bad request POP, and IMAP Clients Question 1 Sign in to vote Good afternoon everyone,I
Outlook Web App Bad Request
have an intersting issue at one of my client sites that I'm hoping to get some insight on. The client
Bad Request Error Outlook Web Access
in question has an Microsoft Exchange Server 2007 that has been functioning fine for the past couple years. The problem is that when users attempt to access the page:https://server.domain.com/exchangeThey receive an error in Internet
400 Outlook Web App Options Exchange 2013
Explorer stating "HTTP 400 Bad Request"; however, viewing the web page in an alternative browser in light mode (e.g. Firefox) works perfect.The Exchange server's OWA site works fine if you visit the following address:https://server.domain.com/owaIn the past this occured once because of a patch from Microsoft, but I'm having a hard time ascertaining whether or not this is the case this time or not. My thoughts lead me to exchange 2010 owa bad request believe the error may be IIS related.Does anyone have any input on this issue?Thank you for your time and I look forward to hearing from you.: Michael Thursday, May 01, 2008 10:55 PM Reply | Quote All replies 0 Sign in to vote I am having this same exact issue. I tried to install a new certificate and everything went to heck. I can access the owa lite through Safari, but not internet explorer. I'm just as confused. Friday, May 02, 2008 8:14 PM Reply | Quote 0 Sign in to vote Hearty B, I forgot to mention that we had completed a similar task on our client's Exchange Server a few weeks back. The local certificate was slated to expire, which we resolved by executing a simple command in the Exchange Power Shell. This happened some time ago so we didn't believe that this was related...Does anybody have any idea why this may cause the issue described in my original post?: Michael Friday, May 02, 2008 8:22 PM Reply | Quote 0 Sign in to vote Hi Michael, Thank you for your post. I understand when accessing OWA via url https://server.domain.com/owa, it works fine. When using https://server.domain.com
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for exchange 2013 delivery report 400 outlook web app options a Full Time Job Ways to Get Help Expand Search Submit Close Search exchange 2013 ecp http 400 bad request Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions outlook email bad request > OWA - HTTP 400 Bad Request Want to Advertise Here? Solved OWA - HTTP 400 Bad Request Posted on 2011-01-24 Exchange SBS 1 Verified Solution 2 Comments 4,468 Views Last Modified: https://social.technet.microsoft.com/Forums/exchange/en-US/5c3b9041-a479-4979-a176-a11e8cbfc55f/http-400-bad-request-error-for-owa?forum=exchangesvrclientslegacy 2012-05-10 New server install. SBS 2008, exchange 2007, IIS7. When trying to access OWA internally via https://mail.server.com/owa can login fine and everything works fine. When trying to access externally login page is dispalyed but after entering username and password it shows HTTP 400 Bad Request - Webpage cannot be found. However using Firefox to access OWA externally it works fine. Any ideas, I https://www.experts-exchange.com/questions/26765876/OWA-HTTP-400-Bad-Request.html think it might be a certificate issue 0 Question by:Bellscape Facebook Twitter LinkedIn Google LVL 15 Best Solution byJBond2010 This certainly sounds like a certificate issue. Please refer to the link below. http://social.technet.microsoft.com/Forums/en-US/exchangesvrclients/thread/5c3b9041-a479-4979-a176-a11e8cbfc55f/ Go to Solution 2 Comments LVL 15 Overall: Level 15 Exchange 8 SBS 5 Message Accepted Solution by:JBond20102011-01-24 This certainly sounds like a certificate issue. Please refer to the link below. http://social.technet.microsoft.com/Forums/en-US/exchangesvrclients/thread/5c3b9041-a479-4979-a176-a11e8cbfc55f/ 0 LVL 4 Overall: Level 4 SBS 3 Exchange 1 Message Expert Comment by:wylie_uk2011-01-24 this is an odd error. to understand the error 'bad request' - normally this is an issue with the web browser. try another machine or browser first to see if you have the same error. next look at your firewall, somehow this could be mangling your https request. try using light mode (firefox) so see if the error is with the ful version of OWA make sure your server/exchange is fully patched. this problem can also occur if your external address that you use to access owa does not match the outlook anywhere configured address. to fix this 1) open "Exchange Management Console"; expand "Server configuration" and select "Client access
over the past months & most recently this past week with a customer. Luckily there's a fairly simple fix to the issue published https://exchangemaster.wordpress.com/tag/http-400-bad-request/ by Microsoft, but realizing not everyone remembers every Microsoft KB that gets http://www.techieshelp.com/exchange-2010-ecp-error-400/ released I thought I'd shine a spotlight on this one. Scenario As part of the migration process, when customers move their namespace from either Exchange 2007 or 2010 to 2013, HTTP connections start proxying through 2013 to the legacy Exchange Servers and some users will experience failures. bad request The potential affected workloads are: AutoDiscover Exchange Web Services (Free/Busy) ActiveSync OWA Outlook Test or new mailboxes may not be affected. Resolution The cause of this is the age old problem of Token Bloat. Users being members of too many groups or having large tokens. The fix is to implement the changes in the below Microsoft KB article "HTTP outlook web app 400 Bad Request" error when proxying HTTP requests from Exchange Server 2013 to a previous version of Exchange Server https://support.microsoft.com/en-us/kb/2988444 The interesting thing in this scenario is that the issue was not experienced in the legacy version of Exchange & even if you look at the tokens themselves, they may not seem overly large. It seems that the process of proxying Exchange traffic is much more sensitive to this issue. Also, in a recent case that went to Microsoft, even if you increase the recommended values to a value higher than your current headers it may not have the desired effect. In our case we had to set the MaxRequestBytes & MaxFieldLength values to exactly match the values in the Microsoft KB (65536 (Decimal)). For further reading, please see the below articles. Complimentary Articles "HTTP 400 - Bad Request (Request Header too long)" error in Internet Information Services (IIS) https://support.microsoft.com/en-us/kb/2020943 How to use Group Policy to add the MaxTokenSize registry entry to multiple computers https://support.microsoft.com/en-us/kb/938118 Additional Note As an FYI, another issue I commonly
2013SBS2008/2011Server 2003Server 2008Server 2012Windows VistaWindows 7Windows 8Windows 10Windows XPTerminal ServicesVMwareVeeam HomeMicrosoft Exchange 2010 Exchange 2010 ECP error 400 Exchange 2010 ECP error 400 Written by Allen White on. Posted in Exchange 2010, General IT Problem When you try to access the ECP in exchange 2010, in your web browser you see ERROR 400 BAD REQUEST. See the image below. Ive seen this on new installs of exchange 2010. error 400 bad request - Exchange 201 ECP IT Solution This is down to the security on the OWA virtual directory and the ECP not matching, the quickes way to fix this is to regenerate both virtual directories. Use the commands below to do so. Open the exchange managment shell and enter the below. Remove-OwaVirtualDirectory -Identity "owa (default Web site)" Then Remove-ECPVirtualDirectory -Identity "ecp (default Web site)" Then New-OwaVirtualDirectory Then New-ECPVirtualDirectory then Reset IIS. This will have recreated both OWA and ECP virtual directories, you will be able to login to the ECP now. If you want to learn more about powershell consider this book.   Allen WhiteAllen is a Consultant for ITPS in the North East of England and holds the following accreditations. MCSA, MCSE, MCTS, MCITP, CCA, CCSP, VCP 4,5 and HP ASE, AIS - Network Infrastructure. ITPS provides strategic IT consultancy, implementation, data centre provision and unified communications, as well as support services and workspace and disaster recovery. If you require a consultation then please contact me via the contacts section or direct on 07931222991, add me on linkedin. https://uk.linkedin.com/in/allenwhiteconsultant0001 Tags: ECP, OWA Comments (1) Frank May 23, 2011 at 8:10 am | # Also possible that you disabled the forms based authentication on the owa directory and didn't disable it on the ecp directory… Reply Leave a comment Search Solutions Categories Categories Select Category Apple Citrix Exchange 2003 Exchange 2007 Exchange 2010 Exchange 2013 Exchange 2016 General HP Procurve IGEL Linux Lync 2013 Microsoft Microsoft Office Microsoft Outlook Networking Office 2013 Office 2016 Office 365 Readers Problems SBS2008/2011 Server 2003 Server 2008 Server 2012 Symantec Terminal Services Trend Micro Veeam VMware VPS Web Web Browsers Windows 10 Windows 7 Windows 8 Windows Vista Windows XP Cannot Manage Remote Desktop Servers -The servers must be added to the server poolRemote Desktop Services.The following servers[...] Rip Blu-ray/DVD Movies Take Control of Your PDFs with Wondershare PDFelementWondershare PDFelement ove