Addressing Involuntary Logouts

If your users are being logged-out of InformationLeader whilst they’re working, the following steps should help identify and resolve the problem. Take note of the time when users were logged out.

WARNING: Changes to the settings documented here will cause IIS to reload the InformationLeader Application. Ensure your users are notified of the downtime if changes are to be made during business hours.

Areas of particular interest are:

InformationLeader Server – IIS Settings, Web.config entries
InformationLeader Server Windows\Application logs

 

Checking your InformationLeader Server – IIS Settings

  1. Connect to your InformationLeader IIS Server, and load up the IIS (version 6 or higher) Snap-In
  2. Navigate to SERVERNAME\Application Pools
  3. Select the Application Pool that InformationLeader is running under
  4. Click Advanced Settings
  5. Under Process Model, ensure that Idle Time-out is set to zero.

It is worth noting that the Application Pool should also have comparable values for Start Automatically and the Recycling section as well (see image).

 

 

 

 

 

 

Checking your InformationLeader Server – Web.config Entries

You can generally access your web.config at
C:\inetpub\wwwroot\informationleader\web.config

Recommendation: View or edit this file in Administrator Mode using notepad++ or Visual Basic editors

Search the document for “timeout” entries. Line numbers are approximate and may vary depending on your site’s configuration

Line 20: <add key="Session Timeout" value="20" />
Line 33: <add key="ChartImageHandler" value="Storage=session;Timeout=20;" />
Line 95: <forms name="InformationLeaderSecurity" loginUrl="Startup/login.aspx" path="/" protection="All" slidingExpiration="true" timeout="60"></forms>
Line 127: <sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;user id=sa;password=" cookieless="false" timeout="20" />
Line 135: executionTimeout="[seconds]" - time in seconds before request is automatically timed out
Line 142: <httpRuntime executionTimeout="270" maxRequestLength="20560" useFullyQualifiedRedirectUrl="false" minFreeThreads="8" minLocalRequestFreeThreads="4" appRequestQueueLimit="100" requestValidationMode="2.0" />

Was this article helpful?

Related Articles