Techrunner
asked on
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.
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
User: NT AUTHORITY\SYSTEM
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:
ASKER
Hi
Where I can find option in IIS to increase the connection time out settings ?
Where I can find option in IIS to increase the connection time out settings ?
Hi,
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.
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.
ASKER
Hi
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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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
http://learn.iis.net/page.aspx/266/troubleshooting-failed-requests-using-tracing-in-iis/