Exclusive Locks on Database

[Jack]

I'm not sure if this is the correct newsgroup to be asking
about this problem but here goes. We are running Terminal
Services on one of our servers to allow users to access an
application on that server from remote locations that have
slower speed lines. Within the last two weeks we've moved
SQL Server and the application that these people access
onto the same server that is handling the Terminal
Services for remote users. Since completing the SQL
Server move we've had a recurring problem of an exclusive
lock being put on the database. This never occurred when
SQL Server was running on another server. I can force
unlock the database to allow users access but that is not
a solution. I've heard that Terminal Services has
possible problems with applications that use System DSN's
and that we should change the Data Source to User DSN's.
Has anyone else heard of this problem and if so, should
User DSN's be used. Also if that is correct, is there any
way to create User DSN's for each user without having to
logon as that user and create them? Thanks for any help.
..

 

[Matthew Harris [MVP]]

Yeah, this is a problem that Microsoft knows about but
will not fix in Windows 2000. You might want to try
Windows 2003. However, I can't be sure that the problem
I'm thinking about is your problem, so you might want to
make sure you have the latest service pack installed.

Here are some links that might be useful:

support.microsoft.com/default.aspx?scid=kb;en-us;296264
support.microsoft.com/default.aspx?scid=kb;en-us;294816
support.microsoft.com/default.aspx?scid=kb;en-us;272582

-M