ODBC Drivers error '80004005' only on Hi

Results 1 to 2 of 2

Thread: ODBC Drivers error '80004005' only on Hi

  1. #1
    Join Date
    Dec 1969

    Default ODBC Drivers error '80004005' only on Hi

    Pleas Help :-) <BR>I get this error on my server!! <BR>Microsoft OLE DB Provider for ODBC Drivers error &#039;80004005&#039; <BR>[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied. <BR><BR>But its only happens when the server is on hi load..<BR>around 35 % CPU...<BR>the server is an win 2000 with sql 2000 conected to the web server win 2003 with two 1 gb card:s via a HP switch...<BR><BR>Regards<BR>Rickard<BR><BR>

  2. #2
    Join Date
    Dec 1969

    Default RE: ODBC Drivers error '80004005' only o

    Hello, We&#039;re also experiencing the same issue! Have you resolved this? Here&#039;s a summary of our current situation:<BR><BR><BR>Microsoft OLE DB Provider for SQL Server error &#039;80004005&#039; <BR><BR>[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.<BR><BR><BR>... the error pops up on any page in any spot on the page. If you refresh the page 10 times, 4 of 10 will come back with an error today.<BR><BR>Our environment:<BR>- 1 Dual Xeon 2.4 Windows 2003 Standard w/ SQL Server 2000 SP3<BR>- 1 Dual Xeon 2.4 Windows 2003 Web Edition IIS6 w/ 15 websites seperated into 3 app pools.<BR><BR>The 15 websites are very similar code, all classic ASP with OLE DB connection strings. They all get this error, and recycling the aplication pools does not help at all. We also rebooted both servers and still doesn&#039;t help.<BR><BR>Does anybody have any tools to monitor connections / connection pooling on our web server? And also helpful tools for this situation to monitor our SQL Server to see if maybe there are too many connetions over there as well? The randomness of this error occuring is amazingly difficult to troubleshoot.<BR><BR><BR>Here&#039;s our connection string btw:<BR><BR>"Provider=SQLOLEDB; Data Source=; Initial Catalog=mydatabase; User ID=myuser; Password=mypass;"<BR><BR>The connection is always opened at the beginning of a page, and closed at the end. And while the connection is open we may call 10 recordsets throughout the page, like this for example:<BR><BR>SQL = "SELECT * FROM Products"<BR>set RS_Products = Server.CreateObject("ADODB.Recordset")<BR>RS_Produ cts.Open SQL, Conn, adOpenForwardOnly, adLockReadOnly<BR><BR>And the error we get always happens on the recordset ".open" line.<BR><BR>Thank you to anyone that can assist.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts