web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Microsoft Dynamics NAV (Archived)

Idle Client Timeout NOT working after NAV 2013 CU 37

(0) ShareShare
ReportReport
Posted on by 5,136

Hello Experts! 


We just implemented the NAV 2013 CU 37 PLATFORM ONLY updates over the weekend.  Everything seemed fine.  However, for some reasons, the 'Idle Client Timeout' setting of 01:00:00 (1 hr) in the Client Services Tab of our NAV Service doesn't seem to work.  Users are NOT logged off automatically even passed 1 hour of no activities.

I already stopped and restarted our NAV Service just to make sure.

FYI, below are our settings in the client services of our NAV Service:

Idle Client Timeout=01:00:00  (to indicate 1 hr)

Max Number of Orphanned Connections=20

Reconnect Period=00:10:00

FYI, i checked the customsettings.config in the C:\program files\microsoft dynamics nav\70\service folder of our Nav server and i found below:

 <!--
    Maximum time in seconds a call from the client to the server
    may take to return.
    Time span format: [dd.]hh:mm:ss[.ff]
        dd: days
        hh: hours
        mm: minutes
        ss: seconds
        ff: fractions of a second
    Or "MaxValue" to indicate there is no timeout.
  -->
  <add key="ClientServicesOperationTimeout" value="MaxValue" />
  <!--
    The security services used to protect the client/server data stream.
    Valid options: EncryptAndSign, Sign, None
  -->
  <add key="ClientServicesProtectionLevel" value="EncryptAndSign" />
  <!--
    Maximum number of concurrent client calls that can be active on the
    Microsoft Dynamics NAV Server. To disable this setting set the value
    to "MaxValue".
  -->
  <add key="MaxConcurrentCalls" value="40" />
  <!--
    The maximum number of concurrent client connection that the service
    will accept. To disable this setting set the value to "MaxValue".
  -->
  <add key="ClientServicesMaxConcurrentConnections" value="150" />
  <!--
    Sets the grace period within which the client can reconnect to a
    running session.
    Time span format: [dd.]hh:mm:ss[.ff]
        dd: days
        hh: hours
        mm: minutes
        ss: seconds
        ff: fractions of a second
    Or "MaxValue" to indicate there is no timeout.
  -->
  <add key="ClientServicesReconnectPeriod" value="00:10:00" />
  <!--

You think this is overwriting my settings?

Thoughts?

*This post is locked for comments

I have the same question (0)
  • Verified answer
    mbr Profile Picture
    5,136 on at
    RE: Idle Client Timeout NOT working after NAV 2013 CU 37

    Hi All,

    I have figured it out. With the CU that Nav did (in my case CU37) for Nav 2013, the Client Idle Timeout will not work for any settings higher than 2 minutes.  One would need to ensure that the   ClientServicesKeepAliveInterval key in the ClientUserSettings.config is also set up to be at least 1 min higher than the Client Idle Timeout.  If this key is not present in the ClientUserSettings.config, users will stay logged on regardless of the Client Idle Timeout Settings (if set up as higher than 2 minutes).

    So all you have to do is add below key in the ClientUserSettings.config.  Below is setup

     <add key="ClientServicesKeepAliveInterval" value="660" />

    whereby Client Idle Timeout = 00:10:00 (for 10 min).

    That should do it!

  • mbr Profile Picture
    5,136 on at
    RE: Idle Client Timeout NOT working after NAV 2013 CU 37

    Another FYI:

    In the CustomerSettings.Config of the Nav c:\program files\....\70\Service folder, should i change the ServicesDefaultTimeZone from "Server Time Zone" to "UTC"?

    Also, in the CustomerSettings.Config, should i remove below?

    <add key="ClientServicesIdleClientTimeout" value="01:00:00" />

    Our Test Environment which has the same version NAV (including CU37) works as far as auto logging the users after 1 hr of no activities.  And in Test, there is no entry for ClientServiceIdleClientTimeout in the customersettings.config in the test server.

    Please advise.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Mansi Soni – Community Spotlight

We are honored to recognize Mansi Soni as our August 2025 Community…

Congratulations to the July Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans