NAV2013R2 - Clients Sessions aren't disconnected

(0) Share

Report

Posted on by Community Member

Hy, I describe our current configuration

SQL2008R2
NAV2013R2 - CU25
2 Services DynamicsNAV71_S01 and DynamicsNAV71_S02 points to the same database. The services are on the same Server NAV_SV01 with differents ports. Both were created from the default Istance DynamicsNAV71 (Istance subfolders)
All Clients are Windows Clients (from terminal servers)
2 NAS: one for service
For limit connections (and licences used) we've configured both services with this parameters
- - Idle Client Timeout: 00:10:00 (ten minutes)
  - Max Number of Orphaned Connections: 5
  - Reconnect Period: 00:10:00

On DynamicsNAV71_S02 the clients are correctly disconnected from the service.

On DynamicsNAV71_S01 clients remain always active and sometimes there are more connection for the same user in the session list (One with Windows Client in Client Type column and on with background).

We have this problem after Upgrade to CU24 (before we have CU16 and the clients were disconneteced from DynamicsNAV71_S01 )

We try to delete and recreate DynamicsNAV71_S01 service with no success. We think that the problem could be on sql Session Event Table... but before delete records I ask here ;-)

Thanks

*This post is locked for comments

I have the same question (0)

All responses (11)

Answers (2)

keoma 32,729 on at

Like (0)

Report

some connections are held by the nav service (background).

did you solve the issue ?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hy Jonathan, i didn't solve the issue, 2 connections are correctly held by nav service but some users connection remains in background state... it's very strange and I think the problem is Session Event Table.

Thanks!

Was this reply helpful? Yes No
keoma 32,729 on at

Like (0)

Report

the session event table can sometimes make problems, especially in scenarios like yours. why do you have 2 nav service instances with the same database? i think that this issue has something to do with that.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I create the second service DynamicsNAV71_S02 for testing, normally I've only DynamicsNAV71_S01.

Next days after a backup and I'll try to delete all entries from session table.

Best Regards

Marco

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report

I've resolved it!

Someone... has changed the user mapping from dbo to the old nav$listner... in sql server. The navservice user has permissions problems.

Thank's!

W t'pol ;-)

Was this reply helpful? Yes No
keoma 32,729 on at

Like (0)

Report

changing the user mappings :-( bad thing. but, it's solved. greetings and

Qapla' !

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report

Sorry but there's something that I don't understand in configuring session timeout in the help guide.

My scope: I want to close an inactive connection after 15 minutes of inactivit (users leave windows client open...) to release licence.

From the Help

Server Side:

Idle Client timeout 00:05:00

Reconnect Period 00:10:00

Client Side (ClientUserSettings)

If I leave <add key="ClientServicesKeepAliveInterval" value="120"/> the client sends "I'm alive" every 2 minutes, so the session never close for me.

For me (and i try it) the correct value for ClientServicesKeepAliveInterval is a value greater than Idle Client timeout.

The guide for me it's not very clear... or i'm wrong ...

Thanks

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

If you want to close a connection after 15 minutes of it being inactive, just set the 'Idle Client Timeout' to 00:15:00. Don't forget to restart the service. Hope this answers your question!

Was this reply helpful? Yes No
phenno on at

Like (0)

Report

I have the same issue on NAV2015. If I set ClientServicesKeepInterval to value higher than Idle Time that NAV disconnects session. But if it's lower, it doesn't. Also, I can see on perf counter "Server Operations/sec" that it generates hit on keepalive packet, althought in documentation for counter it says that hits are generated only for C/AL object runs.

Was this reply helpful? Yes No
phenno on at

Like (0)

Report

Well, after little digging I found out that this behaviour occurs after CU 12 (42951) applied. I've checked what were the platform changes in that CU and found an intersting line saying:
375708 Connection cannot be resumed after the client has timed out.

It seems to me that now they broke it to the level that client cannot timeout at all, if in idle state.

Same correction was made to NAV2013 in CU 31 (42948), and to NAV2013 R2 in CU 24 (42950)

I've checked latest CU and it still cannot timeout on idle.

Was this reply helpful? Yes No