PHWinfo - Afficher un message

07/04/2008, 04h03

Hi Stefano

Stefano wrote:
> After buying a new database server running Sql Server 2005 Win
> 2003,sometimes happens tha after a period of user inactivity (about 1
> hour) , when the user restarts his activity a general network error is
> raised and ERP crashes
> It sounds like ,in the meantime,the sql server database hanged up the
> connection.

Just to let you know, you're not alone with this problem. We've
experienced this ourselves. Any application that only opened a
connection once can suffer from this.

> Any idea

A number of people have suggested it is to do with Keep Alives. For us
the solution of disabling keep alive packets did seem to reduce the
problem, but it has not eliminated it (A situation which, by the way,
makes no sense to me. I would have thought it would either fix it or do
nothing, NOT sort of fix it).

Posts by brianpaulflynn in the following thread may be ful to you...
http://forums.microsoft.com/MSDN/Sho...02016&SiteID=1

The final (solution) post in thread did not work for us either.

As you can probably tell I'm a bit stumped and confused about this
problem. Another line of inquiry could be the network cards used. What
cards to you have on your server/client pcs ?

Regards
Clint.

07/04/2008, 04h03	#3
Clint Good Messages: n/a Hébergeur:	Re: SQL 2005 automatically disconnect Hi Stefano Stefano wrote: > After buying a new database server running Sql Server 2005 Win > 2003,sometimes happens tha after a period of user inactivity (about 1 > hour) , when the user restarts his activity a general network error is > raised and ERP crashes > It sounds like ,in the meantime,the sql server database hanged up the > connection. Just to let you know, you're not alone with this problem. We've experienced this ourselves. Any application that only opened a connection once can suffer from this. > Any idea A number of people have suggested it is to do with Keep Alives. For us the solution of disabling keep alive packets did seem to reduce the problem, but it has not eliminated it (A situation which, by the way, makes no sense to me. I would have thought it would either fix it or do nothing, NOT sort of fix it). Posts by brianpaulflynn in the following thread may be ful to you... http://forums.microsoft.com/MSDN/Sho...02016&SiteID=1 The final (solution) post in thread did not work for us either. As you can probably tell I'm a bit stumped and confused about this problem. Another line of inquiry could be the network cards used. What cards to you have on your server/client pcs ? Regards Clint.