SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified

原文链接：https://blogs.msdn.microsoft.com/sql_protocols/2007/05/13/sql-network-interfaces-error-26-error-locating-serverinstance-specified/

Users often see this error message when connection to a SQL Server and don't know where to start to solve the problem. In most forums, people says this is because remote connection is not enabled on the server. This is not exactly correct. Actually, this error message give customers very specific information and the solution is quite simple.

First of all, you get this error message only if you are trying to connect to a SQL Server named instance. For default instance, you never see this. Why? Because even if we failed at this stage (i.e. error locating server/instance specified), we will continue to try connect using default values, e.g defaul TCP port 1433, default pipe name for Named Pipes. You may see other error message due to failure later, but not this error message.

Every time client makes a connection to SQL Server named instance, we will send a SSRP UDP packet to the server machine UDP port 1434. We need this step to know configuration information of the SQL instance, e.g., protocols enabled, TCP port, pipe name etc. Without these information, client does know how to connect the server and it fails with this specified error message.

In a word, the reason that we get this error message is the client stack could not receive SSRP response UDP packet from SQL Browser. It's easy to isolate the issue. Here are the steps:
1) Make sure your server name is correct, e.g., no typo on the name.
2) Make sure your instance name is correct and there is actually such an instance on your target machine. [Update: Some application converts \ to . If you are not sure about your application, please try both ServerInstance and Server\Instance in your connection string]
3) Make sure the server machine is reachable, e.g, DNS can be resolve correctly, you are able to ping the server (not always true).
4) Make sure SQL Browser service is running on the server.
5) If firewall is enabled on the server, you need to put sqlbrowser.exe and/or UDP port 1434 into exception.

Once you are done the steps, you should not see this error message anymore. You may still fail to connect your SQL server, but error message should be different and you have a different issue now. [Update: If it still fails, you may replace serverinstance with tcp:serverinstance and/or np:serverinstance and see if it succeeds with either TCP or NP protocol. That way, you can isolate the issue a little bit. ]

There is one corner case where you may still fail after you checked step 1)-4). It happens when a) your server is a named instance on cluster or on a multi-homed machine, and b) your client is a Vista machine with Firewall on. I have explained the details at: Unable to connect to a SQL Server named instance on a cluster

[Update May 2009] My collegue found a good tool online which could be very helpful for users to isolate issues related to this error message. You can download PortQry from http://support.microsoft.com/kb/832919, run "portqry.exe -n yourservername -p UDP -e 1434". If this command returns information and it contains your target instance, then you can rule out possiblity 4) and 5) above, meaning you do have a SQL Browser running and your firewall does not block SQL Browser UDP packet. In this case, you can check other issue, e.g. wrong connection string.

As a final note, the error message for the same issue when you use SNAC is:
[SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].

If you still see this error, please post questions at MSDN SQL Server Data Access Forum:
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=87&SiteID=1
Please mention you already read this post and confirm steps you have taken and the results of each step.(e.g. serverinstance,etc)

SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified相关推荐

provider: SQL Network Interfaces, error: 26 - 定位指定的服务器/实例时出错
1.错误描述 ===================================无法连接到 SKY-20160824VTF\SQLEXPRESS.========================= ...
provider: SQL Network Interfaces , error: 26 - Error Locating Server / Instance
在 ASP.NET 中使用了角色管理机制(System.Web.Security.Roles )连接数据库时出现了如下错误: 在与 SQL Server 建立连接时出现与网络相关的或特定于实例的错误. ...
provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified
https://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error ...
provider：SQL Network Interfaces，error：26 - 定位指定的服务器/实例时出错--错误原因及解决办法
问题截图: 错误错误原因一未启动SQL服务错误原因二数据库和VS自带的LocalDB有冲突: 导致远程过程调用失败:(需要卸载VS中的LocalDB) 方法解决办法一启动SQL Serve ...
SQL Network Interfaces error: 26
解决办法:单击windows操作系统"开始"菜单,单击"运行"并输入services.msc 或者进入任务管理器中找到"服务(S)"点击进入 ...
SQL Server 2008 R2:error 26 开启远程连接详解
远程连接sql server 2008 数据库,出现下面的错误: <--在与 SQL Server 建立连接时出现与网络相关的或特定于实例的错误. 未找到或无法访问服务器.请验证实例名称 ...
SQL Server provider: SQL 网络接口, error: 26 - 定位指定的服务器/实例时出错
在与 SQL Server 建立连接时出现与网络相关的或特定于实例的错误.未找到或无法访问服务器.请验证实例名称是否正确并且 SQL Server 已配置为允许远程连接. (provider: SQL ...
Oracle Caused by: java.sql.SQLException: sql injection violation, syntax error: syntax error, expect
参考:https://blog.csdn.net/qq_36326332/article/details/102938147 https://blog.csdn.net/fly_captain/art ...
毕业设计Spring boot问题记录（后端三)：java.sql.SQLSyntaxErrorException: You have an error in your SQL syntax；
原创博文,欢迎转载,转载时请务必附上博文链接,感谢您的尊重报错情况 intell IDEA调试台报错 Caused by: java.sql.SQLSyntaxErrorException: You ...

SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified

SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified相关推荐

最新文章

热门文章