locked
SQL Network Interfaces, error 26 RRS feed

  • Question

  • User1215529056 posted

    Last night I applied patches to my SQL 2012R2 server.

    Updates .Net Framework to 4.7 and a new version of Symantec Endpoint Protection 14

    Today I get SQL Network Interfaces, error 26 when trying to open a site on an XP box that was built in VS 2015

    When I run it on my workstation that is Windows 7 Pro. The site fails to open.

    I can run the site successfully when in VS 2015 on that same workstation.

    Any Suggestions

    Wednesday, May 2, 2018 8:34 PM

Answers

  • User1215529056 posted

    The fix, which I am not happy about seemed to be putting in the IP address in the code instead of the DNS.

    I up graded the SQL Server and this started. Also upgrade Symantec. on that server. I can ping it from my workstation and other workstation by IP or DNS.

    I have another application that this did not effect and it is in the SQL database all day long.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Thursday, May 3, 2018 6:50 PM

All replies

  • User1724605321 posted

    Hi andyr,

    I can run the site successfully when in VS 2015 on that same workstation.

    Do you mean one workstation after apply patches works but another workstation doesn't work ?  Or before apply patches it works ,but after updating the same workstation doesn't work ?

    Best Regards,

    Nan Yu

    Thursday, May 3, 2018 6:14 AM
  • User1120430333 posted

    If you applied patches to MS SQL server did the services become disabled? The error you talk about means that an instance of SQL Server cannot be found to be running.

    Thursday, May 3, 2018 1:05 PM
  • User753101303 posted

    Hi,

    Try perhaps https://blogs.msdn.microsoft.com/sql_protocols/2007/05/13/sql-network-interfaces-error-26-error-locating-serverinstance-specified/

    Could it be a firewall issue ? Or if the server restarted maybe something was previously started manually (such as the SQL Server browser service ?)

    Thursday, May 3, 2018 1:48 PM
  • User1215529056 posted

    The fix, which I am not happy about seemed to be putting in the IP address in the code instead of the DNS.

    I up graded the SQL Server and this started. Also upgrade Symantec. on that server. I can ping it from my workstation and other workstation by IP or DNS.

    I have another application that this did not effect and it is in the SQL database all day long.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Thursday, May 3, 2018 6:50 PM
  • User753101303 posted

    It seems a DNS name resolution issue. Try perhaps http://techgenix.com/using-nslookup-dns-server-diagnosis/ or see with your network administrator. At this time a Windows networking forum would be better.

    Wednesday, June 6, 2018 1:18 PM