Re: SQL Server does not exist or access denied.

There are a number of things that could be going on here. Let's get some
more info on your environment

What transport are you using (TCP, LPC, NP)?
TCP has is less overhead and network reads/writes over NP.
Check out the following KB's for tweaking your TCP ack depending on your
environment
http://support.microsoft.com/kb/328890/
http://support.microsoft.com/default.aspx?scid=kb;en-us;q315669

There is also a limit on the number of open TCP ports that you can have
at any given time.
There are others under HKLM\SYSTEM\CurrentControlSet\Services\TcpIp
check it out on MSDN.

Are you using SQL auth?
I have seen issues if the DC isn't available (network) and you're using
domain users.

What is the load of the client(s)/server connecting? Are there any specific
loads during failure time?
If either are under heavy memory / cpu pressure you could experience
dropped connecitons.

I would really like to help understand what's going on in your environment.

Have you considered using connection pooling? A million connections per day
is about 10-12 new connections per second. That could be a significant load
depending on how much work is going on in the engine.

--
Brad Sarsfield [MSFT] bradsa(at)microsoft.com

This posting is provided "AS IS", with no warranties, and confers no rights.

<stevehunter_1@xxxxxxxxxxx> wrote in message
news:1128030310.743829.224010@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>I get the following error when trying to connect to SQL Server
>
> SQL Server does not exist or access denied.
> ConnectionOpen (Connect()).
>
> Scenario:
>
> The application connects to SQL Server very frequently (million+ times
> per day). It fails with this error message about 100 times.
>
> The failure rate is not very high and unfortunately, I can not open one
> or more connections. I must open connection and close and do this
> again a million times.
>
> So I need to solve this problem. Where would you start? I set
> timeout to 2 minutes and this helped a lot, but i still get errors.
>


.

Relevant Pages

  • RE: Cannot Connect to SQL 2000 on Win2k3 Server
    ... In that case remote connections would fail ... because by default clients try to connect with TCP. ... on the box to SP3 then retry connecting. ... Potential Causes of the "SQL Server Does Not Exist or Access ...
    (microsoft.public.sqlserver.connect)
  • RE: Cannot connect to MSDE on a W2003 server
    ... Did you apply the SP3 version of MSDE? ... If not TCP will be disabled on ... Do both remote and local connections fail for each protocol? ... Click the desired instance of Microsoft SQL Server 2000 Desktop Engine ...
    (microsoft.public.sqlserver.connect)
  • Re: .NET SqlConnection: connect error SQL Server 2005 DEV on same
    ... I think Rick's point is that you should not use/activate TCP/IP for local connections as it forces the client application to navigate through the network stack to get to the server. ... If I wanted to specify the port in the conenct string, ... enable TCP in the surface area configuration? ... Rick Byham, SQL Server Books Online ...
    (microsoft.public.sqlserver.connect)
  • Re: Setting Open FDs to 16,384
    ... The TCP based application runs fine under 2000 established TCP ... > connection, but once the app starts handling over 2000 TCP connections, ... I would use rlim_fd_max and make sure the process can raise the limit ... or it is launched in an environment that can raise it. ...
    (comp.unix.solaris)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... connections need to be returned to the pool to be ... Enterprise version of SQL Server 2000. ... server user login to be sure that it is not mixed with other running clients). ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)