Hello! I have had a web-based application running on a server for about a year and a half. We had no problems whatsoeverwith the app. It is simply retrieving data from the database and displaying them on the screen. Recently my hosting provider upgraded to Windows 2003. We have been pulling our hair out ever since. The application/scripts run fine for a certain amount of time, then:

Specified SQL Server not Found

on ANY and ALL pages that try to connect to the database. I have created a single class that opens the connection, passes parameters to a stored procedure, binds the data in the dataset (C#/.Net), and then explicitly CLOSES the database connection.

Once the error appears, we have to 'unload the application' - everything works fine again after that. It seems that there is something 'chewing' up the connection pool. I have turned connection pooling OFF for my application so it's got to be happening somewhere else. I have noticed that there are some system-based stored procedures that run very early in the morning (backup, update statistics). The error appears soon thereafter sometimes on the first access to the application (i.e. the first time someone accesses it).

We have had similar problems but from the other side i.e.
a SQL based application working fine from 9x/2K but when
run from XP it appears to open an enormous number of
connections (use Netstat -a) which eventually cause the
same error message you are receiving. There appears to be
a fundamental difference in the TCPIP stack. You could
also try looking at the MDAC version on your clients. You
might have to upgrade them to v2.8 (which is shipped with
2003). Hope this helps a little?



[quoted text, click to view]
server for about a year and a half. We had no problems
whatsoeverwith the app. It is simply retrieving data from
the database and displaying them on the screen. Recently
my hosting provider upgraded to Windows 2003. We have been
pulling our hair out ever since. The application/scripts
run fine for a certain amount of time, then:
[quoted text, click to view]
I have created a single class that opens the connection,
passes parameters to a stored procedure, binds the data in
the dataset (C#/.Net), and then explicitly CLOSES the
database connection.
[quoted text, click to view]
application' - everything works fine again after that. It
seems that there is something 'chewing' up the connection
pool. I have turned connection pooling OFF for my
application so it's got to be happening somewhere else. I
have noticed that there are some system-based stored
procedures that run very early in the morning (backup,
update statistics). The error appears soon thereafter
sometimes on the first access to the application (i.e. the
first time someone accesses it).
[quoted text, click to view]
on this problem so far, and have to get up at all hours to
reset the application. Please help!! :(
[quoted text, click to view]