Post reply

Specified SQL server not found

  • April 7, 2010 at 2:06 pm

    #233488

    All:

    We have VB.net application that connects to the SQL server 2005 DB. Occasionally we get the following error:

    "System.Runtime.InteropServices.COMException (0x80004005): [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL server not found."

    My research so far:

    1. I did not find any event log entries that flagged any errors.

    2. Thinking that it was network card issue, I checked the local area connection settings and made sure the option " to turn off this device to save power" unchecked.

    3. The system DSN which the application uses is set to use "dynamically determine ports". Not sure if this is an issue.

    So much information on the above issue, but could not find a clear answer. The key is it happens occasionally and NOT sure how to go about fixing it. Please share your ideas.

  • April 7, 2010 at 2:31 pm

    #1147770

    This is something that can happen on busy networks from time to time. It could be related to packet loss and the client thinking the server is not present, when it is really more like a network outage. However, the network could be up the entire time.

    I would check with the network team and see about doing a packet capture or hooking up a sniffer and determine if you can find an instance of it happening.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • April 9, 2010 at 8:28 am

    #1149155

    Thanks Jason.

    I will check with the network folks. But before going to them, is there a way from the application perspective that I can prove to see if there is an issue with the network. I would like to make sure everything is covered from the application end. What can I check/do to make sure if it is indeed an issue with the network.

    I am surprised to see that it is a frequent issue with the Win-sql server environments, but there is no clear guidelines/how-to to resolve the issue.

    Any help is appreciated.

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

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