Microsoft OLE DB Provider for SQL Server error '80004005' Every 48 hours

  • Windows Server 2003 SP2, SQL Server 2000 SP4 both on the same box

    SQL Windows Authentication only

    I keep getting the error message below, every 48 hours on all the web sites that connect to the SQL server for data. The only way to fix the issue is to restart the windows OS, which I do remotely. I have noticed a lot of failed attempts to logon using the "sa: account. I have switched everything to Windows Authentication and turned off mix mode. It is still happening.

    Microsoft OLE DB Provider for SQL Server error '80004005'

    [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

    /LM/W3SVC/844747025/Root/global.asa, line "XXX"

    Any ideas why this is occurring every 48 hours. This has been going on for about a month or so.

    Thanks to all who can help

  • Your application must be running Excel with SA permissions instead of the Asp.net runtime so you need to find the code running Excel and add Asp.net to the folder holding the Excel files. The link below will help you with IIS6 folder permission which will resolve your problem.

    http://support.microsoft.com/kb/812614

    Kind regards,
    Gift Peddie

  • Nope, no Excel running. These are ordinary ASP sites, (NOT ASP.NET). The content on particular pages are driven by data that comes from an SQL database associated with the site. Some of the sites have Intranets where users can login and then have access to applications that can update content on the site or communicate data to other intranet users.

    To better explain...I run a small web and multimedia development company we have a web server/SQL server on the same box. It used to host our 10-15 client's sites that we developed over the years. None of our clients have any access to there sites via FTP or RDC. They have access to update content only through the tools we built using ASP/VBscript to update content in the database.

    This situation, "[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied." came up out of nowhere a month or so ago. I am curious if it might have been a windows update that might have caused this issue?

  • You are in SP2 so that is not the issue so it must be related to connection and protocols. Here are two support articles for how to fix it.

    http://support.microsoft.com/default.aspx?kbid=315159

    http://support.microsoft.com/kb/328306/

    Kind regards,
    Gift Peddie

  • Try scheduling a agent job which capture ping server results to a table and see if it has any time out entries when the connection timeouts an application side.

    MJ

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply