Post reply

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

  • July 31, 2006 at 8:22 am

    #171689

    Hello everyone

    I will describe the environment and the problem to see if someone can help me.

    Client: Win XP sp2

    Server: Windows 2003 Server sp1 + SQL Server 2000 sp4

    I have an application developed in VB6 which executes lots of sql querys in a few seconds. This querys are very simple and they are executed properly until i dont know what but te aplication seems to be waiting for an answer and then gives the error:

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

    Number: -2147467259

    then it goes on with other executions and shows the error a few times more.

    This is the only costumer i have with this problem so i asume this is a problem of his net / os settings.

    Thank you for your answers.

    Santiago.

  • July 31, 2006 at 11:51 pm

    #652511

    I suspect that the customer is using hubs not switches to interconnect their network?

    So If one NIC card in the network decides to scream, it will bring the entire network to it's knees.

    You can adjust the *Timeout connection string settings for the ADODB.Connection object to overcome a slow or busy network.

    You should do some packet sniffing to prove the cause. But then this is really a network engineer's job...

    I would also investigate blocking, which is very hard to detect in a real time situation, unless you have the "steps to reproduce".

    Andy

  • August 16, 2006 at 7:50 am

    #655254

    I've found these on the web, think the solution might be here

     

  • September 26, 2006 at 9:50 pm

    #662626

    I recently migrated my web server from windows 2000 to Win2k3 and like the folks on that forum I am having a midstream error as follows:

    Microsoft OLE DB Provider for SQL Server error '80004005'

    [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
     
    The site works fine for 2 - 5 hours and then boom, this issue crops up.  I followed the advice listed on posts similar to those linked above and increased the socket pool to 60,000 and changed the Time Waiting registry to 15.  This appears to have lessened the frequency of the errors, but not eliminated them, and they still occur every 8 - 10 hours.
     
    We had also upgraded the NIC card to a gigabit card, but I changed that back to the old one.
     
    9 times out of 10 a web server reboot fixes the problem, but that 1 out of 10 times we have to reboot the database server and then the web server and it will fix it. 
     
    We never had any issues like these under the old operating system and IIS configuration.  Can anyone suggest anything?  I've tried everything that I can find to no avail and this is really getting tedious.
     
    Thanks!

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

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