Event code 3001 ASP.NET 4.0.30319.0 - Exchange 2016

We have 2 exchange server 2016 in DAG

I am continously seeing the below log message on Server 1 appearing in event viewer.

Appreciating any help and suggestions.

Event code: 3001
Event message: The request has been aborted.
Event time: 11/23/2017 4:34:08 PM
Event time (UTC): 11/23/2017 1:34:08 PM
Event ID: 52506b710e5e4469b47ce9b4a3e07d73
Event sequence: 25
Event occurrence: 24
Event detail code: 0
Application information:
    Application domain: /LM/W3SVC/2/ROOT/Rpc-1-131549950576384434
    Trust level: Full
    Application Virtual Path: /Rpc
    Application Path: C:\Windows\System32\RpcProxy\
    Machine name: EXCHANGESER2016
Process information:
    Process ID: 10168
    Process name: w3wp.exe
    Account name: NT AUTHORITY\SYSTEM
Exception information:
    Exception type: HttpException
    Exception message: Request timed out.

Request information:
    Request URL: http://ex16.mydomain.com:81/rpc/rpcproxy.dll?ex16.mydomain.com:6001
    Request path: /rpc/rpcproxy.dll
    User host address: fe80::bddb:6009:4573:290e10168
    Is authenticated: True
    Authentication Type: Negotiate
    Thread account name: NT AUTHORITY\SYSTEM
Thread information:
    Thread ID: 180
    Thread account name: NT AUTHORITY\SYSTEM
    Is impersonating: False
    Stack trace:
Custom event details: 

Open in new window

Who is Participating?
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.

Hemil AquinoNetwork Security EngineerCommented:
The event 3001 is quite a common event from which we cannot get much useful information. Based on my experience, 1309 with event 3001 may occur when hitting the timeout limit. Please try increase the request timeout value to see if this helps.

If the issue persists, I would suggest you take advantage of failed request tracing to grab more information:

Troubleshooting Failed Requests Using Tracing in IIS 7
cciedreamerAuthor Commented:
Where I can find option in IIS to increase the connection time out settings ?
Hemil AquinoNetwork Security EngineerCommented:

Before you I show you that, I just thought about something. Since the error is making reference to ASP.NET 4.0.30319.0
Try reinstalling ASP.net 4.0 or recent ones, reboot the server and see how it goes.
cciedreamerAuthor Commented:
I think the better idea is to first increase  timeout values as I dont want to the production server into risk by reinstalling ASP.net
Hemil AquinoNetwork Security EngineerCommented:
I am not on my servers at this moment therefore I can't tell you with exactitude but here is a link that will guide you.
https://support.symantec.com/en_US/article.TECH134646.html Same apply to exchange 2013/16

Also, keep in mind this.

1- Always consider to have a test replica of your servers for testing.
2- Make sure your system has been fully updated. Such as: "Windows and Exchange.

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

From novice to tech pro — start learning today.