Have you ever had users complain about the CRM web application timing out on large operations? If so, you may want to check the ASP.Net timeout setting.
The reason for the warning is that the execution time required by CRM connecting with your remote SQL Server is exceeding the currently set ASP.NET request execution timeout value. By default, this value is initially set to 300 seconds. This may occur for example, when working with Large Marketing Lists of 150,000+ members.
The event log entry may look something like the following…
Event code: 3001
Event message: The request has been aborted.
Event time: 11/19/2008 3:37:51 PM
Event time (UTC): 11/19/2008 11:37:51 PM
Event ID: 13998b6749624519856e0b4f83cf6f8b
Event sequence: 302758
Event occurrence: 1
Event detail code: 0
Application domain: /LM/W3SVC/1/ROOT-1-128716032401801167
Trust level: Full
Application Virtual Path: /
Application Path: c:\inetpub\wwwroot\
Machine name: ContosoCRMweb
Process ID: 3656
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception type: HttpException
Exception message: Request timed out.
How to Modify the ASP.NET request execution timeout setting for Windows Server 2003
1. On the computer where Microsoft Dynamics CRM Server application is installed, start Internet Information Services (IIS) Manager.
2. Expand Web Sites, right click the Microsoft Dynamics CRM Web site, and then click Properties.
3. On the Microsoft Dynamics CRM Web site properties page, click ASP.NET, and then click Edit Configuration.
4. Click the Application tab, and then in the Request execution timeout box increase the number of seconds.
5. Click OK two times and close IIS Manager.
We're always looking for feedback and would like to hear from you. Please head to the Dynamics 365 Community to start a discussion, ask questions, and tell us what you think!