Disable user inactivity timeout

SOLVED

I've set the idle timeout in IIS on the App Pool to be 0 and for good measure I've set the time out action to be suspend. I've set the recycling so it is off. In CRM, under the administration -> users -> user configuration, the idle timeout is set to 240. If I want to disable the timeout in CRM, does setting it to 0 do that? I'm sure it does, but the help file doesn't say. All it says is this:

The inactivity period (in minutes) after which a user is automatically logged out of Sage CRM.

Sage CRM uses the value in this field only if it is less than the value in Idle Time-out (minutes) specified for the Sage CRM application pool in Microsoft Web Server (IIS). The default idle time-out value set for the Sage CRM application pool is 120 minutes.

The help file doesn't say how to disable the timeout. Also, I assume that setting the value in CRM to a value higher than the app pool timeout will be pointless as the app pool will suspend or kill the process anyway?

A common question I get asked is how to stop CRM booting you out after a period of inactivity. IE stop it completely. Anyone? This is CRM 2020.

Parents Reply Children
  • 0 in reply to Vega
    verified answer

    Ok, there is something going on here.

    I set the user inactivity timeout to 0 and saved it. It shows on the screen as 0 and in the database it is 0. If I navigate away from that screen and come back, it is 30.

    If I log out and do an IIS Reset the value in the database is still 0. On first login, by the time I have logged in, the value has changed to 30. I ran SQL profiler to see when this change happened and the system sets it to 30 if it is 0 during the initial login.

    I thought I'd see what happens when (or if) I set the user activity timeout to -1. CRM allows this. However, as soon as you do any action and click on anything it logs you out. You can't log back in either. Resetting IIS and logging back in, the value stays at -1.

    I have logged both issues with Sage and I have set the user inactivity timeout to 1440.

    The upshot is, setting the user inactivity timeout to -1 is a handy way of locking the system for more than the "Lock System" allows you to do.

  • 0 in reply to Vega

    I found that after one of the 2019 releases (I think) that the facility to set the inactivity timeout to 0 was effectively removed; if you tried that then it would just revert back to 30.  So I went the other way as there doesn't seem to be an upper limit so where my clients request this I set it to something like 30,000 which is over 20 days.