or even better, find the task that is using up all the connections, and fix it! ;-)
Run an activity monitor on the SQL server and see what connections are active.
cheers.
Main Topics
Browse All TopicsI have a Windows 2000 Server running approximately 30 websites and MS SQL Server 7.0. Most of the sites are dynamic and pulling information from the database. Occasionally (once a week or so) I get the following error on all of the sites that access MSSQL:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.
/includes/dbConn.inc, line 6
I know for a fact that the SQL Server does exist. Further, I'm able to access the DB through SQL Query Analyzer, so I don't think the problem is with SQL Server. I put each of these sites in their own memory space by setting "Application Protection" to "High (Isolated)" in IIS, but this doesn't seem to have made any difference.
When I get this error, I've tried restarting the MSSQL service & restarting IIS but neither has made any difference. The only way to fix the problem is rebooting the server, which is annoying as hell. Can anyone give me any guidence on this?
Thanks in advance.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Here's a cute solution in case you can't resolve this problem: how to promptly notice the problem and reboot the server - the idea comes from Russian joke site http://www.anekdot.ru
Put another server with Linux. The 2nd server's only job is to periodically ping the 1st server (in your case, to periodically connect to sql server on the 1st server same way as your websites do). When the next attempt fails, meaning it's the time to reboot 1st server, the monitoring application on the 2nd server ejects CD tray, which pushes the button "reset" on the 1st server.
Sounds like IIS and SQL are on the same box... yes? Assuming that, you should be using a different protocol as vadimrapp1 suggested. In adddition you should use a DSNless connection using OLEDB. Example:
cn.Open "Provider=sqloledb;" & _
"Data Source=servername;" & _
"Initial Catalog=databasename;" & _
"User Id=userid;Password=userpas
Make sure connection pooling is turned on.
Check your client network config using CLICONFG
fs
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I will leave the following recommendation for this question in the Cleanup Zone:
PAQ: No Refund
Any objections should be posted here in the next 4 days. After that time, the question will be closed.
meverest: Experts Exchange Cleanup Volunteer
Business Accounts
Answer for Membership
by: vadimrapp1Posted on 2007-05-11 at 19:34:52ID: 19076884
Most likely, some leak that eventually exhausts some tcp/ip-related resource. Try another protocol, for instance named pipes, or even better, shared memory, instead of tcp/ip.