Avreon
asked on
After Power failure, OWA and ECP are no longer working - Exchange 2013
We experienced a power failure today and unfortunately, the UPS didn't last long enough. The server was in the process of shutting down when the UPS shut down. After the power was restored, the server appeared to come up properly. However, I am no longer able to access OWA or ECP via browser.
Initially, when I would attempt to login (as Administrator), I was just returned to the login page. However, after doing some research, I changed the Authentication mode from "Basic Authentication" to "Windows Authentication" in IIS for both the owa and ecp virtual. Now, I am getting "The user name or password you entered isn't correct. Try entering it again."
I get this login error regardless of which username/password I use. Please help.
Initially, when I would attempt to login (as Administrator), I was just returned to the login page. However, after doing some research, I changed the Authentication mode from "Basic Authentication" to "Windows Authentication" in IIS for both the owa and ecp virtual. Now, I am getting "The user name or password you entered isn't correct. Try entering it again."
I get this login error regardless of which username/password I use. Please help.
Gareth Gudger
Anything in Event Viewer? All your services started?
Hi,
Please see the below link.
http://support.microsoft.com/kb/827614
And one same issue link is available on EE see the same here.
https://www.experts-exchange.com/questions/27831774/Can't-login-to-Exchange-OWA-The-user-name-or-password-you-entered-isn't-correct-Try-entering-it-again.html
Please see the below link.
http://support.microsoft.com/kb/827614
And one same issue link is available on EE see the same here.
https://www.experts-exchange.com/questions/27831774/Can't-login-to-Exchange-OWA-The-user-name-or-password-you-entered-isn't-correct-Try-entering-it-again.html
This happens when your IS service is down.
Please make usre all your services started.
Please make usre all your services started.
ASKER
Nothing stands out in the Event Viewer
I am able to login via RDP to the Exchange Server using the same username/password without issue. This only appears to be an issue with OWA and ECP
Outlook connecting internal does not have any issue
Windows Phone users are able to access their e-mail both internally and externally
All Microsoft Exchange Services are up and running
E-mail is flowing both inbound and outbound
I suspect that something got corrupt or reconfigured in IIS during the impromptu power loss/shutdown. I just don't know where to look next.
Please check this it may help as it is similar to your case I guess
http://social.technet.microsoft.com/Forums/exchange/en-US/1736b5ab-e69b-4637-aa59-f2d9bd54ead2/unable-to-access-exchange-2013-eacecp-webpage?forum=exchangesvrdeploy
http://social.technet.microsoft.com/Forums/exchange/en-US/1736b5ab-e69b-4637-aa59-f2d9bd54ead2/unable-to-access-exchange-2013-eacecp-webpage?forum=exchangesvrdeploy
ASKER
MAS - I reviewed that article and tried several of the options suggested (including rebuilding the ECP and OWA sub-folders. Unfortunately, I am still stuck.
Can anyone confirm what the Authentication settings should be for the OWA vdir? When I rebuilt the OWA virtual directory, the Authetication settings were reverted back to "Basic Authentication" I have tried to switch it back to Windows Authentication and added NTLM and Negotiate as providers. This still does not work.
Can anyone confirm what the Authentication settings should be for the OWA vdir? When I rebuilt the OWA virtual directory, the Authetication settings were reverted back to "Basic Authentication" I have tried to switch it back to Windows Authentication and added NTLM and Negotiate as providers. This still does not work.
ASKER
I'm not sure if this is related, but it sounds like something is going wrong. This morning there were two series of errors in the Application Event log:
[Oab] An internal server error occurred. The unhandled exception was: System.IO.FileNotFoundExce
File name: 'Microsoft.Exchange.FrontE
at System.RuntimeTypeHandle.G
at System.RuntimeTypeHandle.G
at System.Type.GetType(String
at System.Web.Compilation.Bui
at System.Web.Configuration.H
at System.Web.Configuration.H
at System.Web.Configuration.H
at System.Web.HttpApplication
at System.Web.HttpApplication
at System.Web.HttpApplication
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\F
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\F
[Oab] An internal server error occurred. The unhandled exception was: System.IO.FileNotFoundExce
File name: 'Microsoft.Exchange.FrontE
at System.RuntimeTypeHandle.G
at System.RuntimeTypeHandle.G
at System.Type.GetType(String
at System.Web.Compilation.Bui
at System.Web.Configuration.H
at System.Web.Configuration.H
at System.Web.Configuration.H
at System.Web.HttpApplication
at System.Web.HttpApplication
at System.Web.HttpApplication
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\F
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\F
Check your service every services are running and also try restart iis manually.
Refer for more: http://social.technet.microsoft.com/Forums/exchange/en-US/1736b5ab-e69b-4637-aa59-f2d9bd54ead2/unable-to-access-exchange-2013-eacecp-webpage?forum=exchangesvrdeploy
Refer for more: http://social.technet.microsoft.com/Forums/exchange/en-US/1736b5ab-e69b-4637-aa59-f2d9bd54ead2/unable-to-access-exchange-2013-eacecp-webpage?forum=exchangesvrdeploy
ASKER
All "Automatic" services are running. All Microsoft ExchangeI also executed the iisreset command to restart IIS. Users are still unable to login via OWA (ECP is also not working).
One thing I did want to mention... When I attempt to login to ECP, the URL actually changes to "https://servername/owa/auth/logon.aspx?replaceCurrent=1&url=https%3a%2f%2fservername%2fecp%2f". I'm assuming that this is correct. It looks like ECP is just using the same authentication engine that OWA uses.
In any case neither OWA or ECP are working. I get the login page, but whenever I attempt to login, I get the "The user name or password you entered isn't correct. Try entering it again." As a reminder, this was all working correctly prior to the power interruption.
I suspect that the issue lies in the OWA authentication configuration. (i.e. the OWA authentication isn't able to validate the credentials provided for some reason)
One thing I did want to mention... When I attempt to login to ECP, the URL actually changes to "https://servername/owa/auth/logon.aspx?replaceCurrent=1&url=https%3a%2f%2fservername%2fecp%2f". I'm assuming that this is correct. It looks like ECP is just using the same authentication engine that OWA uses.
In any case neither OWA or ECP are working. I get the login page, but whenever I attempt to login, I get the "The user name or password you entered isn't correct. Try entering it again." As a reminder, this was all working correctly prior to the power interruption.
I suspect that the issue lies in the OWA authentication configuration. (i.e. the OWA authentication isn't able to validate the credentials provided for some reason)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It took a few different suggestions to finally find where the issue was at. Ultimately, it was as I expected, a security authentication mode configuration issue. For some reason, when the power interruption occurred, the authentication mode configuration somehow got out of sync. After following the PowerShell steps to reset the authentication modes on OWA and ECP, I am now able to access both sites.