Skip to main content

NAV Three Tier - Auto Kill Idle Session..

Hi all,

This question was asked by one of my Friend, and i thought i will share will all.

Normally we have some code written till NAV 2009 or in SQL to kill an Idle Navision Session.



The Code was working fine till NAV 2013 Where the session table has been changed, Now with NAV 2013 we don't have a parameter of IDLE Time in the session table.



So how we can kill Idle Sessions automatically?

If you check the service tier of NAV 2009 and Later, we have a parameter -

NAV 2009 / NAV 2009 SP1 / NAV 2009 R2 - "ClientReconnectPeriod".
NAV 2013 / NAV 2013 R2 - "Idle Client Timeout".

This parameter can be used to acheive the same in easy way.
And the best part is we don't need to code anything.
*The Default Value in the field is MaxValue.



How to use the Parameter - "ClientReconnectPeriod" OR "Idle Client Timeout".

*Below Steps are performed in NAV 2013 R2 but steps remain same for all Three Tier Version released Till date. For 2009 you need to change them in the configuration file.

1. Open the Service Tier.

2. Edit the service that you want to set the Auto Kill Session.

3. Go to Client Services Tab.

4. Put the time delay in "Idle Client Timeout".

5. Format it Support is [dd.]hh:mm:ss[.ff] where dd (DAY) ff(fractions of a second) are optional.

6. Support you want to disconnect a client idle for 20 minutes then use - 00:20:00

7. In my case i am using 02 minutes. - 00:02:00 as shown below.



8. Save and Restart the service.

DEMO -

1. I started two session of Client out of which i am using Session ID 14 as active while session ID 12 is IDLE(Minimized on my screen).



2. After Exactly 2 minutes the session with ID 12 will be removed from list.



3. When user from session 2 try to access the client he/she ends up with an error message.



Points to remember -

For Other Features like WebServices/JetReports/NAS/Web Client/Sharepoint Client you need to create a separate service as they will be idle for the time you specified in "Idle Client Timeout".

I hope the post will be helpful to all as its a conman requirement by most of the client.

Regards,
Saurav Dhyani
saurav-nav.blogspot.in

Comments

Post a Comment

Popular posts from this blog

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

RTC Report It is not possible to instantiate the Visual Studio bridge.

Hi all, As a Navision developers I have Multiple Versions of Navision running in single Machine. As discussed Earlier in the post how to run multiple Version of RTC in single machine. So my machine have following details for RTC Versions - NAV 2009 R2    - is installed. NAV 2009 SP1  - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 SP1 IN\ NAV 2009         - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 IN\ This approach has been working great for execution of Classic and RTC Clients. However, after installing Dynamics NAV 2009 R2, if i tried to view the Layout for an NAV 2009 SP1 Report i was getting the following error: ---------------------------  Microsoft Dynamics NAV Classic  ---------------------------  It is not possible to instantiate  the Visual Studio bridge.  ---------------------------  OK    --------------------------- After searching for the error i figured out the issue was due to - Design change in NA

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.