Remote database Connection Error!

use sql2k5 surface area configuration tool to enable 'remote connections'.
-oj
"Sujata P" <SujataP@.discussions.microsoft.com> wrote in message
news:94D32EEB-9098-4A51-B55D-95BD84B5AA96@.microsoft.com...
> Hi,
> My Application which is written in VB.Net uses database connection to my
> Local Instance of SQL Server Express version.
> My connection string is " Data
> Source=SM5\SQLEXPRESS;AttachDbFilename=C
:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data\MgmtSystem.mdf;Initial
> Catalog=MgmtSystem;Persist
> Security Info=True;User ID=sa;Password=belmont". When I run my application
> from the same machine where SQL Server instance is installed, it works
> fine.
> But now I am intending to use it as Client-Server type as database on
> Server
> and application running from another machine. To test this I have
> deployed
> my application on another machine. When I run it I get following error,
> "An
> error has occured while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default setting SQL Server does not allow remote
> connections.(provider: SQL Network Interface, error: 26 - Error Locating
> Server/Instance specified)(Microsoft SQL Server Error:-1).
> To Fix this I did try enabling all protocols(Shared Memory, TCP/IP, Named
> Pipe). Then I even started SQL Browser service to enable the instance to
> be
> browsed by client. Then Checked if Hide Instance property. Still no Luck.
> I am really going crazy. This is really important for me since we are
> migrating from Access to SQL Server Express. Since in Access my
> application
> can have client server
> Architecture. Same thing I need to have in SQL Express.
> Any help is really appreciated.
> Thanks,
> SujataHi,
My Application which is written in VB.Net uses database connection to my
Local Instance of SQL Server Express version.
My connection string is " Data
Source=SM5\SQLEXPRESS;AttachDbFilename=C
:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Data\MgmtSystem.mdf;Initial Catalog=MgmtSystem;Persist
Security Info=True;User ID=sa;Password=belmont". When I run my application
from the same machine where SQL Server instance is installed, it works fine.
But now I am intending to use it as Client-Server type as database on Server
and application running from another machine. To test this I have deployed
my application on another machine. When I run it I get following error, "An
error has occured while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default setting SQL Server does not allow remote
connections.(provider: SQL Network Interface, error: 26 - Error Locating
Server/Instance specified)(Microsoft SQL Server Error:-1).
To Fix this I did try enabling all protocols(Shared Memory, TCP/IP, Named
Pipe). Then I even started SQL Browser service to enable the instance to be
browsed by client. Then Checked if Hide Instance property. Still no Luck.
I am really going crazy. This is really important for me since we are
migrating from Access to SQL Server Express. Since in Access my application
can have client server
Architecture. Same thing I need to have in SQL Express.
Any help is really appreciated.
Thanks,
Sujata|||use sql2k5 surface area configuration tool to enable 'remote connections'.
-oj
"Sujata P" <SujataP@.discussions.microsoft.com> wrote in message
news:94D32EEB-9098-4A51-B55D-95BD84B5AA96@.microsoft.com...
> Hi,
> My Application which is written in VB.Net uses database connection to my
> Local Instance of SQL Server Express version.
> My connection string is " Data
> Source=SM5\SQLEXPRESS;AttachDbFilename=C
:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data\MgmtSystem.mdf;Initial
> Catalog=MgmtSystem;Persist
> Security Info=True;User ID=sa;Password=belmont". When I run my application
> from the same machine where SQL Server instance is installed, it works
> fine.
> But now I am intending to use it as Client-Server type as database on
> Server
> and application running from another machine. To test this I have
> deployed
> my application on another machine. When I run it I get following error,
> "An
> error has occured while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default setting SQL Server does not allow remote
> connections.(provider: SQL Network Interface, error: 26 - Error Locating
> Server/Instance specified)(Microsoft SQL Server Error:-1).
> To Fix this I did try enabling all protocols(Shared Memory, TCP/IP, Named
> Pipe). Then I even started SQL Browser service to enable the instance to
> be
> browsed by client. Then Checked if Hide Instance property. Still no Luck.
> I am really going crazy. This is really important for me since we are
> migrating from Access to SQL Server Express. Since in Access my
> application
> can have client server
> Architecture. Same thing I need to have in SQL Express.
> Any help is really appreciated.
> Thanks,
> Sujata|||Thanks oj...but I found answer...Actually I did everything last time except
creating exceptions in Windows Firewall for instance of my SQL Server to
unblock the connection.
For anyone who is facing similar problem, Follow
http://support.microsoft.com/?id=914277..it is very useful for creating
remote connection.
"oj" wrote:

> use sql2k5 surface area configuration tool to enable 'remote connections'.
> --
> -oj
>
> "Sujata P" <SujataP@.discussions.microsoft.com> wrote in message
> news:94D32EEB-9098-4A51-B55D-95BD84B5AA96@.microsoft.com...
>
>|||Thanks oj...but I found answer...Actually I did everything last time except
creating exceptions in Windows Firewall for instance of my SQL Server to
unblock the connection.
For anyone who is facing similar problem, Follow
http://support.microsoft.com/?id=914277..it is very useful for creating
remote connection.
"oj" wrote:

> use sql2k5 surface area configuration tool to enable 'remote connections'.
> --
> -oj
>
> "Sujata P" <SujataP@.discussions.microsoft.com> wrote in message
> news:94D32EEB-9098-4A51-B55D-95BD84B5AA96@.microsoft.com...
>
>

Remote Connection problems, I've read many a thread on this and nothing has worked!

Hi, I am trying to enable remote access on a SQL Server 2005 standard edition instance. I have enabled it in the properties using the Management studio and have enabled it under Sql Server Surface Area Configuration under "Database engine".

But it didn't work. I know for a fact that my connection string is correct (I tested it on the actual machine)

So I checked everything again and I noticed in the Sql Server Surface Area under "Analysis Services" there is another "remote connection" checkbox to be enabled, however it won't let me enable it there because it says the "Sql Browser" is not started. I checked and the Sql Browser is started.

I'm thinking maybe the problem there is that I have an instance of SQL 2000 running and perhaps it is the sql browser for that (I can remotely connect ot my SQL 2000 instance).

I checked under Computer management -> services and their is no SQL Browser for the instance of SQL 2005. Not even a thing to enable. Just the Default instance SQL Browser, which is for my SQL 2000 instance. Am I missing something here?

Also there is no SQL Browser to enable in the management or Surface Area Configuration programs.

I have also tried to connect using the default port number (1433) and the IP (to bypass the need for the SQL Browser). It apparently finds my Server 2000 instance because it doesn't accept my user name and password and connot find the specific database (note: I verified the username and pswd are correct by testing the values on the SQL machine). How do I find what port number a specific instance of SQL Server is running on?

Hi,

the fact that you are using the default instance of SQL Server 2000 on your computer and that you can connect to the SQL Server 2k with the default settings (1433) indicates that SQL Server 2l5 is installed on another port than 1433, because ports can′t be shared. So try to see on which port you installed SQL Server 2k and on therefore on which port it is listening. Then specify the port within your connection string with the following syntax:

MachineName\instanceName,Portnumber

HTH; Jens Suessmeyer.

http://www.sqlserver2005.de
|||

I've tried figuring out what port the SQL 2005 is running on by running a port scan, but nothing really jumped out at me other than the 1433, which the SQL 2000 is running on.

What is a good way to find out what port the SQL 2005 is running on?

|||

Hi,

you can have a look at:

http://support.microsoft.com/default.aspx?scid=kb;en-us;823938

The port which SQL Server is listening to can be retrieved via looking in the eventlog or using the statement xp_readerrorlog which shows up something like "SQL Server listening on xxx.xxx.xxx.xxx:PortNumber"

HTH, Jens Suessmeyer.

http//www.sqlserver2005.de

Remote connection problems

I have a Windows 2003 server running SQL Server 2005. I can connect locally via TCP/IP and I've followed all the recommended steps to enable TCP/IP and remote connections.

However, I cannot connect remotely from my desktop machine (different LAN) using the SQL Management Studio, not will the same connection string work on a webserver that's on a different machine.

My connection string is:

Dim objConn, objRS, strConn, strSQL, Email_Number, Template
strConn = "Driver={SQL Server};Server=88.208.229.121;Database=test;Uid=XXX;Pwd=YYY;"
Set objConn = Server.CreateObject("ADODB.Connection")
objConn.Open strConn

The error that I'm getting on the client with management studio is that the remote database is not available and most probably because TCP/IP was not enabled!

The error that I'm getting through classic ASP on the remote web is:

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

Keep in mind I can use the exact same connection string and ASP and connect on the local machine, no problems.

Any help in this matter will be greatly appreciated.

Thanks
Riaan
London

Is there a firewall (esp. Windows firewall) between your computer and the server?

Have you enabled remote connections (using the Surface Configuration tool)?

Have you enabled TCP/IP?

Check these resources:

Configuration -Configure SQL Server 2005 to allow remote connections
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277

Configuration -Connect to SQL Express from "downlevel clients"
http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx

|||Hi

There is no firewall on the server, and from this location I connect through a broadband router that has the standard type of protection.

Yes, remote connections and TCP/IP are enabled.

I actually followed the steps from the first article.

Riaan|||I've done every step in the mentioned articles as above and neither of my two web servers at my ISP are running Windows Firewall. They are both at the same ISP and as I said, with the connection string I use I can browse the DB from classic ASP on the server that runs SQL, but not from another server that just runs IIS.

Is there anywhere else I should look?

Riaan
London|||

I noticed that your server bridges two networks.

It is possible that the problem lies there due to the added complexity involved in dealing with two networks simultaneously.

It will have two ip addresses, one for network 1 and another for network 2. You cannot connect to the network 1 ip from network 2. From your local machine you can "see" both networks and both network cards, so it will be able to connect to either ip address. Only remotely does it matter which identifier you use for your server (assuming that the configuration of your server is absolutely perfect) because again the server bridges two networks. So have you tried the other ip address to make sure you aren't using network 1's ip address to try to access the server from network 2?

Additionally, you will have to make sure that you have enabled it for both network interfaces -- this requirement is there to allow differentiation between trusted and untrusted networks but of course adds to the complexity of configuring the system to service two different networks.

I hope this helps,

John Gordon (MSFT)

Remote connection of SQL Express

Good day! I'm trying to make remote connections to SQL Express and it seems that it is not working.

Below are the steps that I did

- TCP/IP enable in the "Protocols for SQLExpress" node

- Since I'm not going to use SQL browser, I clear out the value for "TCP Dynamic Ports" and instead create my own TCP Port number

- I add my windows authentication to the dbase that I want to try to connect remotely

- Add the sqlsrver.exe to the exceptions of the firewall but even I turned-off the firewall already it still not connecting.

My error message is

"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) "

Is there any step that fail to apply?

Thanks in advance.

It already worked. I just included the port number to my connection. (Bummer! How come I forgot to include it... :))