Outlook Web Access Error 400
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 exchange 2013 owa 400 bad request Versions of Exchange > Exchange Previous Versions - Outlook, OWA, POP, and
Outlook Email Bad Request
IMAP Clients Question 1 Sign in to vote Good afternoon everyone,I have an intersting issue at one outlook web access bad request of my client sites that I'm hoping to get some insight on. The client in question has an Microsoft Exchange Server 2007 that has been functioning fine for the
Outlook Bad Request Android
past couple years. The problem is that when users attempt to access the 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 owa bad request after login 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 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 th
VIAcode Contact Us Sign In Welcome to Management Pack Wiki! http://mpwiki.viacode.com/default.aspx?g=posts&t=4985 Your documentation pro for SCOM Management Packs SCOM MP Tuner MP Wiki Management Pack Import your MP! ERROR Public MPWiki » Page not found Page not found The page you are looking for might have been removed or is temporarily unavailable. © VIAcode. All Rights Reserved
Highly Available (HA) Microsoft Exchange 2013 setup was designed and installed by Dave Stork. I have installed various cumulative updates on https://dirteam.com/sergio/2014/01/21/bad-request-http-400-error-in-exchange-2013-owaecp/ this setup and almost everything went 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 working anymore and it was inaccessible for all our 500+ employees. However, all other services kept on working normally (ActiveSync, bad request Outlook Anywhere, etc.). Since I’m not managing this Microsoft Exchange 2013 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 outlook web access thank my colleague and partner in crime, Chris Petit (@christiaanpetit) for his insights and tips. He was 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 tell