For several reasons after installation updates/KB (for example KB4536987) you may faced with some backfires. I collected 3 type of issues and their fixes.
Issue #1 — Lack os styles on ECP page
After authentication on ECP page you may see only text and hyperlinks without any images and styles.
How to fix
Run the script «C:Program FilesMicrosoftExchange ServerV15BinUpdateCas.ps1» or do following manual steps:
- Go to «C:Program FilesMicrosoftExchange ServerV15ClientAccessecp» folder and find the folder with latest version number of your server (e.g. «15.1.1913.7») and it will be empty.
- Open folder with previous version number (e.g. «15.1.1913.5») and copy all data to the new folder (e.g. «15.1.1913.7»).
- Restart IIS. Reload the ECP page.
Issue #2 — Something went wrong with OWA
After authentication on OWA page you may get an error «Something went wrong».
How to fix
Run the script «C:Program FilesMicrosoftExchange ServerV15BinUpdateCas.ps1» or do following manual steps:
- Go to «C:Program FilesMicrosoftExchange ServerV15ClientAccessOwaprem» folder and find the folder with latest version number of your server (e.g. «15.1.1913.7») and it will be empty.
- Open folder with previous version number (e.g. «15.1.1913.5») and copy all data to the new folder (e.g. «15.1.1913.7»).
- Restart IIS. Reload the OWA page.
Issue #3 — Server Error in ‘/ecp’ Application
After authentication on ECP page you may get an error «Could not load file or assembly ‘Microsoft.Exchange.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=***’ or one of its dependencies. The system cannot find the file specified.».
How to fix
- Check the value of «BinSearchFolders» variable in «Exchange Back End — ECP» application settings. If the value is «%ExchangeInstallDir%» change it to «C:Program FilesMicrosoftExchange ServerV15bin;C:Program FilesMicrosoftExchange ServerV15binCmdletExtensionAgents;C:Program FilesMicrosoftExchange ServerV15ClientAccessOwabin«.
- Restart IIS. Reload the ECP page.
How to avoid all of those issues
- Run the security update at an elevated command prompt.
- Before run the update stop all Microsoft Exchange services and set startup type to manual.
Continuing my exchange 2010 troubleshooting notes.
Server Error in ‘/ecp’ Application (EAC in Exchange 2013)
Issue: When we try to login to the Exchange Control Panel (ECP) we will get the following error:
Server Error in ‘/ecp’ Application
Runtime Error
Description: An exception occurred while processing your request. Additionally, another exception occurred while executing the custom error page for the first exception. The request has been terminated.
We get the following event ID for ASP.NET
Log Name: Application
Source: ASP.NET 4.0.30319.0
Event ID: 1310
Task Category: Web Event
Level: Warning
Keywords: Classic
User: N/A
Description:
Event code: 3008
Event message: A configuration error has occurred.
Event time: 5/1/2015 8:11:30 PM
Event ID: 2f6f040d6c6648d5b546aa5a48f76f39
Event sequence: 1
Event occurrence: 1
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/2/ROOT/ecp-106-130719545516088102
Trust level: Full
Application Virtual Path: /ecp
Application Path: D:Program FilesMicrosoftExchange ServerV15ClientAccessecp
Machine name: EXCHANGE
Process information:
Process ID: 13044
Process name: w3wp.exe
Account name: NT AUTHORITYSYSTEM
Exception information:
Exception type: ConfigurationErrorsException
Exception message: Could not load file or assembly ‘Microsoft.Exchange.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find the file specified.
at System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, XmlNode node, Boolean checkAptcaBit, Boolean ignoreCase)
at System.Web.Configuration.Common.ModulesEntry.SecureGetType(String typeName, String propertyName, ConfigurationElement configElement)
at System.Web.Configuration.Common.ModulesEntry..ctor(String name, String typeName, String propertyName, ConfigurationElement configElement)
at System.Web.HttpApplication.BuildIntegratedModuleCollection(List`1 moduleList)
at System.Web.HttpApplication.GetModuleCollection(IntPtr appContext)
at System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers)
at System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context)
at System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context)
at System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext)
Could not load file or assembly ‘Microsoft.Exchange.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find the file specified.
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.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, XmlNode node, Boolean checkAptcaBit, Boolean ignoreCase)
Request information:
Request URL: https://Exchange.domain.com:444/ecp/
Request path: /ecp/
User host address: ::1
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITYSYSTEM
Thread information:
Thread ID: 385
Thread account name: NT AUTHORITYSYSTEM
Is impersonating: False
Stack trace: at System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, XmlNode node, Boolean checkAptcaBit, Boolean ignoreCase)
at System.Web.Configuration.Common.ModulesEntry.SecureGetType(String typeName, String propertyName, ConfigurationElement configElement)
at System.Web.Configuration.Common.ModulesEntry..ctor(String name, String typeName, String propertyName, ConfigurationElement configElement)
at System.Web.HttpApplication.BuildIntegratedModuleCollection(List`1 moduleList)
at System.Web.HttpApplication.GetModuleCollection(IntPtr appContext)
at System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers)
at System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context)
at System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context)
at System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext)
In addition to above if you have a SCOM server the following errors will get triggered:
ECP Error in SCOM:
Exchange Admin Center is failing to respond to ping request on Mailbox server EXCHANGE-SERVER-MAIN. Availability has dropped to 4REPLACE_PERCENT_SIGN. You can find protocol level traces for the failures on D:Program FilesMicrosoftExchange ServerV15LoggingMonitoringECPEacBackEndPingProbe. Incident start time: 5/1/2015 8:11:30 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.checkHTTP/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: 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?
OWA Error in SCOM:
Description:
Outlook Web Access logon is failing on Mailbox server EXCHANGE-SERVER-MAIN. Availability has dropped to 0REPLACE_PERCENT_SIGN. You can find protocol level traces for the failures on D:Program FilesMicrosoftExchange ServerV15LoggingMonitoringOWAMailboxProbe. Incident start time: 5/1/2015 8:11:30 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 400BadRequest 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: Exch13Server X-BEServer: Exch13Server 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
Resolution:
=> Issue appears to be with the Exchange 2013 KB3040856 Security update. It had created 2 folders with empty sub-folders which was causing the issue.
=> Location of 2 folders which the update created:
-Folder 15.0.1044.29 in C:Program FilesMicrosoftExchange ServerV15ClientAccessecp
-Folder 15.0.1044.27 in C:Program FilesMicrosoftExchange ServerV15ClientAccessOwa
=>Uninstall the Security Update KB3040856
=>Move the above 2 folders to a different location (just take a copy as backup)
=>Re-create the ECP and OWA Virtual Directories (Default and BackEnd).
===================================================================================
“Your request couldn’t be completed. Please try again in a few minutes.” If I try to create a new rule, I get an error message “access denied”.
Issue: After a recovery in Exchange 2013 (CU7), when we try to access the Exchange Control Panel (ECP), try to create new Transport rules we get the following error:
“Your request couldn’t be completed. Please try again in a few minutes.” If I try to create a new rule, I get an error message “access denied”.
Having said that we will still be able to successfully create Transport rules using the Exchange Management Shell without any errors.
We get the following error in the log:
Current user: ‘mydomain.local/MyBusiness/Users/Admin’
Web service call ‘https://exchangeserver.mydomain.local:444/ecp/RulesEditor/TransportRules.svc/GetList?msExchEcpCanary=p2Zp1y_1kESsrueBkDB6T1r0z46NLdII4Q_D6294gRCkKBixfp0OnWr9OfSQ9SO205BuS7NQnns.(https://remote.mydomain.com/ecp/RulesEditor/TransportRules.svc/GetList?msExchEcpCanary=p2Zp1y_1kESsrueBkDB6T1r0z46NLdII4Q_D6294gRCkKBixfp0OnWr9OfSQ9SO205BuS7NQnns.)’ failed with the following error:
System.Security.SecurityException: Request for principal permission failed.
at System.Security.Permissions.PrincipalPermission.ThrowSecurityException()
at System.Security.Permissions.PrincipalPermission.Demand()
at Microsoft.Exchange.Management.ControlPanel.WebServiceParameters.set_Item(String cmdletParameterName, Object value)
at Microsoft.Exchange.Management.ControlPanel.ResultSizeFilter.set_ResultSize(Int32 value)
at ReadTransportRuleFilterFromJson(XmlReaderDelegator , XmlObjectSerializerReadContextComplexJson , XmlDictionaryString , XmlDictionaryString[] )
at System.Runtime.Serialization.Json.JsonClassDataContract.ReadJsonValueCore(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)
at System.Runtime.Serialization.Json.JsonDataContract.ReadJsonValue(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)
at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)
at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Type declaredType, DataContract dataContract, String name, String ns)
at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName)
at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
at System.Runtime.Serialization.Json.DataContractJsonSerializer.ReadObject(XmlDictionaryReader reader, Boolean verifyObjectName)
at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.PartInfo.ReadObject(XmlDictionaryReader reader, XmlObjectSerializer serializer)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameterPart(XmlDictionaryReader reader, PartInfo part)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameters(XmlDictionaryReader reader, PartInfo[] parts, Object[] parameters, PartInfo returnInfo, Object& returnValue)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeBodyCore(XmlDictionaryReader reader, Object[] parameters, Boolean isRequest)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeBody(XmlDictionaryReader reader, MessageVersion version, String action, MessageDescriptionmessageDescription, Object[] parameters, Boolean isRequest)
at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeBodyContents(Message message, Object[] parameters, Boolean isRequest)
at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeRequest(Message message, Object[] parameters)
at System.ServiceModel.Dispatcher.DemultiplexingDispatchMessageFormatter.DeserializeRequest(Message message, Object[] parameters)
at System.ServiceModel.Dispatcher.UriTemplateDispatchFormatter.DeserializeRequest(Message message, Object[] parameters)
at Microsoft.Exchange.Management.ControlPanel.DiagnosticsBehavior.SerializationPerformanceTracker.DeserializeRequest(Message message, Object[] parameters)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.DeserializeInputs(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
The action that failed was:
Demand
The type of the first permission that failed was:
System.Security.Permissions.PrincipalPermission
The first permission that failed was:
<IPermission mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″
version=”1″>
<Identity Authenticated=”true”
Role=”Get-TransportRule?ResultSize@R:Organization”/>
</IPermission>
The demand was for:
<IPermission mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″
version=”1″>
<Identity Authenticated=”true”
Role=”Get-TransportRule?ResultSize@R:Organization”/>
</IPermission>
The assembly or AppDomain that failed was:
mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
at System.Security.Permissions.PrincipalPermission.ThrowSecurityException()
at System.Security.Permissions.PrincipalPermission.Demand()
at Microsoft.Exchange.Management.ControlPanel.WebServiceParameters.set_Item(String cmdletParameterName, Object value)
at Microsoft.Exchange.Management.ControlPanel.ResultSizeFilter.set_ResultSize(Int32 value)
at ReadTransportRuleFilterFromJson(XmlReaderDelegator , XmlObjectSerializerReadContextComplexJson , XmlDictionaryString , XmlDictionaryString[] )
at System.Runtime.Serialization.Json.JsonClassDataContract.ReadJsonValueCore(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)
at System.Runtime.Serialization.Json.JsonDataContract.ReadJsonValue(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)
at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)
at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Type declaredType, DataContract dataContract, String name, String ns)
at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName)
at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
at System.Runtime.Serialization.Json.DataContractJsonSerializer.ReadObject(XmlDictionaryReader reader, Boolean verifyObjectName)
at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.PartInfo.ReadObject(XmlDictionaryReader reader, XmlObjectSerializer serializer)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameterPart(XmlDictionaryReader reader, PartInfo part)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameters(XmlDictionaryReader reader, PartInfo[] parts, Object[] parameters, PartInfo returnInfo, Object& returnValue)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeBodyCore(XmlDictionaryReader reader, Object[] parameters, Boolean isRequest)
at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeBody(XmlDictionaryReader reader, MessageVersion version, String action, MessageDescriptionmessageDescription, Object[] parameters, Boolean isRequest)
at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeBodyContents(Message message, Object[] parameters, Boolean isRequest)
at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeRequest(Message message, Object[] parameters)
at System.ServiceModel.Dispatcher.DemultiplexingDispatchMessageFormatter.DeserializeRequest(Message message, Object[] parameters)
at System.ServiceModel.Dispatcher.UriTemplateDispatchFormatter.DeserializeRequest(Message message, Object[] parameters)
at Microsoft.Exchange.Management.ControlPanel.DiagnosticsBehavior.SerializationPerformanceTracker.DeserializeRequest(Message message, Object[] parameters)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.DeserializeInputs(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
Demand: <IPermission mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″
version=”1″>
<Identity Authenticated=”true”
Role=”Get-TransportRule?ResultSize@R:Organization”/>
</IPermission>
First Failed Demand: <IPermission mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″
version=”1″>
<Identity Authenticated=”true”
Role=”Get-TransportRule?ResultSize@R:Organization”/>
</IPermission>
Url: https://exchangeserver.mydomain.local:444/ecp/RulesEditor/TransportRules.svc/GetList?msExchEcpCanary=p2Zp1y_1kESsrueBkDB6T1r0z46NLdII4Q_D6294gRCkKBixfp0OnWr9OfSQ9SO205BuS7NQnns.(https://remote.mydomain.com/ecp/RulesEditor/TransportRules.svc/GetList?msExchEcpCanary=p2Zp1y_1kESsrueBkDB6T1r0z46NLdII4Q_D6294gRCkKBixfp0OnWr9OfSQ9SO205BuS7NQnns.)
Flight info: Features:[[Global.DistributedKeyManagement, False],[Global.GlobalCriminalCompliance, False],[Global.MultiTenancy, False],[Global.WindowsLiveID, False],[Eac.AllowMailboxArchiveOnlyMigration, True],[Eac.AllowRemoteOnboardingMovesOnly, False],[Eac.BulkPermissionAddRemove, True],[Eac.CmdletLogging, True],[Eac.CrossPremiseMigration, False],[Eac.DevicePolicyMgmtUI, False],[Eac.DiscoveryDocIdHint, False],[Eac.DiscoveryPFSearch, False],[Eac.DiscoverySearchStats, False],[Eac.DlpFingerprint, False],[Eac.EACClientAccessRulesEnabled, False],[Eac.GeminiShell, False],[Eac.ManageMailboxAuditing, False],[Eac.ModernGroups, False],[Eac.Office365DIcon, False],[Eac.OrgIdADSeverSettings, False],[Eac.RemoteDomain, False],[Eac.UCCAuditReports, False],[Eac.UCCPermissions, False],[Eac.UnifiedAuditPolicy, False],[Eac.UnifiedComplianceCenter, False],[Eac.UnifiedPolicy, False],[Eac.UnlistedServices, False],], Flights:[], Constraints:[[LOC, EN-US],[MACHINE, EXCHANGESERVER],[MODE, ENTERPRISE],[PROCESS, W3WP],[USER, TECHSUPPORT@],[USERTYPE, BUSINESS],], IsGlobalSnapshot: False
Resolution:
=> Reinstall CU7 & run the following command:
- Run setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
- Run setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms
- Run setup.exe /PrepareDomain /IAcceptExchangeServerLicenseTerms
=========================================================
Address rewriting doesn’t work in outbound message (Exchange 2013 SP1)
Issue: After creating a new Address rewrite on the Edge server with the following command,
New-AddressRewriteEntry -Name “rewrite all” -InternalAddress test.local -ExternalAddress mail.test.com the address rewrite works fine for the inbound messages, but does not work for the outbound message & they still appears as”test.local”
Resolution:
=> Check if the Send Connector is configured properly. If not configure it properly.
==========================================================
Mail flow not working in the Exchange 2013 server with error: 451 4.4.0 DNS query failed. The error was: DNS query failed with error”
Issue:
Issue with mailflow not working on Exchange 2013 server, in a mixed environment (Exchange 2010 (server 2008 R2 / Exchange 2013 (server 2012), however the mail flow works on Exchange 2010 without any issues. We get the following error:
2013-04-13T16:41:12.526Z,EX01Default Frontend EXCHANGE01,08D004497C6E9CC3,25,127.0.0.1:25,127.0.0.1:61348,*,,Message or connection acked with status Retry and response 451 4.4.0 DNS query failed. The error was: DNS query failed with error ErrorRetry
2013-04-13T16:41:12.526Z,EX01Default Frontend EXCHANGE01,08D004497C6E9CC3,26,127.0.0.1:25,127.0.0.1:61348,>,451 4.7.0 Temporary server error. Please try again later. PRX2 ,
And we see the following error in the connectivity log:
2013-04-13T23:59:44.720Z,08D006869E9DDB49,SMTP,internalproxy,>,DNS server returned ErrorRetry reported by 0.0.0.0. [Domain:Result] = EX01.xyz.priv:ErrorRetry;
2013-04-13T23:59:44.720Z,08D006869E9DDB49,SMTP,internalproxy,-,Messages: 0 Bytes: 0 (The DNS query for ‘Undefined’:’internalproxy’:’00000000-0000-0000-0000-000000000000′ failed with error : ErrorRetry)
2013-04-14T00:00:46.316Z,08D006869E9DDB4C,SMTP,internalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=0
2013-04-14T00:01:46.404Z,08D006869E9DDB4C,SMTP,internalproxy,>,DNS server returned ErrorRetry reported by 0.0.0.0. [Domain:Result] = EX01.xyz.priv:ErrorRetry;
2013-04-14T00:01:46.404Z,08D006869E9DDB4C,SMTP,internalproxy,-,Messages: 0 Bytes: 0 (The DNS query for ‘Undefined’:’internalproxy’:’00000000-0000-0000-0000-000000000000′ failed with error : ErrorRetry)
Resolution:
=> Change the DNS settings in the Server properties to use specific DNS instead of all network adapters.
=> Also check the DNS being used by the Transport service by running: get-transportservice and get-frontendtransportservice . Look for the External & Internal DNS being used. Change the DNS settings if the Transport service is not using the appropriate one.
==========================================================
Send connector created on exchange 2013 with 2010 coexistence does not work.
Issue: Issue with Send connector created on Exchange 2013 in a co-existence scenario with Exchange 2010. The send connector created on the Exchange 2013 does not work. When dropping an email through telnet we get this error:
451 4.7.0 Temporary server error. Please try again later
Resolution:
=>Check the Server state by running: Get-ServerComponentState –Identity <ServerID> make sure the following components are active.
HubTransport
FrontendTransport.
=> Run this command to set the state to active: Set-ServerComponentState -Component xxx -Identity EXCHSERVER.domain.com -State Active
==========================================================
Some emails are not getting delivered to one external domain (from any user)
Issue: Users may experience issues with not being able to send mails to one specific external domain. The issue occurs for many users & is not user specific.
Resolution:
=> Check if the problematic domain is blocking mails & have them white list.
=> Check if any antivirus / anti spam software is blocking it.
==========================================================
Exchange 2013 acting as an open relay
Issue: Exchange 2013 started to acts as open relay. Nothing found in the send/ receive connector settings.
Resolution:
=> Search for anonymous relay by running the command:
Get-ReceiveConnector | Get-ADPermission -User “NT AuthorityAnonymous Logon” | Where-Object {$_.ExtendedRights -like “ms-Exch-SMTP-Accept-Any-Recipient”} | Format-List Identity,ExtendedRights
=> Then run this command to remove it:
get-ReceiveConnector -Identity “” | remove-ADPermission -User “NT AuthorityAnonymous Logon” -ExtendedRights “ms-Exch-SMTP-Accept-Any-Recipient”
=========================================================
StartTLS Error Event ID 12014
Issue: You will keep getting Start TLS error event 12014 on Exchange 2007 windows 2003R@ server. When we check the list of certificates in Exchange we will see invalid certs.
Resolution:
=> server not compatible with SHA2 .
=> Try this hotfix: http://support.microsoft.com/en-in/kb/938397
Ratish Nair
Microsoft MVP | Exchange Server
Team @MSExchangeGuru.com
Posted March 31st, 2015 under Exchange 2010, Exchange 2013, Tips, Uncategorized.
RSS 2.0 feed.
Leave a response, or trackback.
Exchange OWA and ECP are not working. Signing in to Exchange Server OWA is showing you an error. The error is showing that there is a Server Error in ‘/owa’ Application. When trying with ECP, it’s showing Server Error in ‘/ecp’ Application. How did this happen, and what is the solution to it? In this article, you will learn how to fix Exchange Server Error in ‘/owa’ Application.
Table of contents
- Server Error in ‘/owa’ Application
- Explanation Server Error in ‘/owa’ Application
- Solution for Server Error in ‘/owa’ Application
- Default Web Site configure bindings
- Exchange Back End configure bindings
- Conclusion
When starting Exchange OWA (Outlook Web Access) and entering the credentials, the below error appears. The same happens when going to the ECP (Exchange Control Panel) page.
Server Error in ‘/owa’ Application.
https://ex01-2016/owa/auth/errorFE.aspx?CafeError=SSLCertificateProblem
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.Web.HttpException: https://ex01-2016/owa/auth/errorFE.aspx?CafeError=SSLCertificateProblemSource 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.Stack Trace:[HttpException (0x80004005): https://ex01-2016/owa/auth/errorFE.aspx?CafeError=SSLCertificateProblem]
Microsoft.Exchange.HttpProxy.FbaModule.OnBeginRequestInternal(HttpApplication httpApplication) +441
Microsoft.Exchange.HttpProxy.<>c__DisplayClass16_0.b__0() +1672
Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(Action tryDelegate, Func2 filterDelegate, Action1 catchDelegate) +35
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +142
System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) +75
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +93Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.8.3928.0
Why is this happening and what is the solution for Exchange 2016 OWA and ECP not working?
Explanation Server Error in ‘/owa’ Application
Why did the error start to show when signing in to Exchange OWA and ECP? This can happen if you, for example:
- Install Exchange Cumulative Update
- Remove certificate that was assigned to Exchange Server
If you already have a third-party certificate installed, select that in the next part. If you don’t have a third-party certificate because you removed it, select the default Microsoft Exchange self-signed certificate. You can always select the self-signed certificate to get access to the Exchange Admin Center. After that, you can import a new certificate.
Solution for Server Error in ‘/owa’ Application
Sign in to the Exchange Server. Start Internet Information Services (IIS) Manager. Unfold the Exchange Server and click the Sites list. You will find the Default Web Site and Exchange Back End.
Default Web Site configure bindings
Click on Default Web Site and click Bindings in the actions panel.
Check both the site bindings with type https. Double-click the first type https with IP Address * (asterisk).
The SSL certificate is Not selected.
Click on Not selected and select the Microsoft Exchange self-signed certificate from the dropdown menu. Do you have a third-party certificate? Select that certificate instead. Click OK.
In my example, I selected the Exchange self-signed certificate. That’s because I don’t yet have a third-party certificate configured. The self-signed certificate is created by default when you install Exchange Server.
Read more: Install free let’s encrypt certificate in Exchange Server »
On my end, after assigning the certificate it was reverted back to Not selected. Select the certificate again from the dropdown menu and click OK. To make sure it’s now selected, check again. This time it’s selected.
Important: After selecting the certificate from the dropdown menu, it sometimes does not get selected. Make sure that you double-check after assigning the certificate.
Do the same with the second site binding. Double-click IP Address 127.0.0.1.
Select the certificate and click OK. Again, double-check if it’s assigned. If the certificate is already bound to the site, you don’t have to make any changes.
Now that we have the certificates assigned and checked both site bindings, we can proceed to the next step.
Exchange Back End configure bindings
Click on Exchange Back End and click Bindings in the actions panel.
Select the site binding with type https and port 444. Click Edit...
Select the Microsoft Exchange self-signed certificate from the dropdown menu. Click OK. If you have a third-party certificate, select that. Don’t forget to double-check after assigning the certificate.
After applying and double-checking, you have to restart IIS.
After IIS restarts, go to Exchange OWA or ECP and sign in. You can now successfully sign in.
I hope this article helped you fix the server error in ‘/owa’ application in Exchange Server. Good to know is that it also fixed the server error in ‘/ecp’ application in Exchange Server.
Keep reading: Recreate virtual directories in Exchange Server »
Conclusion
You learned why you get Server Error in ‘/owa’ Application in Exchange Server. This happens when the bindings are not configured to the Exchange web sites in IIS. Bind the certificates to both the Exchange Default Web Site and Exchange Back End. Don’t forget to double-check after selecting the certificates. As of last, restart IIS. Now you can sign in to OWA and ECP without the Server Error in ‘/owa’ Application showing up.
Did you enjoy this article? You may also like the article Exchange Hybrid test plan checklist. Don’t forget to follow us and share this article.
ALI TAJRAN is a passionate IT Architect, IT Consultant, and Microsoft Certified Trainer. He started Information Technology at a very young age, and his goal is to teach and inspire others. Read more »
Problem
You’ve noticed that after patching Exchange Server 2019 servers (for this example, the patch for HAFNIUM was applied), access to /OWA and /ECP now displays the following errors:
OWA
Something went wrong
Your request couldn’t be completed. HTTP Status code: 500.
X-ClientId: F8E662D41996402E8660EEEB0976EA50
request-id a5077939-13bd-4032-9471-d6c8dc221d5a
X-OWA-Error System.Web.HttpUnhandledException
X-OWA-Version 15.2.721.13
X-FEServer Exch01
X-BEServer Exch02
Date:3/8/2021 12:31:53 PM
InnerException: System.IO.DirectoryNotFoundException
Fewer details…
Refresh the page
ECP
Server Error in ‘/ecp’ Application.
_______________________________________
Could not load file or assembly ‘Microsoft.Exchange.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.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.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 [HKLMSoftwareMicrosoftFusion!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 [HKLMSoftwareMicrosoftFusion!EnableLog].
Stack Trace:
[FileNotFoundException: Could not load file or assembly ‘Microsoft.Exchange.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find the file specified.]
System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMarkHandle stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName, ObjectHandleOnStack type) +0
System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName) +96
System.Type.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) +65
System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) +62
System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, XmlNode node, Boolean checkAptcaBit, Boolean ignoreCase) +50
[ConfigurationErrorsException: Could not load file or assembly ‘Microsoft.Exchange.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find the file specified.]
System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, XmlNode node, Boolean checkAptcaBit, Boolean ignoreCase) +572
System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, Boolean checkAptcaBit) +31
System.Web.Configuration.Common.ModulesEntry.SecureGetType(String typeName, String propertyName, ConfigurationElement configElement) +59
System.Web.Configuration.Common.ModulesEntry..ctor(String name, String typeName, String propertyName, ConfigurationElement configElement) +59
System.Web.HttpApplication.BuildIntegratedModuleCollection(List`1 moduleList) +221
System.Web.HttpApplication.GetModuleCollection(IntPtr appContext) +1103
System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +122
System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +173
System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +255
System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +347
[HttpException (0x80004005): Could not load file or assembly ‘Microsoft.Exchange.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find the file specified.]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +552
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +122
System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +737
You’ve noticed that reviewing the BinSearchFolders application settings for ecp folder in the Exchange Back End website shows that the Value is configured with %ExchangeInstallDir%:
Changing this to the path without using the variable appears to fix the ECP page but not OWA:
Solution
One of the possible solutions to correct the issue is to use the UpdateCas.ps1 script located in the MicrosoftExchange ServerV15Bin folder to rebuild the /OWA and /ECP directory:
Proceed to test the /owa and /ecp directories once the PowerShell completes.
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 [HKLMSoftwareMicrosoftFusion!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 [HKLMSoftwareMicrosoftFusion!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