Hello, When Windows crash with a navision client opened, after some times, that session is always active for navision server, but there is no nav client Is it a way to ‘kill’ these ‘fantom’ session?
Restart the NAVISION Server (Service). Regards, Jörg Joerg A. Stryk Apollo-Optik, IT/ERP
Erm, Joerg, this also kicks all active users off the server and is nothing you would like to do in a company like ours There is a TCP/IP parameter which is responsible for the timeout of network sessions in general. I don’t know the details, but I think it’s documented in some Navision handbook. This parameter has to be set on the server and results in aborted sessions to be terminated after a few minutes. We haven’t had any zombie sessions ever since. Regards, – Heinz Herbeck Waagner-Biro AG, Vienna, Austria
this also kicks all active users off the server
… and that’s exactly what we are doing once a day, 18:00, no mercy Joerg A. Stryk Apollo-Optik, IT/ERP Edited by - stryk on 2002 Aug 09 13:26:10
Originally posted by stryk: … and that’s exactly what we are doing once a day, 18:00, no mercy
Cruel world… – Heinz Herbeck Waagner-Biro AG, Vienna, Austria
stop service … mmm active user don’t like that and boss … I dont find this parameter, but I look
Just checked with our network engineer… Microsoft Technical Reference Q120642 (available on www.microsoft.com) contains a (long) list of TCP/IP parameters. You will probably have to adjust several of them for your system. Good luck – Heinz Herbeck Waagner-Biro AG, Vienna, Austria
[quoteThere is a TCP/IP parameter which is responsible for the timeout of network sessions in general.
Right. Depending on the setting of this timeout parameter it might take anything between 5 minutes and 2 hours until the session is closed automatically. If you are running SQL DB, there are utilities available to kill the session. With best regards from Switzerland Marcus Fabian
your hints are very interesting and i had a look at Q120642 of the Microsoft-page. But can anyone be a little more specific which parameters have to be set to achieve the session killing ? just last week we had the case that a session which worked with table 37 was lost. After that table 37 was still locked. This happened late in the evening and we had to wait till the next morning when this session was killed. But i would prefer a smaller time a dead session is killed. thanks in advance Stefan Weinreich Billing Analyst
Our network engineer (who is currently on vacation…) told me that he had to modify several parameters, but unfortunately didn’t tell me which. I’d suggest that you first try KeepAliveTime TcpMaxDataRetransmissions These control the interval and the number of times TCP/IP checks a connection. – Heinz Herbeck Waagner-Biro AG, Vienna, Austria
If there is some other tcp /IP activity going on, lets say I have a download, going on a client machine… If we modify the tcp IP, keep alive time ? woudnt this affect those other applications? regards, Sharandeep.
Sharandeep, you need to set these parameters on the server, so client activities are not affected. Of course, if the client downloads something from the Navision server, then it does make a difference, since these parameters affect all TCP/IP connections on the server.
The parameter you’re looking for is the KeepAliveTime. You set this parameter in the registry of your server. The default value for that parameter ist 2 hours. Set the parameter to 5 minutes and the lost session will be closed after that time (normally). If the open TCP-port is the problem, then this should be the solution. A Navision client is - from the point of view of the server - an open TCP-Port. And as long as the port is open, the DBMS-server will recognize the session as alive. TCP sends alive-packages every xxx seconds (also set in a TCP-parameter) and if there is no response to such a package, then the server will wait for the → KeepAliveTime until he closes the session actively. Walter Kreutzner already posted a detailed description of the TCP-Parameters. If you look for “KeepAliveTime” you will find it. The parameters may change a little, depending on your server-OS. So maybe you should look for the appropriate description on MSDE. If you are the right one to change Network-parameters in the registry of your server, then this should be no problem for you BTW - the 2 hours are standard and work without having the KeepAliveTime-key in the registry. If you want to set your own value, then you will have to insert a new key in the registry.