DB errors after upgrading from Win2k to Win2k3

We have a few popular sites sharing a database. We were running smoothly on
Windows 2000, but then we did a hardware upgrade and an OS upgrade to Window
s 2003. Since then we've been having a lot of DB errors. I've optimised the
queries and took down the n
umber to somewhere near 1/15th the number of queries the 2000 server was han
dling fine. The errors have clearly went down in frequency, yet not complete
ly.
The most common error is:
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied.
followed by:
Timeout expired
and lastly (this happened only a few times):
[DBNETLIB][ConnectionRead (recv()).]General network error. Check you
r network documentation.
It seems I'm not the only one having such problems, having seen it being men
tioned quite a few times in forums. Does anyone have a solution please?Mark,
We are having the same problem. We upgrated from Win2000 to Win2003. We open
ed ticket with Microsoft and they still haven't found the solution.
I found a thread that stated that people on Win2000 with SQL Server SP3 had
the same problem. I think it is SP3 because you have to install SP# for SQL
if you are planning it to run on Win2003.
Thanks,
Anna
"Mark Cilia Vincenti" wrote:
[vbcol=seagreen]
> PS - the errors are intermittent, and right now make a very small percenta
ge of the number of requests. However we are planning improvements which wil
l take the queries up again, and we need to solve this problem first.
> "Mark Cilia Vincenti" wrote:
>
he number to somewhere near 1/15th the number of queries the 2000 server was handling fine.
The errors have clearly went down in frequency, yet not completely.[vbcol=seagreen]