If you’re getting a 443 owa auth error.asp error, today’s blog post is here to help.
Resolve Common PC Errors
Very long, but short, please: Users cannot connect to OWA/EWS and ECP
This is the administrative site of a small company with about 10 employees. This is one standalone computer with Windows Server Std 2012 and Exchange Standard 2013 installed.
Recent success stories include installing a patch to actually allow additional USB backup drives to be added individually – http://support.microsoft.com/kb/2833738 – shortly thereafter and new ones after that. access to EWS. , which were seen by Boss Mac and myself when I logged into OWA. The login will work, but you will actually be redirected to a white blank website. ASP.NET warnings in application execution log: ASP.NET 4.0.30319.0 “Event Meaning: An unhandled exception occurred.”
I checked this, but couldn’t identify a specific fix, so with CU2 already installed, we upgraded to SP1 (aka CU4 after Due cu2 was first uninstalled due to a bug in some SP1 update). After that, OWA/ECP will not serve as a site login page – just an empty white history -ASP.NET errors will no longer be generated.
Because this server is running third party transport agents (Trend AV), I had to apply: Fix http://support.microsoft.com/kb/2938053/en-us to allow mail flow to finally exit .
Someone pointed out that updatecas.ps1 was in the swap bin directory, which I unfortunately did:
Now OWA/ECP launches a huge login page, but be aware that login fails with error:
“You may have entered an incorrect customer name or password. Please try again.”
The username and password are NOT incorrect and have been reset to confirm they are correct. I tried multiple accounts using different formats for specific usernames:
I have tried various methods to allow you to access the server whether or not you use multiple web browsers and also client computers
Everyone gives the above error for this and other unsecured debts (for example, a domain administrator).
Microsoft Support has a section with instructions for those whoo Having problems after restoring the OWA/ECP virtual website: http://support.microsoft.com/kb/2778897/en-gb
set-Owavirtualdirectory -identity “E15MBXowa (Exchange backend)” -WindowsAuthentication $True -Basicauthentication $false -Formsauthentication $false
Set-EcpVirtualDirectory -Identity “E15MBXecp (Exchange backend)” $true -windowsauthentication -FormsAuthentication $false
Perhaps I checked that the virtual directory authentication capabilities match the idea suggested by MS: http://technet.microsoft.com/en-us/library/gg247612%28v=exchg.150%29.aspx< / p>
When I try to log in, this error does not appear in the application itself or in the system event log. In the security event log, the user id I used, also known as the Exchange GUID (found as the correct result “username get-mailbox | schoolname fl,exchangeguid”) still failed or something.
However, when trying to find the user account, ID 4625 (validation failed) is logged.