> My client has a server running Windows 2003 Server and SQL Server
> 2000. The sole purpose of the server is to run a single web site.
> It was previously hosted with Verio and except for a problem backing
> up the SQL database, it ran just fine.
> Since it's been moved to the new web server we've had intermittant
> connection problems between the ASP code and the SQL server:
> Microsoft OLE DB Provider for SQL Server error '80004005'
> [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
> access denied.
> /gov/vendor/index.asp, line 106
> All you have to do is wait a few seconds, refresh and everything is
> What's strange is that we don't have this problem on our development
> server which is set up 99% the same as the client's server. However,
> their server is running dual 3 Ghz P4's with 4 gigs of RAM and my
> development server is a 633Mhz system with 512 megs of RAM.
> I looked up the error on ASPFAQ and came across:
> which only pointed me to a knowledge base article:
> Niether of which helps. My guess is that too many people could be
> connected to the web site and SQL counts each web connection as a
> seperate connection. Does that sound plausible?