X owa error system web httpunhandledexception - Исправление ошибок и поиск оптимальных решений проблем

Remove From My Forums

Question

X-ClientId: 03BE6BE5BF9149BDBA03C48EEFD4E298 request-id 0c68c50a-cd58-415b-8396-4e4987e03726 X-OWA-Error System.Web.HttpUnhandledException X-OWA-Version 15.1.1466.3 X-FEServer FCXSMBX2 X-BEServer FCXSMBX2 Date:4/16/2018 5:54:48 AM InnerException: System.IO.DirectoryNotFoundException

i tried to redo the IIS binding to https with cert,and it was working for a few days before it crash again.

what should i try now? need help!

ROnald

All replies

what is your .net version?

https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed

Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me — and others — to take time out to help you. Thank you! Off2work
Hello,

I am working on the problem with ronald, our exchange servers are using the following version (obtained from regedit method)

C:WindowsMicrosoft.NETFramework64v4.0.30319

Regards

C
378389 is 4.5 and yours is even older if that is correct.

Depends on your CU version, you should upgrade your .net to that version https://eightwone.com/2017/12/21/upgrade-paths-for-cus-net/

Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me — and others — to take time out to help you. Thank you! Off2work
We are currently on CU9.. however to share when i use the following command

Get-ItemProperty-Path»HKLM:SOFTWAREMicrosoftNET Framework SetupNDPv4Full»| Format-List

It shows the Release as 460805, so not too sure which is which now.
Hello,

I did an update to Dot.net 4.7.1. but it didnt help, however i noticed something

Server A and B and C , if i swap to Server C and try owa while Server A and B are up , owa works.. once i swap back to server B or A as primary it starts getting the error as above regardless of using the server IP and note the time is off too (UTC time?)
Well, thanks for your cooperation.

First, run below command to check the status of Exchange component:
```
Get-ServerComponentstate -Identity “servername” 
```
If the state is Inactive, please run below command to active relevant component:
```
Set-ServerComponentState <Identity> -Component “component name” -Requester HealthAPI -State Active
```
If this issue remain exists, run UpdateCas.PS1 on problematic Exchange server to rest OWA service.
Open PowerShell as administrator and run «cd: ‘C:Program FilesMicrosoftExchange ServerV15Bin«, then run UpdateCas.ps1.

Best Regards,
Allen Wang

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact
tnsf@microsoft.com.

Click
here to learn more. Visit the dedicated
forum to share, explore and talk to experts about Microsoft Teams.
- Proposed as answer by
  
  Wednesday, April 18, 2018 1:30 PM
Any further concern about your question?
If the above suggestion helps, please be free to mark it as answer. Thanks for your cooperation.

Best Regards,
Allen Wang

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact
tnsf@microsoft.com.

Click
here to learn more. Visit the dedicated
forum to share, explore and talk to experts about Microsoft Teams.
- Proposed as answer by
  Allen_WangJF
  Wednesday, May 2, 2018 4:25 PM
Hi,

Sorry to interrupt your again.
I just want to check the current status of your question.
Is there any update or any other assistance I could provide on this issue?

Please feel free to mark responses as the answer and/or
vote them helpful as appropriate.
Thank you for your understanding and patience!

Best Regards,
Allen Wang

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact
tnsf@microsoft.com.

Click
here to learn more. Visit the dedicated
forum to share, explore and talk to experts about Microsoft Teams.
Event ID 18, MSExchange OWA

Outlook Web App couldn’t initialize.
Themes folder «D:Program FilesMicrosoftExchange ServerV15ClientAccessowaprem/15.2.529.8resourcesthemes» doesn’t exist.

After installing KB4536987
OWA did not work. Exchange 2019 CU4

The use of UpdateCas.PS1 worked for me.

Thanks Allen Wang.

Michael Wiskman
- Proposed as answer by
  Michael Wiskman
  Wednesday, April 22, 2020 12:36 PM

Источник

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.

_______________________________________

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.

Источник

Within Exchange 2013 you can have OWA (Outlook Web App) Mailbox policies, in which an Exchange Admin can determine which features within OWA are available to users. By default, there’s a default policy with all options enabled, but you can have more policies and configure them at will and assign them to Mailbox-enabled users according to the organization’s needs.

In this case we wanted to completely disable the Text Messaging option, as it offers no additional functionality for this organization. Disabling it prohibits unnecessary confusion with end users. The same is for the OWA IM integration option; it is very possible you don’t want every user Lync-enabled but still Mailbox-enabled. When IM integration is configured, the IM Login option is visible for everybody but only works for those who are Lync-enabled. This could potentially be confusing and therefore OWA Mailbox policies, in this case, are a great way to limit user confusion.

However, we ran into an issue within this environment. Disabling Text Messaging (in the default OWA Mailbox Policy) caused some issues within the OWA options screen. I haven’t checked the other options whether they also cause issues, but for now I’ll assume it’s only the case with the Text Messaging option.

Even though I should have access to Call Answering rules (via Options > Phone > Voice Mail) because my mailbox is UM enabled within Exchange, I can’t manage them. A http 500 server error is presented in the frame where the rules should be as you can see in the screenshot below. Luckily, it’s just this screen and I can still navigate to other options without any problem.

This looks like a bug, I’ve seen more during the RTM build in OWA (setting Calendar permissions also generated similar errors). A bit annoying, but I decided to create a second policy with everything enabled again because I gathered the errors will be fixed in the future. The servers were already on CU1, so currently no new update exists that could potentially fix it.

Unfortunately that didn’t fix the issue! I changed the OWA Policy several times, but the error remained. I’ve moved the mailbox to another database, disable the UM features of the mailbox (and re-enabled them shortly thereafter) but all to no avail…

Some further investigation in the event log of the corresponding Client Access Server I was load balanced to, showed a little more insight in what is going wrong:

Log Name:      Application
Source:        MSExchange Control Panel
Date:          27-5-2013 22:14:02
Event ID:      4
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      ex02.contoso.local
Description:
Current user: ‘contoso.local/Contoso/Users/Test/Test Kees’
Request for URL ‘https://ex02.contoso.local:444/ecp/Customize/Voicemail.aspx?showhelp=false(https://mail.contoso.com/ecp/Customize/Voicemail.aspx?showhelp=false)’ failed with the following error:
System.Web.HttpUnhandledException (0x80004005): Exception of type ‘System.Web.HttpUnhandledException’ was thrown. —> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> Microsoft.Exchange.Configuration.Authorization.CmdletAccessDeniedException: You don’t have permission to open this page. If you’re a new user or were recently assigned credentials, please wait 15 minutes and try again.

If you notice the bold emphasis (added by me) the underlying cause is apparently a permission issue. Which makes sense, as what that is what OWA Mailbox policies do (next to changes in UI).

It made me think whether there is another option to change permissions in what user can and can’t do. Within Exchange 2013 you can have RBAC (Rights Based Access Control) User Roles of which an example is shown here (partly, within EAC > Permissions > User Roles).

Two options were interesting: MyTextMessaging and MyVoiceMail. I’ve enabled them in a new policy (with all other enabled options in the default policy), although MyVoiceMail is already enabled in the Default Role Assignment Policy.

First I’ve changed the mailbox policy to one that doesn’t disable Text Messaging. You can do that in the EAC via Recipients >DoubleClick Mailbox enabled User > Mailbox Features and scroll down to Email Connectivity and press View Details (highlighted below in screenshot).

Now select the OWA Mailbox Policy that does not have the Text Messaging option disabled.

I’ve then assigned this Role Assignment Policy to this specific mailbox, to the policy that I created earlier (see previous screenshot). This is key, even if they are the same, changing the assigned Role Assignment Policy somehow corrects the permissions within OWA for this user.

It can take a while (probably no longer than 15 minutes) for permissions to be active, but after that you can happily manage Call Answering rules again within OWA (which is the only place for users).

Concluding

It looks like disabling the Text Messaging option within an OWA Mailbox policy has some unexpected side-effects on UM enabled mailboxes within Exchange 2013 with CU1.

The side-effects are two-fold: First issue is that Call Answering rule management isn’t possible. The second issue is that changing the OWA Mailbox policy back again didn’t resolve the issue. Only by changing and applying another Role Assignment Policy (with correctly enabled options) resolves this latter issue.

If memory serves me right, this bug wasn’t present within the RTM build.

Источник

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