Recently, I setup a Windows 2003 Server with SQL Server 2005 Express Edition, along with ISA Server. When I tried to connect to the SQL Server from a remote machine, I was presented with the following error:
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: TCP Provider, error: 0 – A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)
Whew! That’s a pretty long error and really doesn’t tell you much, even with all that blabber.
First thing first, you should make sure that you have remote connections enabled in SQL Server so that remote connections are even allowed. If you’re good there, then keep on reading.
In order to connect properly to an SQL Server remotely, you have to take several different items into consideration.
1. ISA Server – If you have ISA server installed, you need to first make sure that you allow port 1434 – UDP and the MSSQL port number in ISA. If you don’t, the connections will be blocked.
2. MSSQL Port – This is the port number that is set in the properties of MSSQL. Whatever the port number is here, you have to add it to ISA server.
3. SQL Browser Service – You need to make sure that the SQL browser service is also running in order to remotely connect.
Basically, when you install the Express edition of SQL Server, it is installed as a named instance, rather than as a default instance.
Because it is a named instance, by default, it will use dynamic port assignment when it is started. So in essence, your SQL Server will be listening on some random port that was assigned to it when it started.
That’s where the SQL Browser service comes in. This is the service that tells the client, which is trying to connect to the server, what port to use. If the service is not up and running, you will not be able to connect to the named instance.
So you have two choices to solve this problem:
1. Enable the SQL Browser service so that clients can be told which port they need to connect to for that instance or…
2. If you set a port number for that instance, you need to provide that port number in the connection string.
If you are still having difficulties connecting or your setup is different, post a comment here and we’ll try to help! Enjoy!
Hi,
I deployed my asp.net application in one server and my application database is on some other server.
When I try to connect to the sql server datbase from my application then i got following Error Message.
"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)"
I googled on this Error.I checked the Configurations on sql server like
sql browser is running. allowing remote connections go checked and tcp/ip enabled.All Configurations are correct.
Still i got the same problem.
Please Some one Help to solve my problem.
I have a windows service written in c# that tries to connect to a remote SQL Server 2005 via ISA Proxy Server. The server on which windows service runs has ISA Proxy Client installed. The required firewall settings allow connection to the SQL Server on port 1433. We have tried creating a DSN and also tried using "telnet 1433" commands to verify connectivity. The network guys tell us that the application should be completely proxy server agnostic and that is what it is. However, they are telling that when the application tries to connect to the SQL Server, it is directly trying to go via the ISA Proxy Server rather than via the ISA Proxy Server Client (which encapsulate the network packets before forwarding to the ISA Proxy Server) which results in exactly the same error.
The windows service also consumes some WCF webservice services and normal SOAP web services within the domain.
The peculiar thing is that I created another light weight windows service which does just what the regular windows service does in terms of SQL connection and that seems to work without any issues. Both windows services run on the same server with the same credentials.
Hi,
I deployed my asp.net application in one server and my application database is on some other server.
When I try to connect to the sql server datbase from my application then i got following Error Message.
“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)”
I googled on this Error.I checked the Configurations on sql server like
sql browser is running. allowing remote connections go checked and tcp/ip enabled.All Configurations are correct.
Still i got the same problem.
Please Some one Help to solve my problem.
I am using Windows Vista OS. I have installed SQL Server 2008. I wanted to connect to my remote server using sql server management studio. I have VPN connection for connecting the remote server. I connected to VPN.
I Microsoft SQL Server Management studio when I enter 'myremoteservernameSQLExpress' I am getting the below error:
"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".
I have done all the below steps for solving the issue:
1) Enabled tcp/ip protocol, enabled local and remote connection and restarted the instance in sqlsever surface aera configuration settings.
2) Enable tcp/ip protocol in sqlserver configuration manager.
3) Restarted sqlserver browser,mssqlserver instance.
4) Created sqlbrowser.exe exception of the file in firewall.
5) created sqlserver.exe exception of the file in firewall.
6) Enabled Allow remote connections to this server in Microsoft SQL Server Management Studio server node properties connections.
Please help me to solve this issue.
Hi.
I am using windows 2003 professional operating system. I deployed my asp.net web application on it. It generated an error. I provided you a snapshot of it.
===============
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:
public virtual businesslogic.tlinksme.ShoppingCartClass.Cart SCart {
get {
return ((businesslogic.tlinksme.ShoppingCartClass.Cart)(this.GetPropertyValue("SCart")));
}
set {
===============
Actually, I am using Custom Profile for shopping cart as Binary.
I did not get where is the error. I googled many web sites, but I did not get the exact answer.
For your information, my SQL server 2005 has been configured correctly. SQL server 2005 names instance is running, and a web browser is also running. I have enabled TCP/IP as well as enabled remote connection.
One surprising thing is that when I deployed another server like XP, it is working well. No error at all, but when I deploy on windows 2003, an error is generated for network interface.
I need your help.
Bye.
Thank you.
hey guyz…
I have been using Ms-Access for the last one year….due to its size and server based need….I changed to sql server 2008…..and it works fine now. my question is how can I audit different user and their role on the database….like what if I wanna know which user is exporting data from another application like access(which I now used it for a front end)….any help ???
hi i am using Sql server 2005 while working with database connection this problem occurred:
A network-related or instance-specification error occurred while establishing a connection to sql Server.
This server was not found or was not accessible.Verify that the instance name is correct and sqlserver is configured to allow remote connections.(provider: SQL Network Interfaces,err:26-error locating Server/Instance Specified)
How can I fix it?
Dude, i set up the firewall inbound rules 1433 for tcp, then inbound rules 1434 udp. but what really was needed was to set up the connection string with the port
like this:
connectionString=”Data Source=database\CORP,1433….
with the port 1433 worked fine from my computer with the firewall enabled.