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

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.