Hi!

I'm having a problem in a customer's netwok:


We have an application that connects to a SQL Server from multiple
terminals via ODBC, but sometimes (I don't know why) the server stops
responding to new connections. The terminals that already had an open
connection works fine, but the others receive no answer from the server.
Closing and reopening the application doesn't help. If I close an active
terminal and try to open it again I get the same problem. The only
solution as for now is restarting the server.

SQLServer version is 2000. Any clues ?

The network administrator told me that they had the same problem and
changed the connection from ODBC to OLEDB and it worked fine

Yes change the provider to point to sqloledb driver and install latest MDAC 2.
81 version on clients as well.

Darío Alejandro Guzik wrote:
>Hi!
>
> I'm having a problem in a customer's netwok:
>
>
>We have an application that connects to a SQL Server from multiple
>terminals via ODBC, but sometimes (I don't know why) the server stops
>responding to new connections. The terminals that already had an open
>connection works fine, but the others receive no answer from the server.
>Closing and reopening the application doesn't help. If I close an active
>terminal and try to open it again I get the same problem. The only
>solution as for now is restarting the server.
>
>SQLServer version is 2000. Any clues ?
>
>The network administrator told me that they had the same problem and
>changed the connection from ODBC to OLEDB and it worked fine

--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums...ivity/200603/1

It's not so easy as it sounds. The application uses some specifico
components to connec to to the database and the change is not so straight.

Is there a way to resolve it at the srever side?

ranjitjain via SQLMonster.com wrote:
> Yes change the provider to point to sqloledb driver and install latest MDAC 2.
> 81 version on clients as well.
>
> Darío Alejandro Guzik wrote:
>> Hi!
>>
>> I'm having a problem in a customer's netwok:
>>
>>
>> We have an application that connects to a SQL Server from multiple
>> terminals via ODBC, but sometimes (I don't know why) the server stops
>> responding to new connections. The terminals that already had an open
>> connection works fine, but the others receive no answer from the server.
>> Closing and reopening the application doesn't help. If I close an active
>> terminal and try to open it again I get the same problem. The only
>> solution as for now is restarting the server.
>>
>> SQLServer version is 2000. Any clues ?
>>
>> The network administrator told me that they had the same problem and
>> changed the connection from ODBC to OLEDB and it worked fine
>