ODBC Drivers error '80004005'

Hello, I am running IIS 6.0 on a windows 2003 server. I have an asp page
that accessed a SQL server 2000 running on windows 2003 through DSN. Every
once in a while the webpage becomes inaccessable and gives the following
message:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][DBNETLIB] General network error.
Check your network documentation.
/direct/dbConn.asp, line 34

Line 34 of the asp file contains the line:
adoCon.Open "dsn=DatabaseConnect;uid=login;pwd=test"

The webpage doesn't just comeback after a few minutes but instead stays
inaccessible until the SQL Server is restarted.
The only way around this problem has been to restart the SQL server every 3
hours in order to decrease the webserver downtime.
Please help,
Danny

Ken
Mon Feb 20 23:03:48 CST 2006

Why do you think this is an IIS issue?

Cheers
Ken

"Dannyb" <dannyb@alianza.com> wrote in message
news:%23b1POLqNGHA.812@TK2MSFTNGP10.phx.gbl...
: Hello, I am running IIS 6.0 on a windows 2003 server. I have an asp page
: that accessed a SQL server 2000 running on windows 2003 through DSN.
Every
: once in a while the webpage becomes inaccessable and gives the following
: message:
: Microsoft OLE DB Provider for ODBC Drivers error '80004005'
: [Microsoft][ODBC SQL Server Driver][DBNETLIB] General network error.
: Check your network documentation.
: /direct/dbConn.asp, line 34
:
: Line 34 of the asp file contains the line:
: adoCon.Open "dsn=DatabaseConnect;uid=login;pwd=test"
:
: The webpage doesn't just comeback after a few minutes but instead stays
: inaccessible until the SQL Server is restarted.
: The only way around this problem has been to restart the SQL server every
3
: hours in order to decrease the webserver downtime.
: Please help,
: Danny
:
:

Dannyb
Tue Feb 21 09:19:53 CST 2006

Well, truthfully I am unsure weather this is the right area for this post or
not. I posted it here because it was a website error and in the
sqlserver.odbc newsgroup because that is the type of error I recieved. If
there would be a better area please let me know.
Danny
"Ken Schaefer" <kenREMOVE@THISadOpenStatic.com> wrote in message
news:eR$ozQqNGHA.2816@TK2MSFTNGP15.phx.gbl...
> Why do you think this is an IIS issue?
>
> Cheers
> Ken
>
> "Dannyb" <dannyb@alianza.com> wrote in message
> news:%23b1POLqNGHA.812@TK2MSFTNGP10.phx.gbl...
> : Hello, I am running IIS 6.0 on a windows 2003 server. I have an asp
> page
> : that accessed a SQL server 2000 running on windows 2003 through DSN.
> Every
> : once in a while the webpage becomes inaccessable and gives the following
> : message:
> : Microsoft OLE DB Provider for ODBC Drivers error '80004005'
> : [Microsoft][ODBC SQL Server Driver][DBNETLIB] General network error.
> : Check your network documentation.
> : /direct/dbConn.asp, line 34
> :
> : Line 34 of the asp file contains the line:
> : adoCon.Open "dsn=DatabaseConnect;uid=login;pwd=test"
> :
> : The webpage doesn't just comeback after a few minutes but instead stays
> : inaccessible until the SQL Server is restarted.
> : The only way around this problem has been to restart the SQL server
> every
> 3
> : hours in order to decrease the webserver downtime.
> : Please help,
> : Danny
> :
> :
>
>

Jim
Tue Feb 21 12:34:20 CST 2006

You are probably hitting the number of ODBC connection limit (per
processor). This sometimes happens if you end up looping thru the
"adocon.open" section. You could check this by looking at the ODBC
perfmon counters. Try changing to a dsnless connection using OLEDB.

Dannyb
Tue Feb 21 13:21:20 CST 2006

Wow, sounds like I am talking to the right person. I however, am a
completely new to SQL Server. How would one go about setting up a log of
the odbc counters?
Thanks,
Danny
"Jim B" <jim.butts@gmail.com> wrote in message
news:1140546860.629897.250100@g43g2000cwa.googlegroups.com...
> You are probably hitting the number of ODBC connection limit (per
> processor). This sometimes happens if you end up looping thru the
> "adocon.open" section. You could check this by looking at the ODBC
> perfmon counters. Try changing to a dsnless connection using OLEDB.
>

Ken
Tue Feb 21 21:54:29 CST 2006

Sorry, but /don't/ think this is the issue. The issue here seems to be
related to SQL Server and/or transient network problems. This correlates
with the error message received, and also with the fact you need to restart
SQL Server to get things working again.

Cheers
Ken

"Dannyb" <dannyb@alianza.com> wrote in message
news:ucktDwxNGHA.2604@TK2MSFTNGP09.phx.gbl...
: Wow, sounds like I am talking to the right person. I however, am a
: completely new to SQL Server. How would one go about setting up a log of
: the odbc counters?
: Thanks,
: Danny
: "Jim B" <jim.butts@gmail.com> wrote in message
: news:1140546860.629897.250100@g43g2000cwa.googlegroups.com...
: > You are probably hitting the number of ODBC connection limit (per
: > processor). This sometimes happens if you end up looping thru the
: > "adocon.open" section. You could check this by looking at the ODBC
: > perfmon counters. Try changing to a dsnless connection using OLEDB.
: >
:
:

Christopher
Tue Feb 21 23:11:34 CST 2006

Look at your ODBC setup and make sure that you are allowing for TCP/IP
connections.
--
Christopher A. Reed
"The oxen are slow, but the earth is patient."

"Dannyb" <dannyb@alianza.com> wrote in message
news:%23b1POLqNGHA.812@TK2MSFTNGP10.phx.gbl...
> Hello, I am running IIS 6.0 on a windows 2003 server. I have an asp page
> that accessed a SQL server 2000 running on windows 2003 through DSN.
> Every once in a while the webpage becomes inaccessable and gives the
> following message:
> Microsoft OLE DB Provider for ODBC Drivers error '80004005'
> [Microsoft][ODBC SQL Server Driver][DBNETLIB] General network error.
> Check your network documentation.
> /direct/dbConn.asp, line 34
>
> Line 34 of the asp file contains the line:
> adoCon.Open "dsn=DatabaseConnect;uid=login;pwd=test"
>
> The webpage doesn't just comeback after a few minutes but instead stays
> inaccessible until the SQL Server is restarted.
> The only way around this problem has been to restart the SQL server every
> 3 hours in order to decrease the webserver downtime.
> Please help,
> Danny
>

Dannyb
Wed Feb 22 11:20:17 CST 2006

Where group would you recommend I post this problem in? I posted it in the
sqlserver.odbc group but I don't think anyone ever looks at it.
"Ken Schaefer" <kenREMOVE@THISadOpenStatic.com> wrote in message
news:%23GvDwO2NGHA.344@TK2MSFTNGP11.phx.gbl...
> Sorry, but /don't/ think this is the issue. The issue here seems to be
> related to SQL Server and/or transient network problems. This correlates
> with the error message received, and also with the fact you need to
> restart
> SQL Server to get things working again.
>
> Cheers
> Ken
>
> "Dannyb" <dannyb@alianza.com> wrote in message
> news:ucktDwxNGHA.2604@TK2MSFTNGP09.phx.gbl...
> : Wow, sounds like I am talking to the right person. I however, am a
> : completely new to SQL Server. How would one go about setting up a log
> of
> : the odbc counters?
> : Thanks,
> : Danny
> : "Jim B" <jim.butts@gmail.com> wrote in message
> : news:1140546860.629897.250100@g43g2000cwa.googlegroups.com...
> : > You are probably hitting the number of ODBC connection limit (per
> : > processor). This sometimes happens if you end up looping thru the
> : > "adocon.open" section. You could check this by looking at the ODBC
> : > perfmon counters. Try changing to a dsnless connection using OLEDB.
> : >
> :
> :
>
>

Ken
Wed Feb 22 18:13:17 CST 2006

Firstly start by isolating the problem.

When the problem occurs, can you connect to SQL Server using anything else
(e.g.enterprise manager, from a remote computer?)

Is there anything being logged in the SQL Server's event logs?

Using Profiler on the SQL Server box, how many open connections etc do you
see?

Cheers
Ken

"Dannyb" <dannyb@alianza.com> wrote in message
news:uEkJFR9NGHA.3944@tk2msftngp13.phx.gbl...
: Where group would you recommend I post this problem in? I posted it in
the
: sqlserver.odbc group but I don't think anyone ever looks at it.
: "Ken Schaefer" <kenREMOVE@THISadOpenStatic.com> wrote in message
: news:%23GvDwO2NGHA.344@TK2MSFTNGP11.phx.gbl...
: > Sorry, but /don't/ think this is the issue. The issue here seems to be
: > related to SQL Server and/or transient network problems. This correlates
: > with the error message received, and also with the fact you need to
: > restart
: > SQL Server to get things working again.
: >
: > Cheers
: > Ken
: >
: > "Dannyb" <dannyb@alianza.com> wrote in message
: > news:ucktDwxNGHA.2604@TK2MSFTNGP09.phx.gbl...
: > : Wow, sounds like I am talking to the right person. I however, am a
: > : completely new to SQL Server. How would one go about setting up a log
: > of
: > : the odbc counters?
: > : Thanks,
: > : Danny
: > : "Jim B" <jim.butts@gmail.com> wrote in message
: > : news:1140546860.629897.250100@g43g2000cwa.googlegroups.com...
: > : > You are probably hitting the number of ODBC connection limit (per
: > : > processor). This sometimes happens if you end up looping thru the
: > : > "adocon.open" section. You could check this by looking at the ODBC
: > : > perfmon counters. Try changing to a dsnless connection using OLEDB.
: > : >
: > :
: > :
: >
: >
:
: