Exchange 2013 - Server Error '/ecp' Application

We just started getting this error when trying to log on to the Exchange Admin Center.

We have 6 Exchange 2013 CU7 and it is happening to all of them using https://servername/ecp

ECPerror.JPG
nourbenAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Seth SimmonsSr. Systems AdministratorCommented:
what changed?  suspicious that they all have the issue suddenly
did you just apply CU7?
nourbenAuthor Commented:
No it was a fresh install with CU7, and if I knew what changed I would have fixed the problem.
Simon Butler (Sembee)ConsultantCommented:
Knowing what changed doesn't mean you would be able to fix the problem.

Unfortunately that is a very generic error. What was the last thing changed? The fact that is happening across all servers would suggest there has been a global change somewhere, probably thought to be unrelated to Exchange.

Does EMS work?
Does OWA work?

Simon.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

nourbenAuthor Commented:
I am just stressed out, I apologize for my response.

We added these 6 servers to our exchange 2007 environment last month with no mailboxes, and no coexistence set yet.

We hardened the OS/IE, IIS and everything was fine for weeks, then couple days ago I couldn't get in.

I cannot test OWA because we don't have any mailbox on these servers but EMS is fine on all servers.
Simon Butler (Sembee)ConsultantCommented:
"We hardened the OS/IE, IIS and everything was fine for weeks, then couple days ago I couldn't get in."

What exactly did you do with IIS?

IIS in a default configuration doesn't need to be hardened. The combination of Exchange and IIS has never been compromised - it has always been through another app.

Simon.
nourbenAuthor Commented:
Government follow DoD Stig or Benchmark.

But after that it worked for weeks.
nourbenAuthor Commented:
Installed SCOM and this is the error I see

Error for ECP
Exchange Admin Center is failing to respond to ping request on Mailbox server ExchServer01. Availability has dropped to 4REPLACE_PERCENT_SIGN. You can find protocol level traces for the failures on D:\Program Files\Microsoft\Exchange Server\V15\Logging\Monitoring\ECP\EacBackEndPingProbe. Incident start time: 3/20/2015 6:21:40 PM Last failed result: Failing Component - Ecp Failure Reason - UnexpectedHttpResponseCode Exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Exchange.Net.MonitoringWebClient.ScenarioException: Microsoft.Exchange.Net.MonitoringWebClient.ScenarioException: Failure source: Ecp Failure reason: UnexpectedHttpResponseCode Failing component:Ecp Exception hint: UnexpectedHttpCode: Redirect Inner exception: Microsoft.Exchange.Net.MonitoringWebClient.UnexpectedStatusCodeException Expected status codes: OK Actual status codes: Redirect Microsoft.Exchange.Net.MonitoringWebClient.UnexpectedStatusCodeException: Unexpected response code received. WebExceptionStatus: Success GET https://localhost:444/ecp/exhealth.check HTTP/1.1 User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; MSEXCHMON; ACTIVEMONITORING) Accept: */* Cache-Control: no-cache X-FeToBeTimeout: 100 X-IsFromCafe: 1 Cookie: HTTP/1.1 302 Redirect X-UA-Compatible: IE=10 Content-Length: 166 Date: Thu, 26 Mar 2015 12:35:56 GMT Location: /ecp/error.aspx?aspxerrorpath=/ecp/exhealth.check Server: Microsoft-IIS/8.5 X-Powered-By: ASP.NET <html><head><title>Object moved</title></head><body> <h2>Object moved to <a href="/ecp/error.aspx?

Error for OWA:
Description:
Outlook Web Access logon is failing on Mailbox server ExchServer01. Availability has dropped to 0REPLACE_PERCENT_SIGN. You can find protocol level traces for the failures on D:\Program Files\Microsoft\Exchange Server\V15\Logging\Monitoring\OWA\MailboxProbe. Incident start time: 3/20/2015 6:22:53 PM Last failed result: Failing Component - Owa Failure Reason - OwaErrorPage Exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Exchange.Net.MonitoringWebClient.ScenarioException: Microsoft.Exchange.Net.MonitoringWebClient.ScenarioException: Failure source: Owa Failure reason: OwaErrorPage Failing component:Owa Exception hint: OwaErrorPage: System.Web.HttpUnhandledException Inner exception: Microsoft.Exchange.Net.MonitoringWebClient.OwaErrorPageException ErrorPageFailureReason: OwaErrorPage, Exception type: System.Web.HttpUnhandledException Microsoft.Exchange.Net.MonitoringWebClient.OwaErrorPageException: The response contained an OWA error page WebExceptionStatus: Success GET https://localhost:444/owa/ HTTP/1.1 User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; MSEXCHMON; ACTIVEMONITORING; OWADEEPTEST) Accept: */* Cache-Control: no-cache Cookie: ClientId=KULSMSRBYKEULRCOXGKNW; $Path=/; UC=a296b3201cbb4dc0b96fae4fd...; $Path=/ X-OWA-ActionName: Monitoring X-MonitoringInstance: 79214237-0154-f865-b7cf-4bd453074563 X-FeToBeTimeout: 100 X-CommonAccessToken: VgEAVAdXaW5kb3dzQwBBCEtlcmJlcm9zTB5OUkNET01BSU5cSGVhbHRoTWFpbGJveDliYzc5MjhVL1MtMS01LTIxLTE5MjI3NzE5MzktMTU4MTY2Mzg1NS0xNjE3Nzg3MjQ1LTk3NTE3RwkAAAAHAAAALVMtMS01LTIxLTE5MjI3NzE5MzktMTU4MTY2Mzg1NS0xNjE3Nzg3MjQ1LTUxMwcAAAAHUy0xLTEtMAcAAAAHUy0xLTUtMgcAAAAIUy0xLTUtMTEHAAAACFMtMS01LTE1BwAAwBFTLTEtNS01LTAtMjQ4NjI1MgcAAAAvUy0xLTUtMjEtMTkyMjc3MTkzOS0xNTgxNjYzODU1LTE2MTc3ODcyNDUtOTAyMjIHAAAAL1MtMS01LTIxLTE5MjI3NzE5MzktMTU4MTY2Mzg1NS0xNjE3Nzg3MjQ1LTg4MjA2BwAAAAhTLTEtMTgtMkUAAAAA HTTP/1.1 400 BadRequest Pragma: no-cache Transfer-Encoding: chunked X-Content-Type-Options: nosniff request-id: 20634693-2849-4bea-9aeb-f4a15655f8a8 X-OWA-Version: 15.0.1044.29 X-OWA-OWSVersion: V2_22 X-OWA-MinimumSupportedOWSVersion: V2_6 X-Frame-Options: SAMEORIGIN X-OWA-Error: System.Web.HttpUnhandledException X-BackEnd-Begin: 2015-03-26T08:40:48.555 X-BackEnd-End: 2015-03-26T08:40:48.586 Persistent-Auth: true X-DiagInfo: HQPWMSMRS05 X-BEServer: HQPWMSMRS05 X-UA-Compatible: IE=EmulateIE7 Cache-Control: no-cache, no-store Content-Type: text/html Date: Thu, 26 Mar 2015 12:40:48 GMT Expires: -1 Set-Cookie: X-OWA-CANARY=Y_bdrKfs0ki8rcZ46ibyl80Ok...; path=/; secure Server: Microsoft-IIS/8.5 WWW-Authenticate: Negotiate oRswGaADCgEAoxIEEAEAAABDh+CIwTbjqQAAAAA= X-Powered-By: ASP.NET Bad Request Response time: 0.0312629s ---> Microsoft.Exchange.Net.MonitoringWebClient.OwaErrorPageException: Microsoft.Exchange.Net.MonitoringWebClient.OwaErrorPageException ErrorPageFailureReason: OwaErrorPage, Exception type: System.Web.HttpUnhandledException Microsoft.Exchange.Net.MonitoringWebClient.OwaErrorPageException: The response contained an OWA error page WebExceptionStatus: Success GET https://localhost:444/owa/ HTTP/1.1 User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; MSEXCHMON; ACTIVEMONITORING; OWADEEPTEST) Accept: */* Cache-Control: no-cache Cookie: ClientId=KULSMSRBYKEULRCOXGKNW; $Path=/; UC=a296b3201cbb4dc0b96fae4fd...; $Path=/ X-OWA-ActionName: Monitoring X-MonitoringInstance: 79214237-0154-f865-b7cf-4bd453074563 X-FeToBeTimeout: 100 X-CommonAccessToken: VgEAVAdXaW5kb3dzQwBBCEtlcmJlcm9zTB5OUkNET01BSU5cSGVhbHRoTWFpbGJveDliYzc5MjhVL1MtMS01LTIxLTE5MjI3NzE5MzktMTU4MTY2Mzg1NS0xNjE3Nzg3MjQ1LTk3NTE3RwkAAAAHAAAALVMtMS01LTIxLTE5MjI3NzE5MzktMTU4MTY2Mzg1NS0xNjE3Nzg3MjQ1LTUxMwcAAAAHUy0xLTEtMAcAAAAHUy0xLTUtMgcAAAAIUy0xLTUtMTEHAAAACFMtMS01LTE1BwAAwBFTLTEtNS01LTAtMjQ4NjI1MgcAAAAvUy0xLTUtMjEtMTkyMjc3MTkzOS0xNTgxNjYzODU1LTE2MTc3ODcyNDUtOTAyMjIHAAAAL1MtMS01LTIxLTE5MjI3NzE5MzktMTU4MTY2Mzg1NS0xNjE3Nzg3MjQ1LTg4MjA2BwAAAAhTLTEtMTgtMkUAAAAA HTTP/1.1 400 BadRequest Pragma: no-cache Transfer-Encoding: chunked X-Content-Type-Options: nosniff request-id: 20634693-2849-4bea-9aeb-f4a15655f8a8 X-OWA-Version: 15.0.1044.29 X-OWA-OWSVersion: V2_22 X-O
nourbenAuthor Commented:
Problem Solved
Culprit: The security update for Exchange 2013 KB3040856 created 2 folders with empty sub-folders and that was the issue.
-Folder 15.0.1044.29 in C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\ecp
-Folder 15.0.1044.27 in C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa

Resolution:
Uninstalled the Security Update
Moved those 2 folders somewhere else (just in case)
Re-created ECP and OWA Virtual Directories (Default and BackEnd)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
nourbenAuthor Commented:
In our environment, that what happened
Anil PujariCommented:
Uninstalling Security updates solved the issue.
AMULRAJ SCommented:
we are using Exchange Server 2013 , past one week the exchange server was not working properly . the Error is

Server Error in '/ecp' Application.

Could not load file or assembly 'Microsoft.Exchange.HttpProxy.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
  Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

 Exception Details: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Exchange.HttpProxy.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

Source Error:


 An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.  

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.Exchange.HttpProxy.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' could not be loaded.



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].

 

Stack Trace:



[FileNotFoundException: Could not load file or assembly 'Microsoft.Exchange.HttpProxy.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.]
   Microsoft.Exchange.HttpProxy.HttpProxySettings.Prefix(String appSettingName) +0
   Microsoft.Exchange.HttpProxy.FbaModule..cctor() +126

[TypeInitializationException: The type initializer for 'Microsoft.Exchange.HttpProxy.FbaModule' threw an exception.]
   Microsoft.Exchange.HttpProxy.FbaModule..ctor() +0

[TargetInvocationException: Exception has been thrown by the target of an invocation.]
   System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck) +0
   System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) +159
   System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) +256
   System.Activator.CreateInstance(Type type, Boolean nonPublic) +127
   System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark) +14297981
   System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes) +198
   System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture) +28
   System.Web.HttpRuntime.CreateNonPublicInstance(Type type, Object[] args) +83
   System.Web.HttpApplication.BuildIntegratedModuleCollection(List`1 moduleList) +334
   System.Web.HttpApplication.GetModuleCollection(IntPtr appContext) +1262
   System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +133
   System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +304
   System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +404
   System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +475

[HttpException (0x80004005): Exception has been thrown by the target of an invocation.]
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +12617668
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +159
   System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +12457285

 


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.34209
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.