Exchange 2010 Owa Error 400 Bad Request
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 outlook web app bad request Versions - Outlook, OWA, POP, and IMAP Clients Question 1 Sign in to 400 outlook web app options exchange 2013 vote Good afternoon everyone,I have an intersting issue at one of my client sites that I'm hoping to get some owa bad request exchange 2013 insight on. The client 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
Bad Request Error Outlook Web Access
page:https://server.domain.com/exchangeThey receive an error in Internet 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 exchange 2013 ecp http 400 bad request case this time or not. My thoughts lead me to 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, Than
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 exchange 2010 owa bad request Freelance Project Hire for a Full Time Job Ways to Get Help
Exchange 2013 Delivery Report 400 Outlook Web App Options
Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store
/owa/auth.owa Bad Request
Headlines Experts Exchange > Questions > OWA - HTTP 400 Bad Request Want to Advertise Here? Solved OWA - HTTP 400 Bad Request Posted on 2011-01-24 Exchange SBS 1 Verified https://social.technet.microsoft.com/Forums/exchange/en-US/5c3b9041-a479-4979-a176-a11e8cbfc55f/http-400-bad-request-error-for-owa?forum=exchangesvrclientslegacy Solution 2 Comments 4,434 Views Last Modified: 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 https://www.experts-exchange.com/questions/26765876/OWA-HTTP-400-Bad-Request.html to access OWA externally it works fine. Any ideas, I 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 doe
Highly Available (HA) Microsoft Exchange 2013 setup was designed and installed by Dave Stork. I have installed various cumulative updates on this setup and almost everything went https://dirteam.com/sergio/2014/01/21/bad-request-http-400-error-in-exchange-2013-owaecp/ without a hitch. Since then, I moved on. The issue Last week our IT deparment had a big problem with Outlook Web App (OWA) on Microsoft Exchange 2013. It was not https://lyncdude.com/2013/02/07/cannot-access-exchange-contorl-panel-ecp-in-exchange-server-2013/ working anymore and it was inaccessible for all our 500+ employees. However, all other services kept on working normally (ActiveSync, Outlook Anywhere, etc.). Since I’m not managing this Microsoft Exchange 2013 bad request environment anymore, I wasn’t fully aware of this problem, until the IT Department asked me to take a look at it, in the hope that I could fix it. In the end, we managed to fix this problem without too many complications. I have to thank my colleague and partner in crime, Chris Petit (@christiaanpetit) for his insights and tips. He was outlook web app a great help during this ordeal at work. The problem Our IT department changed the authentication option on the ECP virtual directory and suddenly Outlook web access was not working anymore. All our employees working in the field use Outlook Web App to communicate. You can just imagine how frustrating this can be for customers. On smartphone devices, colleagues could see the nice Outlook Web App login page of Microsoft Exchange 2013, only to find out that it doesn’t work. After providing their (correct) credentials, they received this error: “Outlook web app didn’t initialize. If the problem continues please contact your helpdesk. Couldn’t find a base theme (folder name=base)” In the eventviewer we saw a lot of these error messages: With this informationin mind, we concluded that some web technology and perhaps some webservice was at fault. The solution The solution to this problem is a neat one. On the internet we read blogposts telling us that we needed to recreate the Outlook Web App (OWA) and Exchange Control Panel (ECP) virtual directories. We did do this, following the instructions from this blogpost: http://exchangeonline.in/re-create-owa-virtual-directory-exchange-2013/ But… recreating the virtual directories did not solve anything for us
couple of messages on Twitter from Engineers saying they cannot access the ECP page after they finished configuring the Virtual Directories. Problem: When trying to access the ECP , it takes you to the OWA page and after providing your username and password it gives you a blank "HTTP 400 Error" page. Cause: You missed up your authentications methods my friend Solution: make sure that the authentication methods used by OWA and ECP are matching this is done by running the following > Get-owavirtualdirectory | fl make sure that you using "Form based Authentication" and "Basic Authentication" do the same with ECP using the following command line > Get-ECPVirtualDirectory | fl If not then you just need to reconfigure the Authentications on both Virtual Directories, DONNOT use IIS use Exchange Management Shell. For owa use the following >Set-owavirtualdirectory -identity "owa