Exchange Owa Login Error

(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語)  HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Exchange 2013 OWA Login Error HTTP 500 Exchange Server > Exchange Server 2013 - Outlook, OWA, POP, and IMAP Clients Question 0

Exchange 2003 Owa Login

Sign in to vote I have a dual Exchange server 2013 setup with two servers exchange 2007 owa login running both Café and Mailbox roles in a DAG. We are in the process of migrating from 2010 to 2013, all mailboxes

Microsoft Exchange Owa Login

have been moved, and everything is pointing to the new servers. The only thing left on 2010 is our public folder database. Here is the problem: After attempting to login to our server at https://mail.domain.ca/owa, they exchange 2010 owa login page blank get a big frown and amessage that says "something went wrong Sorry, we can't get that information right now. Please try again later. If the problem continues please contact your helpdesk" In the address bar it says httpCode=500 The weird thing is that if they change the url to https://mail.domain.ca/ecp, they can log into their "My account" just fine. Exchange ActiveSync is up and running just fine, no errors at all, and exchange 2003 owa login page doesn't appear all our outlook 2010/2013 clients are working perfectly fine as well, it is only OWA. Monday, August 12, 2013 9:14 PM Reply | Quote Answers 1 Sign in to vote I was on the phone with Microsoft for a few hours, and here is what we did to fix the problem: 1. Upgraded to the latest version of Exchange 2013 CU2 (V2). We were on the initial build (712.22), and CU2 V2 is 712.24. 2. Changed bindings of the default website to conform to Microsoft recommended settings ({http port 80 *}{http port 80 127.0.0.1}{https port 443 *}{https port 443 127.0.0.1}) 3. Insure that "Require SSL" is checked on the root of the default website 4. remove all of those "HTTP Redirect" settings that we like to use to make the users life easier So between those four items the issue seems to have been resolved. Proposed as answer by Martina_MiskovicMVP Thursday, August 15, 2013 7:02 PM Marked as answer by Simon_WuMicrosoft contingent staff, Moderator Friday, August 16, 2013 12:41 PM Thursday, August 15, 2013 6:57 PM Reply | Quote All replies 0 Sign in to vote Hi, Based on my research, you can refer to the following resolutions. Try rebuilding the OWA virtual directory To remove: Remove-OwaVirtualDirectory -Identity "exchange server name\owa (default Web site)" To build:

| general In November 2013, Cumulative Update 3 was released for Exchange Server 2013. This update resolved many issues with Exchange Server and proved to be advantageous for both

Owa Login Army

Administrator and clients. However, the users can encounter various issues with the Cumulative Updates. Issues With owa login with email address Cumulative Updates of Exchange Server 2013 With Cumulative or some other updates, the users can come across some difficulties after the installation. Some

Owa Login Url

of the issues include: Powershell shortcuts get omitted. Virtual Directories Missing of Powershell dll’s OWA, ECP or Active sync do not work properly Missing of reference from the registry Issues with the certificate Improper updation or breakage of https://social.technet.microsoft.com/Forums/exchange/en-US/08d3777c-dc03-4411-8c87-7db37d2f406a/exchange-2013-owa-login-error-http-500?forum=exchangesvrclients ASP.net In case of Cumulative update 3 and above version, the basic functionalities that get hindered are: OWA ECP Indication of the issue On installing Cumulative Update with Exchange Server 2013 and above versions either in DAG or non DAG mode, access to OWA or ECP is denied but it is found that Outlook is working effectively. If case of such scenarios either of the following errors will be generated: Event ID: 4 & 1309 : http://www.blog.edbtopst.org/ecp-and-owa-login-fails-with-error-500-in-exchange-2013.html caused due to ASP.net Error 500: caused due to login failure of OWA or ECP However, both the above mentioned errors can prevail in Exchange Server environment but we will focus on "ECP And OWA Logins Fail With Error 500 in Exchange 2013″ . Let’s now move to the reason due to which this error occurs. Cause Of The Error 500 in Exchange 2013 The main reason behind the log in failure of OWA and ECP is the mismatch of canary tokens between the client and server A canary is usually a secret token between client and Server in OWA, ECP or some other web services that is stored in the cookie collection of the browser and gets submitted with various requests which the browser sends. For each request the value of GUID stored in the URL is compared with the one stored in session state. If the value of GUID stored in these location do not match or if the value of GUID is lost from the URL, the request becomes malicious and it is blocked. As a result of it, the users will encounter “http error message 500: Internal Server Error” and the Server will come across an unexpected condition that stops it from executing the request. Functioning Of Canary Tokens In Normal Condition And At The Time Of Error Generation As mentioned above that the m

crash a few times while running diagnostics, OWA and ECP logons started showing an error. 500 Unexpected Error :( An error occurred and your request couldn't be completed. Please try again. Reseting owa login IIS, restarting the servers, clearing cookies etc had no effect. Event 4 appears in the Application log at the time of the login. Current user: 'Example.com/Test User' Request for URL 'https://server01.example.com:444/ecp/default.aspx(https://server01/ecp/)' failed with the following error: exchange owa login System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Exchange.Clients.Common.Canary15.Init(Byte[] userContextIdBinary, Byte[] timeStampBinary, String logonUniqueKey, Byte[] hashBinary, String logData) at Microsoft.Exchange.Clients.Common.Canary15..ctor(String logonUniqueKey) at Microsoft.Exchange.Clients.Common.Canary15Cookie.TryCreateFromHttpCookie(HttpCookie cookie, String logonUniqueKey, Canary15Profile profile) at Microsoft.Exchange.Clients.Common.Canary15Cookie.TryCreateFromHttpContext(HttpContext httpContext, String logOnUniqueKey, Canary15Profile profile) at Microsoft.Exchange.Management.ControlPanel.CanaryExtensions.CheckCanary15(HttpContext context, Boolean shouldRenew, String canaryName) at Microsoft.Exchange.Management.ControlPanel.CanaryExtensions.CheckCanary(HttpContext context) at Microsoft.Exchange.Management.ControlPanel.RbacModule.Application_PostAuthenticateRequest(Object sender, EventArgs e) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) at Microsoft.Exchange.Clients.Common.Canary15.Init(Byte[] userContextIdBinary, Byte[] timeStampBinary, String logonUniqueKey, Byte[] hashBinary, String logData) at Microsoft.Exchange.Clients.Common.Canary15..ctor(String logonUniqueKey) at Microsoft.Exchange.Clients.Common.Canary15Cookie.TryCreateFromHttpCookie(HttpCookie cookie, String logonUniqueKey, Canary15Profile profile) at Microsoft.Exchange.Clients.Common.Canary15Cookie.TryCreateFromHttpContext(HttpContext httpContext, String logOnUniqueKey, Canary15Profile profile) at Microsoft.Exchange.Management.ControlPanel.CanaryExtensions.CheckCanary15(HttpContext context, Boolean shouldRenew, String canaryName) at Microsoft.Exchange.Management.ControlPanel.CanaryExtensions.CheckCanary(HttpContext context) at Microsoft.Exchange.Management.ControlPanel.RbacModule.Application_PostAuthenticateRequest(Object sender, EventArgs e) at System.Web.HttpApplication.SyncEventExecutionStep.Syst