Open Forum

Expand all | Collapse all

Idle Session Setup Issues

  • 1.  Idle Session Setup Issues

    Posted Feb 13, 2020 08:32 AM

    I'm having issues using the idle session timeout feature via the server setup.

    I'm using NAV 2017. I have setup the Keep Alive Terminal and Idle session time out fields on the client services tab. My Keep Alive is set as 01:04:00 and my Idle Session is set as 01:00:00 and it keeps timing users out after about 10 minutes. I have found conflicting documentation from microsoft saying that the Keep Alive should should be higher and some saying it should be lower. Anyone else having this issue and how did you resolve?

    Thank you!

    Matthew Dusenberry

  • 2.  RE: Idle Session Setup Issues

    Posted Feb 14, 2020 10:02 AM
    Hi Matthew,

    I have my Keep Alive Interval at 120.  I left this as the default.  My Idle Client Timeout is set to 01:29:00.  My users lose connection at 1 hr and 29 mins but their NAV client stays open.  Only when they go to use it again do they get prompted that their session has disconnected and it closes on them.  Not ideal for me, I'd like them to be able to re-connect instead of shutting down.  My Reconnect Period is 01:30:00.  I'm on NAV 2015.

    I hope that helps.

    Jimmy Yu
    Enterprise Architect
    Step Energy Services Inc

  • 3.  RE: Idle Session Setup Issues

    Posted Feb 20, 2020 08:21 AM
    Thanks Jimmy! I have multiple service tiers on 4 servers and am having this issue on only 2 tiers on two different servers. The setup for keep alive and time out are the same values for everything. The others are working exactly how they should be....I'm stumped on the two that are not working. I'm wondering if perhaps there is other config I need to be checking that I'm not aware of?

    Matthew Dusenberry

  • 4.  RE: Idle Session Setup Issues

    Posted Feb 24, 2020 07:54 PM
    That's pretty weird. You may want to check to see if there are any jobs in NAV or SQL Server that override the settings. I've seen stored procedures running that do some crazy stuff. Also, look in the event log on the service tier and client and see if that gives you any clues. It's got to be something exotic or at least not normal.

    Jon Long
    Director of ArcherPoint-Upgrades
    ArcherPoint Inc.

If you've found this thread useful, dive deeper into User Group community content by role