Using dedicated Win 2003 SQL Server (sp4) with Rackspace. We recently moved to Rackspace, and now often recieve the error: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. from the ASP website running on another dedicated Windows 2003 server.
There's a lot of traffic to the site, 100 new visits per minute approx., and sometimes we get the error above....but then it goes away a minute later.
This is a sporradic problem, so I think it's SQL server setting related....but Rackspace says not and we'd have to hire someone to fix it from Rackspace.
I ran Index Tuning Wizard the other day and created 4-5 new clustered indexes....but the problem still exists.
I'm sure this is not an easy answer, and very broad...being that the MS error description is so friggin vague, but any thoughts appreciated.
NOTE: This is NOT a naming or connection string issue....it only happens randomly.
Seems to be related to too many connections at the same time. Ever seen this message from that?
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.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
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.
Set up a script to run every 5 minutes to ping the ip address of the SQL server check the log tomorrow and if there are any dropped packets you got em!
***<Note from Moderator: see http:#15305052 for updated information>***
Well, the only thing that I see is that the ping time jumps a little when these errors exist. During times when the error "SQL Server does not exist or access denied" occured, the ping response time would jump from 47 to 63. All other times the reply time=47. But, it would respond from IP.
Any thoughts?
I have found the answer to this question. See here for details:
You need to create new registry settings:
path: HKEY_LOCAL_MACHINE\System\
type: DWORD
name: TcpTimedWaitDelay
value: 30 (decimal)
type: DWORD
name: MaxUserPort
value: 10000 (decimal)
For details see:
http://support.microsoft.c
And it should also be pointed out, that this fix is intended if you have disabled connection pooling (which for obvious reason is not recommended).
<quote>
Turning off pooling can cause the underlying SQL Server network driver to rapidly open and close new socket connections to the computer that is running SQL Server. You may have to change default TCP/IP socket settings for the operating system and the computer that is running SQL Server to deal with the higher stress levels.
Note that this article only discusses settings that affect the SQL Server network library when you use the TCP/IP protocol. Turning off pooling can also cause stress-related problems with other SQL Server protocols such as named pipes, but this article does not discuss this topic. This article is for advanced users only. If you do not understand the topics in this article, Microsoft recommends that you see a good book about TCP/IP sockets.
Note that Microsoft strongly recommends that you always use pooling with the SQL Server drivers. Using pooling greatly improves overall performance on both the client side and SQL Server side when you use the SQL Server drivers. Using pooling also considerably reduces network traffic to the computer that is running SQL Server. For example, a sample test that used 20,000 SQL Server connection opens and closes with pooling enabled used about 160 TCP/IP network packets, for a total of 23,520 bytes of network activity. With pooling disabled, the same sample test generated 225,129 TCP/IP network packets, for a total of 27,209,622 bytes of network activity.
</quote>
Thanks, it's not a Rackspace server that's causing the problem but I did a netstat -n check on a Rackspace server we have and didn't get any TIME_WAIT lines back. Maybe you've paved the way for us with Rackspace!
It's at a client site where the problem is and occurs during their stress testing, get's up to around 90 users and then they all fail with the error above.
we'll give the reg change a try, and I guess if they run the netstat it should tell us if this is the problem.
Business Accounts
Answer for Membership
by: theRiddlerPosted on 2005-10-10 at 08:37:46ID: 15052970
May want to post your connection string. Are you using IP address or name to connect?
Here is some info in MS KB:
http://support.microsoft.c