Intermittent SQL Server does not exist or access denied.

Hi, I have a web application which is taking a fair bit of traffic.
It involves a registration process, and then a series of questions which
must be answered. The SQL server receives upwards of 1,000,000 queries a
day.
Unfortunately on a small number of these queries (~500 a day), the ASP pages
are returning that the SQL server does not exist or that access if denied.
Having explored the Microsoft Support Site, and exhausted all possible
solutions, without actually reaching a solution - I was wondering - is it
possible that the server is actually just taking so many requests that it
can't be found? Surely this should return a timeout?
The web box is a Windows 2000 IIS installation, and the SQL box is a
separate Windows 2000 / SQL Server 2000 installation.
Anyone got any ideas?
Many thanks.
MattWhat are you using to handle connections -- TCP/IP sockets, named pipes or
both? I would double check your IIS server and SQL server to make sure the
server and client network utilities match up with connection parameters.
Have you tried using Performance Monitor on the SQL server? You will take a
small performance hit, but you can get some more information on what is
happening when the connection fails. You should probably start off
monitoring a few basic SQL counters -- like for reads, writes and
connections.
When a SQL connection can't be made, the SQL server does not exist or access
denied is actually a common error. In my line of support, it usually means
that a network connection (ipc$) between the client and server can't be
made, but I imagine this is not the case for you.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Matt Pallatt" <matt.pallatt@.bnm.co.uk> wrote in message
news:%23ZMUOpzQEHA.3124@.TK2MSFTNGP12.phx.gbl...
> Hi, I have a web application which is taking a fair bit of traffic.
> It involves a registration process, and then a series of questions which
> must be answered. The SQL server receives upwards of 1,000,000 queries a
> day.
> Unfortunately on a small number of these queries (~500 a day), the ASP
pages
> are returning that the SQL server does not exist or that access if denied.
> Having explored the Microsoft Support Site, and exhausted all possible
> solutions, without actually reaching a solution - I was wondering - is it
> possible that the server is actually just taking so many requests that it
> can't be found? Surely this should return a timeout?
> The web box is a Windows 2000 IIS installation, and the SQL box is a
> separate Windows 2000 / SQL Server 2000 installation.
> Anyone got any ideas?
> Many thanks.
> Matt
>|||So connection/session pooling should be in use for large web based
applications. If you've disabled connection/session pooling then this
would put a heavier burden on the server.
What is your connection Timeout value?
What is running on the server when the timeouts happen?
Is there any blocking?
How many web servers are connecting to the SQL Server?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||We were having the exact same problem. It seems that by stopping SQL Server
from listening on named pipes (ie. just leaving tcp/ip) stopped the problem|||Sorry, may have spoken too soon. Our error have come back.