Modifying Microsoft .NET Timeout Settings

If an FDM process requires more than 60 minutes, the client browser session stops because the Microsoft .NET session times out. Executing a large Hyperion consolidation or uploading and processing a large multiperiod source file are two examples of FDM processes that may require more than 60 minutes. You can modify the timeout settings by modifying Web.config and Machine.config.

On the Web server, Web.config is located in this directory:

The machine.config file is located in the following directory on the Web server:

  To increase the timeout setting (example to change timeout setting from 60 minutes to 120 minutes):

  1. In Web.config, change “60” to “120” in the following line:

    <forms name=”.HyperionFDM” loginUrl=”Pages/Login.aspx” protection=”All” timeout=”60” path=”/”>

  2. In Web.config, change “60” to “120” in the following line:

    <sessionState mode=”InProc” stateConnectionString=”tcpip=127.0.0.1:42424” sqlConnectionString=”data source=127.0.0.1;user id=sa;password=” cookieless=”false” timeout=”60”/>

  3. In Web.config, change “3600” to “7200” in the following line:

    <httpRuntime executionTimeout=”3600” maxRequestLength=”25600” />

  4. In Machine.config, change “00:60:00” to “02:00:00” in the following line:

    <processModel enable=”true” timeout=”Infinite” idleTimeout=”Infinite” shutdownTimeout=”0:00:05” requestLimit=”Infinite” requestQueueLimit=”5000” restartQueueLimit=”1000” memoryLimit=”30” WebGarden=”false” cpuMask=”0xffffffff” userName=”machine” password=”AutoGenerate” logLevel=”Errors” clientConnectedCheck=”0:00:05” comAuthenticationLevel=”Connect” comImpersonationLevel=”Impersonate” responseDeadlockInterval=”00:60:00” maxWorkerThreads=”100” maxIoThreads=”100”/>

  5. In IIS Manager, increase the connection timeout setting of the default Web site, for example, change 3600 seconds to 7200 seconds.

    The figure shows the IIS Manager screen with a value of 7200 seconds entered in the Connection timeout field.