We have confirmed that using the three-finger salute or the close box (X at
the top right corner of the application) causes the held resources problem.
 In fact, the box that causes it can even be shut down after that and the
server still refuses to release the connection.  We learned that this is a
known issue with the Novell NLM (whatever an NLM is).

However, I have felt from the beginning that there was some network-level
component to the whole situation because we really never fixed the
packet-loss issue and from time to time I still get kicked off of or timed
out on my SQL Server boxes.  What occurs to me now after reading your post
(although this is completely not what you are saying) is that it could be a
network issue that is slowing down the performance on the desktop to the
extent that they want to kill the app because they THINK it's frozen. 

> From: "Geo" 
> "Ellen K." 
wrote in message
> news:t5civ0tshe0fo0969i7gta1lvq9ub35ram{at}4ax.com...
>> My theory is that recent modifications to the application cause it to
>> freeze on the desktop and that is why we are suddenly seeing so many
>> users giving it the three-finger salute.
> Have you confirmed that this is the cause? I've also seen this sort of thing
> happen when there is a momentary network outage, the connection gets lost
> and the far end never gets a reset command. I would think if they kill the
> app that the network driver would at least send a close signal to the remote
> server.
> I'd test it to see if killing the app is causing the resource exhaustion at
> the db end. Try to make it happen, if it doesn't then it could be some sort
> of network issue (you had some of those in the past).
> Geo.

--- BBBS/NT v4.01 Flag-5