From: Ellen K. 

Well, that is mildly comforting in that Lawson is a capital-N Name app.

I can understand how it wouldn't recognize a remote user though... for
example I have all my SQL Servers set to use Windows authentication, if we
start doing web apps I hafta figure out how to do the security.   (I
asked about this awhile back and Rich mentioned that it is possible for one
server to pass on its authentication to another, I forget the official term
he used, but so far I didn't need it because the web (really only intranet)
users have to log into the one web app we have so far with their username
and password, and then there is a fake user on the webserver which is the
user SQL Server "recognizes", i.e. all of them have the exact
same privileges.)

When we get the held resources situation, they end up having to restart the
server because trying to kill the zombie users abends it.

On Fri, 28 Jan 2005 10:19:34 -0600, "Glenn Meadows"
 wrote in message :

>We have/had a similar issue with our Lawson application.  It's a Cobol
>program, and the version for Windows 2000 has no ability to know if the
>remote session is still connected (dumb program, but that's another thread).
>Since we've recently been doing remote access to that machine now (via VPN),
>any network burble would drop the connection, and the remote user would have
>to login again.  Lawson had no way of knowing that it was the same user
>logging in again, or to connect again to the same session, so it happily
>creates a new session, leaving the old one orphaned.  Eventually, we'd hit
>the maximum number of registered users, and nobody could log in.  I'd have
>to stop the Lawson Environment, and restart it to clear out the orphaned
>sessions.  Got to be a real PITA as our router was slowly dying.
>
>Sounds similar.  Many apps don't take into account remote sessions, and that
>there might be a break in the connection.

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