Ошибка sql server interfaces error 26 - ErrorsMaster.ru - большая энциклопедия ошибок и их решений

For me the issue was that the DNS record was wrong…

The following, which proved very helpful, is largely taken from this blog post.

This error message is actually pretty specific and the solution quite simple.

You get this error message only if you are trying to connect to a SQL Server named instance. For a default instance, you never see this 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 default TCP port 1433, default pipe name for Named Pipes.

Every time a 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 this information the client does not know how to connect and it fails with this 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. In order to isolate the exact issue follow these steps:

Make sure your server name is correct, e.g., no typo on the name.
Make sure your instance name is correct and there is actually such an instance on your target machine. (Be aware that some applications convert to ).
Make sure the server machine is reachable, e.g, DNS can be resolve correctly, you are able to ping the server (not always true).
Make sure the SQL Browser service is running on the server.
If the firewall is enabled on the server, you need to put sqlbrowser.exe and/or UDP port 1434 into exception.

There is one corner case where you may still fail after you checked steps 1 to 4. It also may happen when:

your server is a named instance on cluster or on a multi-homed machine
your client is a Vista machine with Firewall on.

A tool which could prove useful (it did for me) is PortQry. 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 possible issues such as an incorrect 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].

Microsoft recently released a guided walk through that can serve as a one stop shop to troubleshoot a majority of connectivity issues to SQL Server: Solving Connectivity errors to SQL Server

Источник

First published on MSDN on May 13, 2007

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 ServerInstance 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)

Xinwei Hong, SQL Server Protocols

Disclaimer: This posting is provided «AS IS» with no warranties, and confers no rights

Источник

Methods to Resolve SQL Server Error 26

Users often see “SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified” error message while connecting to SQL Server. This error 26 SQL server is quite common nowadays as a lot of users are complaining about it.

SQL Server Error 26 occurs when users trying to connect to a SQL Server named instance. The reason of the SQL Server Error 26 is the client stack could not receive SSRP response UPD packet from SQL Browser. Now, there a few ways to solve SQL network interfaces error 26 in a smart way. Stay tuned to know the best way.

Table of Content

Quick Steps Guide

Windows Firewall Method

Other Causes of Error 26

Automated Solution

FAQs

Tip: Fix SQL Server Management Studio Error 40

SQL Error 26 Quick Solution in 5 Steps

Downlaod & Launch tool in your PC

Click on Open to Add database files

Select Quick or Advance Scan mode

Select Settings & Destination Location

Click on Export button to get your results

You have to create an incoming rule that allows traffic from all promising IP addresses that are configured for the failover cluster instance and from all possible IP addresses of the remote server. For this, just follow the below steps. We’re sure that this way users can easily get rid of this SQL network interfaces error 26 for sure.

- Open Adminstrative Tools, from Control Panel to begin solving error 26 SQL server
- In Adminstrative Tools, click on Windows Firewall with Advanced Security
- Under Windows Firewall with Advanced Security on Local Computer column, click on the Inbound Rule and then select New Rule from the right pane

- From New Inbound Rule Wizard window, select Custom and then click on the Next button

- Under Does this rule apply to all programs or a specific program? select All programs then click on Next button

- Form Protocol type list, select Any and then click on Next button

- Under Which remote OP addresses does this rule apply to? select These IP addresses and then click on Add button

- In IP Address dialog box, under This IP address or subnet type the IP address and then click on Ok button

- Under What action should be taken when a connection matches the specified conditions? select Allow the connection and then click on Next button

Click on the Next button to complete the New Outbound Rule Wizard steps

Other Possible Causes of SQL Server Error 26 with Solution

SQL Server does not allow remote connections

To resolve the SQL Server Error 26 open SQL Server Management Studio, Right click on the database and select properties
On Security page, select SQL Server and Windows Authentication mode and click on Ok button
Restart SQL Server

If you are still facing the Error 26, then there could be a same name conflict between two systems. Check whether the computer name, system name is same if yes, then try to system using its IP address. In addition this error 26 occurs with several issues that are mentioned below:

SQL network interfaces, error: 26 – error locating server/instance specified
provider: SQL network interfaces, error: 26 – error locating server/instance specified
a network related or instance specific error in SQL server error 26

Experts’ Recommended Solution to Counter Errors Causes Due to Corruption

Now when there is some sort of data corruption issues present in the server, the SQL database might react differently than what it should usually do. Therefore, experts often suggest users to get the automated repair & recovery tool.

Downlaod the tool & then follow easy steps to repair damaged data & solve SQL network interfaces error 26 with ease. In addition, if you want to know how to make SQL server faster then this tool can remove corruption as well. Ultimately resulting in a faster server.

Download Now Purchase Now

Step-1. Launch the Tool in your system & then Click the Open button.

Step-2. Select the Quick or Advanced Scan Mode as per your need.

Step-3. Set the SQL Server database details to continue further.

Step-4. Finally, Click on the Export button to finish the task.

Frequently Asked Questions

Q-1. What is connection error 26 in SQL Express?

A: It is crucial for users to ensure that the name of their server is correct & no typo on the name is present. Always make sure that your SQL browser service is running on the server in case you are trying to connect SQL instance on another server. Your machine should be reachable.

Q-2. How do I fix error code 26?

A: The device drivers of your system are closely connected to the error 26. Removing all external devices can be a solution too here.

Q-3. What is SQL Server error 26 client unable to establish connection because an error was encountered during handshakes before login?

A: The most common reason for this is when a client connects to a unsupported version of SQL Server. Here the the error occurs because the server is too busy to accept the new connections. In some cases, resource limitation is also an issue where maximum allowed connected are pre defined.

Q-4. How do I fix SQL query error?

A: There are 4 steps to fix SQL query error as mentioned below:

Navigate to the failing line in SQL query.
Check failing SQL syntax in SQL query.
Check query logic in joins, subqueries, or CTEs.
Go to troubleshooting error messages to finish.

Q-5. How to restart SQL Server?

A: Go to SQL Server Configuration Manager >> Select SQL Server Services, Right Click a named instance or SQL Server> Select from Start, Stop, Pause, Resume & Restart options.

Q-6. How do I allow remote access to SQL Server database?

A: 5 Steps to allow remote access to SQL Server database:

Start SSMS (SQL Server Management Studio)
Go to Object Explorer & Right Click on Server
Select Properties & then Click Connections
Enable Allow Remote Connections to this Server
Click on Ok to save & Finish the task.

Источник

Remove From My Forums

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

Question

I used profile for shopping cart

Collapse

<system.web>
<anonymousIdentification enabled="true"/>
 <customErrors mode="Off"></customErrors>
 <profile enabled="true">
  <properties>
   <add name="SCart" serializeAs="Binary" type="Tandis.Cart" allowAnonymous="true"/>
  </properties>
 </profile>
</system.web>

Server Error in ‘/’ Application.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
(provider: SQL Network Interfaces, error: 26 — Error Locating Server/Instance Specified)

Description: An unhandled exception occurred during the execution of the current web request.
Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found
or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 — Error Locating Server/Instance Specified)

Source Error:





  


                       
  




Line 19:   public virtual Tandis.Cart SCart {
Line 20:     get {
Line 21:       return ((Tandis.Cart)(this.GetPropertyValue("SCart")));
Line 22:     }
Line 23:     set {

Source File: c:windowsMicrosoft.NETFrameworkv2.0.50727Temporary ASP.NET Filesroot2faf057937b1b4f4App_Code.1mhfv5r1.3.cs
Line: 21

Stack Trace:


[SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)]
  System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +4849719
  System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +194
  System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject) +4863021
  System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) +90
  System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) +376
  System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +221
  System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +189
  System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +4864151
  System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +31
  System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +433
  System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66
  System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +499
  System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +65
  System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +117
  System.Data.SqlClient.SqlConnection.Open() +122
  System.Web.DataAccess.SqlConnectionHolder.Open(HttpContext context, Boolean revertImpersonate) +87
  System.Web.DataAccess.SqlConnectionHelper.GetConnection(String connectionString, Boolean revertImpersonation) +221
  System.Web.Profile.SqlProfileProvider.GetPropertyValuesFromDatabase(String userName, SettingsPropertyValueCollection svc) +772
  System.Web.Profile.SqlProfileProvider.GetPropertyValues(SettingsContext sc, SettingsPropertyCollection properties) +433
  System.Configuration.SettingsBase.GetPropertiesFromProvider(SettingsProvider provider) +258
  System.Configuration.SettingsBase.GetPropertyValueByName(String propertyName) +132
  System.Configuration.SettingsBase.get_Item(String propertyName) +102
  System.Web.Profile.ProfileBase.GetInternal(String propertyName) +36
  System.Web.Profile.ProfileBase.get_Item(String propertyName) +68
  System.Web.Profile.ProfileBase.GetPropertyValue(String propertyName) +7
  ProfileCommon.get_SCart() in c:windowsMicrosoft.NETFrameworkv2.0.50727Temporary ASP.NET Filesroot2faf057937b1b4f4App_Code.1mhfv5r1.3.cs:21
  Showbook.Button2_click(Object sender, EventArgs e) in c:inetpubvhoststandisbooks.irhttpdocsShowbook.aspx.cs:22
  System.Web.UI.WebControls.ImageButton.OnClick(ImageClickEventArgs e) +108
  System.Web.UI.WebControls.ImageButton.RaisePostBackEvent(String eventArgument) +118
  System.Web.UI.WebControls.ImageButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +10
  System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +13
  System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +36
  System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1565

Version Information: Microsoft .NET Framework Version:2.0.50727.4206; ASP.NET Version:2.0.50727.4209

it works locally on IIS but on the host it gives this error!
what should I do ? (my host is plesk 9.5 )

Answers

Hi Nima,

Thank you for your post.

The reasons for throwing this issue could be wrong server name, disabled remote connection

and firewall blocking.

Could you please follow the steps below to solve this issue?

·         Check the server on which SQL Server is running can be accessible. You can use ping command to test that. For instance, ping <computer_name> or ping <IP_address>.
The ping command may be block by the firewall, make sure ICMP is enabled in the firewall. More info, check:

http://technet.microsoft.com/en-us/library/cc739791%28v=ws.10%29.aspx#BKMK_4.

·         Choose appropriate protocol

·         Configure Windows firewall accordingly based on what protocol you have chosen to use. For detailed information about how to configure Windows Firewall to allow SQL Server,
please check http://msdn.microsoft.com/en-us/library/cc646023.aspx.

·         Enable SQL Server Browser Services

You need to enable SQL Server Browser Services if the following are both true:

1.       SQL Server is not listening on default 1433 port or not use default pipe name
\.pipesqlquery;

2.       The corresponding TCP port or pipe name is not specified in the connection string (such as Srv1SQL2008, 1500).

If you have enabled SQL Server Browser Services, you still need to open UDP 1434 port which is used by Browser Services in the Windows firewall.

Best Regards,
Peja Tao

Please remember to click «Mark as Answer» on the post that helps you, and to click «Unmark as Answer» if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
- Proposed as answer by
  
  Friday, March 18, 2011 6:36 AM
- Marked as answer by
  Alex Feng (SQL)
  Friday, March 25, 2011 4:19 AM

Источник

SQL Server Error 26 and SQL Server Error 40 appear when you try to connect to SQL Server. We will troubleshoot and try to fix them in the same article as both are related to connection issue. We recommend to use the below solutions for the both errors and to try to localize the problem.

The error Messages:

(provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified)”

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified)

“ Named Pipes Provider Error: 40 – Could not open a connection to SQL Server“.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that the SQL Server is configured to allow remote connections. (provided: Named Pipes Provider, error: 40- Could not open a connection to the SQL Server) (Microsoft SQL Server, Error: 2).

sql server error 26

SQL Server Error 26 and SQL Server Error 40

What is SQL Server Error 26?

You will get this error message while trying to connect to a SQL Server named instance and not when you use default instance. The client stack could not receive SSRP response UDP packet from SQL Browser.

How to fix Error 26 on SQL Server?

Recheck the server name for any error and fix it
Check the instance name for any error
Check if SQL Server browser is running
Control if this instance exist on server
Ping the server and check if DNS can be resolved correctly

What is SQL Server Error 40?

This error appears mostly when SQL Server does not allow remote connections, Firewall Settings or TCP/IP is not enabled. We will explain below all those in order to troubleshoot easy.

Read also other SQL Server Helping Posts:

How to fix SQL Server Error 229
Fix SQL Server Error 233
SQL Server Error 17002

How to fix error 40 on SQL Server?

Check SQL Server is running
Make sure that Allow Remote Connections is enabled on sql server properties
Check if TCP/IP is enabled
Configure to allow SQL Server in Firewall Settings
Check for working fine SQL Server Browser
Make sure that you can ping the SQL Server

Below we will explain the above steps in long way for better understanding and easy fix of SQL error 26 and sql error 40.

1. Check if SQL Services are running

Hint! If you are running SQL Server by using an instance name and you are not using a specific TCP/IP port number in your connection string, you must enable the SQL Server Browser service to allow for remote connections.

How to check if SQL Server Service is running?

Go to SQL Server Configuration Manager > SQL Server Services
Find the service SQL Server (MSSQLSERVER) if default or the name of your instance
Check if is running – should be running state with a green indication

Using Windows Command Prompt

sc query mssqlserver

For named instance name use below by by replacing instancename with the actual SQL Server instance name.

sc query mssql$instancename

How to check if SQL Server Browser is running?

Navigate to SQL Server Configuration Manager > SQL Server Services
Find the SQL Server Browser Service
Check if it is configured to start automatically and is started – should be with a green indication

Using Windows Command Prompt

sc query sqlbrowser

Check if SQL Server Service

2. Try to Flush DNS

How to flush DNS?

Click Start Button
Type CMD and press enter
Type this into the black window that appears: ipconfig /flushdns and press enter.

Fluish DNS

3. Make sure that allow Remote Connection is enabled

Check if remote connections is allowed for applications/client. This option need to be allowed to establish connections and perform operations on the server. Often this is the reason of SQL Server Error 26 and SQL Server Error 40.

How to check if the remote connection is enabled?

Open ‘SQL Server Management Studio’
Right click on database name and select ‘Properties’
In ‘Properties’ window, select ‘Security’, enable `SQL Server and Windows Authentication mode` and click `OK`.
Now restart the SQL server.

Allow Remote Connections

4. Check Firewall

Check the firewall status for any troubles:

Open ‘Control Panel’ and after that ‘Windows Firewall’.
Select ‘Change Settings’ In ‘Windows Firewall’,
Add an exception for port ‘1434’ and name it ‘SQL Server’
Enable by clicking on the checkbox

5. Connection String

This solution is on cases when you are using connection string and are you writing it wrongly. For example connection string used by .NET framework:

Server=serverAddress;Database=dbName;User Id=username;

Password=password;

Check for each parameter passed in the connection string for any typographical errors.
Control the validity of the username/password.
Confirm if the given database exists.

6. TCPIP Protocol

This solutions can work when you have mix of default and named instance or named instances only.

How to Enable TCP/IP port?

Open SQL Server Configuration Manager
Click on SQL Server Network Configuration and click on Protocols for Name
Right-click on TCP/IP
Click Enable
Restart your SQL Server instance

Enable TCP-Ip port

If you want to use a static port for your instance (instead of dynamic that changes after every restart) you can change it here.

Open Properties for TCP/IP protocol
Go to IP Addresses tab
Scroll down to IPAll section
Remove 0 value from TCP Dynamic Ports
Specify your port in TCP Port

You can use this port to connect to your instance by providing <servername>,<port> or <IP>,<port> as Server Name (yes, there is a comma, not a colon).

TCP-Ip static port

Conclusion:

We have explained some solutions to fix SQL Server Error 26 and SQL Server Error 40 and hope that you find the fix on those solutions. The both errors are included on the same article because they have almost the same troubleshoot. If you have any other solution worked for you comment below and we will try to include it on our article.

Источник

Methods to Resolve SQL Server Error 26

SQL Error 26 Quick Solution in 5 Steps

Other Possible Causes of SQL Server Error 26 with Solution

Experts’ Recommended Solution to Counter Errors Causes Due to Corruption

Frequently Asked Questions

<img itemprop="url image" decoding="async" src="https://i1.social.s-msft.com/globalresources/Images/trans.gif?cver=0001" alt=" locked" /> provider: SQL Network Interfaces, error: 26 — Error Locating Server/Instance Specified

Question

Server Error in ‘/’ Application.

Answers

SQL Server Error 26 and SQL Server Error 40

1. Check if SQL Services are running

2. Try to Flush DNS

3. Make sure that allow Remote Connection is enabled

4. Check Firewall

5. Connection String

6. TCPIP Protocol

Conclusion:

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