After Power failure, OWA and ECP are no longer working - Exchange 2013

Posted on 2014-01-11
Last Modified: 2014-01-15
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.
Question by:Avreon
  • 5
  • 2
  • 2
  • +2
LVL 31

Expert Comment

by:Gareth Gudger
ID: 39774371
Anything in Event Viewer? All your services started?

Expert Comment

by:nashim khan
ID: 39774374

Please see the below link. 

And one same issue link is available on EE see the same here.
LVL 25

Expert Comment

ID: 39774383
This happens when your IS service is down.
Please make usre all your services started.
Edgartown IT Case Study

Learn about Edgartown's quest to ensure the safety and security of the entire town's employee and citizen data. Read the case study!


Author Comment

ID: 39774408
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.
LVL 25

Expert Comment

ID: 39774429

Author Comment

ID: 39774628
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.

Author Comment

ID: 39775119
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.FileNotFoundException: Could not load file or assembly 'Microsoft.Exchange.FrontEndHttpProxy' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.Exchange.FrontEndHttpProxy'
   at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMarkHandle stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName, ObjectHandleOnStack type)
   at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName)
   at System.Type.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase)
   at System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase)
   at System.Web.Configuration.HandlerFactoryCache.GetTypeWithAssert(String type)
   at System.Web.Configuration.HandlerFactoryCache.GetHandlerType(String type)
   at System.Web.Configuration.HandlerFactoryCache..ctor(String type)
   at System.Web.HttpApplication.GetFactory(String type)
   at System.Web.HttpApplication.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
LVL 12

Expert Comment

by:Md. Mojahid
ID: 39775778

Author Comment

ID: 39777727
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)

Accepted Solution

nashim khan earned 500 total points
ID: 39778535

Author Closing Comment

ID: 39783900
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.

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

685 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question