problem : random error with with IIS6 and MSSQL

[JackTorrance]

Hi i have a problem with IIS6 and MSSQL and i hope that someone can
help me.

this is the configuration:

Windows 2003
IIS6
MSSQL 7.0 Standard Edition

ADO 2.5
I have the following error that occur randomly when browsing my
websites.
Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionOpen (Connect()).]
Server SQL inesistente o accesso
negato.

(translate from italian: Server unexisting or access denied)
it occurs when users (more than one but not hundred...) browse some
asp pages where there's a lot of
recordset opening-closing acivity. The ado connection is correctly
open once and closed at the end of the script
and all recordset are opened as static.

It also happens if a single user refreash repeatedly that pages.
It seems that mssql says it doesn't exists but i think it want to say
it is too busy.
However the load is not excessive and the same pages works perfectly
on a system using Windows 2000 Server
and the same version of mssql installed.
One more thing ..... for some reasons that i can't control MSSQL and
IIS are on the same server.

Can anyone help me ? It's just a lack of performance or there is some
misconfiguaration in MSSQL (as i think...). ?

Could the IIS6 application pool configuration cause this problem ?

I don't know what to say....thanks in advance.

[Erland Sommarskog]

JackTorrance (sp**@spam.com) writes:

this is the configuration:

Windows 2003
IIS6
MSSQL 7.0 Standard Edition

ADO 2.5
Why 2.5? On Windows 2003 you have 2.8.
I have the following error that occur randomly when browsing my
websites.
Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionOpen (Connect()).]
Server SQL inesistente o accesso
negato.
...
It seems that mssql says it doesn't exists but i think it want to say
it is too busy.

I can'r really help, but I like to point out that the error message does not
come from SQL Server, but from the SQLOLEDB provider, and the error simply
means that the connection failed, because SQLOLEDB cannot make contact.

I seem to recall having seen this before with this setup, that is IIS +
SQL Server on the same machine. As I don't use IIS myself, I have not
really paid attention to the resolution of these problems.

--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp