question

NVGoldendog avatar image
0 Votes"
NVGoldendog asked NVGoldendog answered

Event ID 1309 ASP.NET 4.0.30319.0 The request has been aborted. NT AUTHORITY\SYSTEM HttpException

Hi. I currently have a Windows 2016 Server fully patched running Exchange Server 2016 with CU22 and SP1 installed and am having an issue with Outlook clients and mobile devices failing to connect to the Exchange Server. I found in the event log this:
Event code: 3001
Event message: The request has been aborted.
Event time: 11/6/2021 11:49:34 AM
Event time (UTC): 11/6/2021 6:49:34 PM
Event ID: 8490d735a0fe4e3fb8ce84565dad50bb
Event sequence: 2862
Event occurrence: 36
Event detail code: 0


Application information:
Application domain: /LM/W3SVC/2/ROOT/mapi/emsmdb-1-132806972104934450
Trust level: Full
Application Virtual Path: /mapi/emsmdb
Application Path: D:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\mapi\emsmdb\
Machine name: ~~~~~~


Process information:
Process ID: 11708
Process name: w3wp.exe
Account name: NT AUTHORITY\SYSTEM


Exception information:
Exception type: HttpException
Exception message: Request timed out.

Request information:
Request URL: https://~~~~~.local:444/mapi/emsmdb/?MailboxId=2a069703-1e8a-4cfe-b136-7440eb5cc1d3@~~~.com
Request path: /mapi/emsmdb/
User host address: fe80::e149:1b8:5117:42d11/6/2021 11:49:34 AM
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\SYSTEM


Thread information:
Thread ID: 22
Thread account name: NT AUTHORITY\SYSTEM
Is impersonating: False
Stack trace:


Custom event details:

and event ID 1310

Event code: 3008
Event message: A configuration error has occurred.
Event time: 11/6/2021 12:00:18 PM
Event time (UTC): 11/6/2021 7:00:18 PM
Event ID: da8cd1169b3143bba8af9d60f8e7893b
Event sequence: 1
Event occurrence: 1
Event detail code: 0


Application information:
Application domain: /LM/W3SVC/2/ROOT/API-1-132806988180043588
Trust level: Full
Application Virtual Path: /API
Application Path: D:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\rest\
Machine name: ~~~~


Process information:
Process ID: 33248
Process name: w3wp.exe
Account name: NT AUTHORITY\SYSTEM


Exception information:
Exception type: ConfigurationErrorsException
Exception message: The 'targetFramework' attribute in the <compilation> element of the Web.config file is used only to target version 4.0 and later of the .NET Framework (for example, '<compilation targetFramework="4.0">'). The 'targetFramework' attribute currently references a version that is later than the installed version of the .NET Framework. Specify a valid target version of the .NET Framework, or install the required version of the .NET Framework. (D:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\rest\web.config line 114)
at System.Web.Compilation.MultiTargetingUtil.ValidateTargetFrameworkMoniker(String targetFrameworkMoniker)
at System.Web.Compilation.MultiTargetingUtil.InitializeTargetFrameworkName()
at System.Web.Compilation.MultiTargetingUtil.EnsureFrameworkNamesInitialized()
at System.Web.Compilation.BuildManager.Initialize()
at System.Web.Compilation.BuildManager.InitializeBuildManager()
at System.Web.HttpRuntime.HostingInit(HostingEnvironmentFlags hostingFlags, PolicyLevel policyLevel, Exception appDomainCreationException)

Request information:
Request URL: https://localhost:444/api/v1.0/users/HealthMailbox9aa272ad27bb409daa0cf83142252185@~~~.local/Messages?$top=1
Request path: /api/v1.0/users/HealthMailbox9aa272ad27bb409daa0cf83142252185@~~~.local/Messages
User host address: ::1
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\SYSTEM


Thread information:
Thread ID: 9
Thread account name: NT AUTHORITY\SYSTEM
Is impersonating: False
Stack trace: at System.Web.Compilation.MultiTargetingUtil.ValidateTargetFrameworkMoniker(String targetFrameworkMoniker)
at System.Web.Compilation.MultiTargetingUtil.InitializeTargetFrameworkName()
at System.Web.Compilation.MultiTargetingUtil.EnsureFrameworkNamesInitialized()
at System.Web.Compilation.BuildManager.Initialize()
at System.Web.Compilation.BuildManager.InitializeBuildManager()
at System.Web.HttpRuntime.HostingInit(HostingEnvironmentFlags hostingFlags, PolicyLevel policyLevel, Exception appDomainCreationException)


Custom event details:

I verified from another forum posting that this file is intact in both locations:
https://docs.microsoft.com/en-us/exchange/troubleshoot/client-connectivity/event-1309-code-3005-cannot-access-owa-ecp

I am able to login to OWA BUT mail flow seems to be slow (may not be related).

I think it might have something to do with us trying to fix a securechannel event ID that kept flooding our system log and were we getting after we disabled TLS 1.0 and 1.1 following https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-server-tls-guidance-part-3-turning-off-tls-1-0-1-1/ba-p/607898

looking like this in our event log: https://www.alitajran.com/a-fatal-error-occurred-while-creating-a-tls-client-credential/
So we followed powershell script to fix which did get rid of Schannel error but clients not able to connect.

I am going to take a backup of the registry and then use IIS Crypto 3.2 to restore the defaults for Server TLS protocols, etc. and reboot to see if it at least resolves until I hear back from someone on these forums as I couldn't find an answer to my exact issue.

Thanks,
Lyle Epstein
Microsoft Silver Partner
Mid Market Cloud Solutions

office-exchange-server-mailflowoffice-exchange-server-connectivityoffice-exchange-server-itpro
· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

As an update to this I went ahead and removed the Web Services Virtual Directory and re-created it with New-WebServicesVirtualDirectory via Powershell/EMS.
I had also restarted all the services and did an IISReset as well.

I notice that I still get the EventID 1309 and 1310 issue and I am able to connect fine via OWA and mail flow is working as well, but via the Outlook client it does not work and on one computer I waited over 45 minutes for it to connect.

II ran the RCA tool and got:

Testing HTTP Authentication Methods for URL https://mail.~~~~~~~.com/mapi/emsmdb/?MailboxId=735c6edc-51b9-445e-a461-12c6fd449c44@~~~~~~.com.
The HTTP authentication test failed.
Additional Details
Exception details:
Message: The operation has timed out
Type: System.Net.WebException
Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.M365.RCA.Services.RcaHttpRequest.GetResponse()

So I am pretty certain it has something to do with the FrontEndProxy and obviously some .NET security or permissions error (I also checked in the IIS AppPool t see what it was running as and it was set to LocalUser which is how the other Exchange App Pool items were set).

0 Votes 0 ·

Hi @NVGoldendog

Agree with Andy, please firstly check your .net framework version. Is your server a newly installed one or you upgrade it from previous CU version?

If your version is correct, you could also try restarting your IIS or recycling related application pools.

Here is a related thread discussed a related issue for your reference: Can't Connect to Exchange server from Mobile After Upgrading to Exchange CU23
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.


0 Votes 0 ·

Hmmmm,

I can observe the same behaviour here on Server 2022 with EXC2019 CU12 installed AND after disabling TLS 1.0 and TLS 1.1 following the PS-script.

The version of the .NET-runtime hasn't changed so I am quite lost to get rid of this event flood. It seems that everything is working though as expected.



0 Votes 0 ·

I seem to have fixed the error by removing the "targetframework"-call in the web.config file meantioned in the event.

Just remove the

"targetFramework="4.5.1" "-part

in

"X:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\rest\web.config"

and do a iireset.

0 Votes 0 ·

Hi @NVGoldendog

Is there any update about your issue so far? Have you checked .net framework version?

0 Votes 0 ·
AndyDavid avatar image
0 Votes"
AndyDavid answered
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

NVGoldendog avatar image
0 Votes"
NVGoldendog answered

Hi ITPepper-1210. Thanks for sharing about removing that line in the web.config file. I hope that it doesn't break anything else though. Are all the errors gone now that you removed that from the web.config file?

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.