HOW TO: Change the Web Page and Database Connection Time-Out settings RMTrack V4 or higher
Symptoms
It is possible in larger databases that the default length of time for web pages and database opeartions to time-out is not sufficient for some operations to complete. Causing an unexpected error to occur.
Resolution
Changing time-out settings requires access to the RMTrack installation folder on the web/application server. The default location of the installation folder is: C:\inetpub\wwwroot\RMT. There are two files in that folder that we need to make changes to: Web.config and DbConnection.udl
Depending on the error occuring (web page time-out or database response time-out) extending one or both my be necessary.
- CHANGE TIMEOUT OF WEB PAGES
- In the web.config file change the <httpRuntime> element to set the execution limit to 600 (10 minutes)
- In the web.config search for the line “Don't include the ASP.NET version header in the response, set maximum upload size - DO NOT CHANGE “
- The line after that should be: <httpRuntime enableVersionHeader="false" maxRequestLength="10236" />
- Add executionTimeout="600" – to the line
- In the web.config file change the <httpRuntime> element to set the execution limit to 600 (10 minutes)
e.g. <httpRuntime enableVersionHeader="false" maxRequestLength="10236" executionTimeout="600" />
- CHANGE DATABASE TIMEOUT
- In the DbConnection.udl add the “Connection Timeout” parameter and set limit to 600 (10 minutes)
[oledb]
; Everything after this line is an OLE DB initstring
Provider=SQLOLEDB.1;Password=***;Persist Security Info=True;User ID=***;Initial Catalog=***;Data Source=***; Connection Timeout=600;
Applies to
[RMTrack Issue Tracking – v4.0 or later]