Help!!!Cannot Connect To Remote Sql Server By Named Pipe
May 6, 2007
Hi, all,
I installed sql server 2005 express on a server with window server 2003 SP1 and tried to connect it from a remote computer with vista installed.
I have already enabled named pipe and tcp/ip protocol for instance SQLEXPRESS on the server, and started sql server browser as well. Of course, I also enabled local and remote connection using tcp/ip and named pipe by sql server surface area configuration tool.
In this senario, I can connect to server locally or remotely by tcp/ip and connect to server locally by named pipe(c>sqlcmd -S \192.168.1.100pipeMSSQL$SQLEXPRESSsqlquery -U * -P *), but I can not connect to server remotely using same command line.
According to some article from MSDN, it might be caused by firewall, but I already disabled my firewall. Moreover, I used tools like makepipe.exe and readpipe.exe, they didn't work too. Why the 2 computers can't create connection using named pipe protocol.
We have 3x instances of SQL Server 2012 installed on a single remote server - there's the default MSSQLSERVER instance, then INSTANCE01 and INSTANCE02. I can remotely connect to the default MSSQLSERVER instance through SSMS, but I cannot connect to either of the additional named instances (INSTANCE01 or INSTANCE02).Â
For example, if I try to connect to "sql.domain.com", I can successfully access the default instance on the remote server. If I try to connect to "sql.domain.comINSTANCE01", I get an error stating
"A network-related or instance-specific error occurred while establishing a connection to SQL Server".
However - if I try to connect to "sql.domain.comINSTANCE01, 49301" (where 49301 is the TCP Port for the TCP/IP Protocol for this SQL Server instance), I am able to successfully connect.
This leads me to think that there's a communication issue with the SQL Server Browser service running on the remote SQL Server and my workstation.Â
The following items have been verified:
SQL Server Browser is running on the remote SQL ServerWindows Firewall has been disabled on the SQL ServerTCP Ports 1433, 1434, 1954, and 49301 have been opened up on the remote destination's firewallUDP Port 1434 has been opened up on the remote destination's firewall.
Linked server is created as (from SQL 2005 to SQL 2000)
EXEC sp_addlinkedserver @server = @SPKServerName,
@srvproduct = '',
@provider = 'SQLOLEDB',
@datasrc = @SPKdatasrc //np:remoteservername
exec sp_serveroption @server = @SPKServerName
, @optname = 'rpc'
, @optvalue = 'on'
exec sp_serveroption @server = @SPKServerName
, @optname = 'rpc out'
, @optvalue = 'on'
exec sp_serveroption @server = @SPKServerName
, @optname = 'data access'
, @optvalue = 'on'
when asp.net applicaiton hits the Stored Procedure, it uses Linked server to get data from remote server. It fails with exception message
OLE DB provider "SQLNCLI" for linked server "ServerName" returned message "Login timeout expired". OLE DB provider "SQLNCLI" for linked server "ServerName" returned message "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.". Msg 5, Level 16, State 1, Line 0 Named Pipes Provider: Could not open a connection to SQL Server [5].
I'm currently having an issue with a linked server. Here's the surrounding information:
A) I have a clustered SQL Server 2005 Instance (A) and a SQL Server 2000 instance (B). B) There is a linked server on A to B. When I set it up, I did run the fix to ensure A could talk to B (There was an issue with communication between 2005 and 2000 servers). It has been there since I installed A, and has worked fine.. Until last week. C) This linked server uses static credentials to connect to B. D) Named Pipes are enabled on both servers to listen to both connections on both A and B in cliconfg. So A has a named pipe listening for B, and B has a named pipe listening for A. E) A has a view that looks at a table on B - It's a table view, very simple, just pulls in all the data from the table on B.
So, I go to do a select statement from the view, connected as a user other then 'sa'. I then get the error:
Named Pipes Provider: Could not open a connection to SQL Server Linked Server Error Source: ncli Client (Paraphrasing, didn't copy that down, but it was the ODBC connector)
Well, that's odd. It's been working fine for months now..
I then go and connect as sa on A to query B. It works! Mind you, absolutely NO QUERY from A to B will run again until I run SOME kind of query has been run as sa on A.
Mind you, this is not a credential issue. Every user who connects to the linked server to B uses a stored credential that is DBO to the database on B. The same User Name and Password exists on both A and B.
Also of note, I check the activity monitor. There's a process that is "dormant" every time I run a query against the view. The details of this connection are:
sp_reset_connection;1
My question is, why is it resetting the connection on B when being queried from A? Why is it "all of a sudden" a problem? Are there any changes that coudl ahve been made that would cause this?
Any help with this confusing issue would be appreciated.
Hi All , I have been racking my head on this for the last two days and really it should be a no brainier. Anyways I can only assume that I€™m missing something here but...
In a nut shell I am attempting to connect to a new SQL Alias that i have created by simply adding the following in the client network utility
Current SQL server name DASQL
Default instance
Alias Name: TASQL
Server Name: DASQL
Pipe Name: \DASQLpipesqlquery
I can connect the new alias via the local (server consol) yet when i attempt to connect remotely it times out as if it can't find the server.
I downloaded MS Pet Shop 4.0 recently for best-practice training purposes. The installation went smoothly with a SQL Server 2005 backend. At first I had a problem authenticating the mspetshop4 user in the database, but that was solved by fixing some settings with the password policy. Now the mspetshop4 user is authenticated properly, but I came across this error instead:Server Error in '/Web' Application. A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) 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 connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)
Source Error:
Line 216: Line 217: if (conn.State != ConnectionState.Open) Line 218: conn.Open(); Line 219: Line 220: cmd.Connection = conn;
Source File: C:Program FilesMicrosoft.NET Pet Shop 4.0DBUtilitySQLHelper.cs Line: 218
Stack Trace:
[SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +117 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +346 System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error) +619 System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj) +224 System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected) +113 System.Data.SqlClient.TdsParserStateObject.ReadBuffer() +59 System.Data.SqlClient.TdsParserStateObject.ReadByte() +36 System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +181 System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK) +56 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +1083 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +272 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +688 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +82 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +558 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +126 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +651 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +160 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +122 System.Data.SqlClient.SqlConnection.Open() +229 PetShop.DBUtility.SqlHelper.PrepareCommand(SqlCommand cmd, SqlConnection conn, SqlTransaction trans, CommandType cmdType, String cmdText, SqlParameter[] cmdParms) in C:Program FilesMicrosoft.NET Pet Shop 4.0DBUtilitySQLHelper.cs:218 PetShop.DBUtility.SqlHelper.ExecuteReader(String connectionString, CommandType cmdType, String cmdText, SqlParameter[] commandParameters) in C:Program FilesMicrosoft.NET Pet Shop 4.0DBUtilitySQLHelper.cs:127 PetShop.SQLServerDAL.Category.GetCategories() in C:Program FilesMicrosoft.NET Pet Shop 4.0SQLServerCategory.cs:27 PetShop.BLL.Category.GetCategories() in C:Program FilesMicrosoft.NET Pet Shop 4.0BLLCategory.cs:20 PetShop.Web.NavigationControl.BindCategories() in c:Program FilesMicrosoft.NET Pet Shop 4.0WebControlsNavigationControl.ascx.cs:53 PetShop.Web.NavigationControl.Page_Load(Object sender, EventArgs e) in c:Program FilesMicrosoft.NET Pet Shop 4.0WebControlsNavigationControl.ascx.cs:27 System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +31 System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +68 System.Web.UI.Control.OnLoad(EventArgs e) +88 System.Web.UI.Control.LoadRecursive() +74 System.Web.UI.Control.LoadRecursive() +158 System.Web.UI.BasePartialCachingControl.LoadRecursive() +61 System.Web.UI.Control.LoadRecursive() +158 System.Web.UI.Control.LoadRecursive() +158 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3035
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42Now I'm clueless. What does No process at the other end of the pipe mean?
Why can I no longer backup a database to a named pipe in SQL Server 2005? Named pipes are much easier to work with than VDI (and VDI is covered in obscurities). I really want the ability to dump a database to a named pipe reimplementation if it€™s been removed. I hate to think of the cost of redesigning our backup applications. Can I force a PIPE dump device into the sysdevices table? Any suggestions? (and DO NOT tell me to use VDI, as it is absurdly cumbersome and loaded with unnecessary dependencies)
I'm writing a java application that queries sqlserver 2005 (and 2000). In case the sql browser service is stopped I need to use the named pipe property or the port property, right? But how could the program know at runtime what is the port and what is the pipe name? And how should a connection string to sqlserver 2005 (and 2000) that includes named pipe, look like?
Does anybody have a working Java code sample that connects to an SQLServer 2005 database on a remote host, via the default named pipe, from a client using the SQLServer 2005 JDBC driver? Could you post it, or a pointer to it?
I've gotten java.sql DriverManager.getConnection() to work fine with TCP/IP connections before. But I'm a newbie with named pipes, and unclear on how the connection string/properties are different. I've tried to piece it together from multiple docs and threads, but haven't found sample code that quite fits my situation. I think a simple working example would best clarify the syntax.
The server is not using SQL Express. Most SQLServer configuration options are defaults; the named pipes protocol is enabled.
I had to un-install and re-install SQL Server 2005 for a different problem which has been resolved.
But now when I try to make a connection to the database I get the following error:
"...No process is on the other end of the pipe"
I have verified that the server allows named pipeing which seems to be the common answer I found after searching. I have also verified that the account I use is setup and has all the proper permissions.
Can someone help me in resolving this issue noting what I have verified above???
I have windows 2003 (SP1) server with sql server 2000 (SP3) .
In the server network utility, I have enables only TCP/IP protocol and disabled the Named pipe protocol.
Now if I try to connect to the sql server from a remote machine, I get the message saying "unable to connect either server does not exist or ......".
I have configured the firewall to allow communication on TCP port 1433. It didn't help. I tried to disable the firewall completely, still it didn't work.
It works only if I enable Named pipe in the server's server network utility.
I try to connect from a pc to a SQL Server on another pc. Both pc’s are in a workgroup. I want to connect from a Windows Forms application to a named instance on the other computer. By now I have been able to connect from one pc to SQL Server on the other with tcp:smurfin, 52782.
I want to be able to use servernameinstancename (instead of portnumber) to make a connection in a Windows Forms application.
I’ve checked / tried te following:
•In the properties of the instance, tab Connections, the option Allow Remote Connections is enabled •In Configuration Manager: TCP is enabled •The service SQL Server Browser is started •On the tab IPAddresses, in the section IPAll, there is NO portnumber for TCP Port. And TCP Dynamic Ports has the nummer 52782 •I have created un inbound rule for port 52782 and also for 1434 (SQL Server Browser). And to be on the save side: a rule for 1433 as well. •Restarted the service
If I run the following code in SQL Server, that same port number (52782) is returned:
EXEC xp_ReadErrorLog 0, 1, N'Server is listening on', N'any', NULL, NULL, 'DESC' GO SELECT local_tcp_port FROM sys.dm_exec_connections WHERE session_id = @@SPID
I have two instances of SQL Server on the same PC:
Default instance: SQL Server 2000 Named instance with name €œMS2005€?: SQL Server 2005. Also I have another SQL Server 2005 on another PC.
I created a .NET 2.0 Compact Framework application that connects to the database and executes simple query. This application can connect to any instance of the SQL Server when it is executed on the PC (not on the server). But the problem is that when I try to execute the application from the windows CE 5.0 device, the application can only connect to the default instance (SQL 2000 and 2005) and can not connect to the named instance (Name: MS2005). Is it some kind of limitation of the SqlClient library for the compact framework?
My connection string (to a remote instance of SQL Server Exress 2005) is exactly the same when the web files are located on my local machine or my remote machine, and while it works fine when I use the local web files, I get the following error when I use the remote files:
"Named Pipes Provider: Could not open a connection to SQL Server [53]"
As you can see, since it works from the local version, I've setup SQL to accept remote connections via TCP/IP and Named Pipes. I'm using IIS7 on the local, and IIS6 on the remote, in case that makes a difference. I have other sites setup the same way, which work fine.
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: Named Pipes Provider,
Hi,I have SQL Server Express Edition. I tried working out some ASP.NET Labs in my local system. Here is the link of the Virtual Lab which I tried. http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032286906&EventCategory=3&culture=en-US&CountryCode=USI recieve this error in my local system. 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)I tried working out solutions from various websites. But the no solution is effective. Could anyone help me in solving this issue.
I am trying to setup a client alias to connect to a named instance on another server.
TITLE: Connect to Server ------------------------------ Cannot connect to fred. ------------------------------
ADDITIONAL INFORMATION:
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) (Microsoft SQL Server, Error: 53)
[URL]
The network path was not found
------------------------------ BUTTONS: OK ------------------------------
I have set up the alias on the server and as expected it works. On the client side I have used the SQL Server Client Network Utility to configure the client side alias but no luck
I am using TCP/IP with a specific port ..
By the way the SQL is SQL Server 2012 Ent and the O/S is Windows 2012 R2 minshell
Hi I always get good reply from u all, thank you, I have copied my asp.net website from one server to another. they administrator made necessary modification on IIS manager . and able to see the website on browser. but now i can't loging to system using old password. I tryed to create new password then also it gives error System.Data.SqlClient.SqlException: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) Here I have used asp.net login control and membership class. Do I need to make nay changes in code. I have already modified server name in connection string in web config file. any one can say what is the problem and how to solve this. thanks Pat
Hi , I am struck with one issue.Plz help me out if you have any solution for this one. Details Front End - Visual Studio 2005 Back End -SQL Server 2000 (Remote database) Error i am getting is {System.Data.SqlClient.SqlException: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup) at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at dbcAccess.clsSQL.GetConnect() in C:Documents and SettingskerlsgMy DocumentsVisual Studio 2005ProjectsdbcAccessdbcAccessclsSQL.cs:line 296}
{System.Data.SqlClient.SqlException: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
I’m going nuts and need some help with my ASP.NET 2.0 application which has trouble talking to a remote SQL Server 2000. First, before I describe my problem let me say that everything works perfectly on my XP development workstation when I point to the local SQL Server database. Screens load fine, saves and edits all work perfectly. Problem is when I connecting to SQL Server on a remote windows 2003 server I get Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. Now, I’ve researched this error and have successfully made the following changes to the remote windows 2003 server where the database resides:1) Added logins for “ASPNET”, “NT AUTHORITYNETWORK SERVICE”, and “IIS_WPG”. The reason I added NT AUTHORITY is because we plan on deploying this web site to the same windows 2003 server and I understand that IIS6 (on this server) has ASP.NET running as NT AUTHORITY acct. 2) For all the logins above I’ve added them as users to the database and given dbo role. I still get same login for user null error when attempting to connect from my XP workstation. Can anyone help?
I recently reinstalled SQL Server 2005 on a new computer, and now I can't connect to remote SQL servers for some reason. When trying to access the remote server with SQL Management Studio or DTS I get the following error: -----------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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476----------- I'm certain the servers I'm trying to connect to allow remote connections so the fault must be on my side. Does anyone have any idea what the cause and solution might be?
Hi Folks I have faced a problem during my application development... The application which is manipulating data in SQL sever 2005 which resides on server Named [Mserver1]... Now in the local netwrok there are 10 Client Pcs... My application will be running on all of them... What connection string will i use for that.. Client Pcs have not got SQL on them... I am using visual studio 2005, SQL server 2005.
Hi, I have Windows XP Pro OS with SP2 and SQL Server 2005 installed. I want to give Windows Authentication to my colleague sitting next to me, we are into same LAN. Is it possible to give access to my friend and if so can I create a seperate Security Group and add multiple users to them and give access.
I have created my sql database script using SQL data publishing wizard, now i want to execute the same on my shared hosting database. But i am not getting any option to connect to remote server in SSMSE.
I have developed web based application with back hand as SQL Server 2005, so now i want to execute my script file onto the server. so how i will connect with my server using SSMSE ?
My application is located under www.briskonsales.com/sales
I am unable to connect to a remote instance of SQL Server to which I have full permissions. Names Pipes are enabled and started. All services appear to be running. The server uses windows authentication and has the domain admin account referenced.
The follwoing is the response on attempting to connect:
An error has occurred while establishing an error to the server. "....this failure may be caused by the fact that under default settings of SQL Server does not allow remote connections. (provider: Named Pipes provider: error 40. could not open a connection to SQL Server IMS SQL Server error 53)"
I wnat to connect to remote sql server 2005, I do the following steps:
Enable remote connections on the instance of SQL Server that you want to connect to from a remote computer. Turn on the SQL Server Browser service. Configure the firewall to allow network traffic that is related to SQL Server and to the SQL Server Browser service. sp_addlogin 'Wind','ack@123','db'
but still can't login,tips as follwing:
Login failed for user 'Wind',The user is not associated with a trusted SQL Server connection. Error:18452
Why? Must use "SQL Server Authentication" connect?
I have 2 Window 2000 servers. A server is a Web server (IIS 5.0). B server is a MS SQL 2000 database server.
I use the following connection string to connect successfully the B DB server from the A server. .... cnstr = "Provider=SQLOLEDB;Persist Security Info=False;UID=xxxx;PWD=xxxx;Data Source=xxx.xxx.xxx.xxx;Initial Catalog=DDDDD;" Set conn = Server.CreateObject("ADODB.Connection") conn.Open cnstr ......
But, I change the connection string to the following (it just only be added "Network=DBMSSOCN;", it is connecting with TCP/IP). It is failed ! .... cnstr = "Provider=SQLOLEDB;Persist Security Info=False;UID=xxxx;PWD=xxxx;Data Source=xxx.xxx.xxx.xxx;Initial Catalog=DDDDD;Network=DBMSSOCN;" Set conn = Server.CreateObject("ADODB.Connection") conn.Open cnstr ......
The error message is : Microsoft OLE DB Provider for SQL Server error '80004005' [DBNETLIB][ConnectionOpen (Connect()).] General network error.Check your network document /TCPIP_Test.asp, line 14
Then, I use the same connection string (TCP/IP) to connect successfully the B DB server from an other C web server.
Other test on the A server : 1. ping -a <B server> : test OK ! 2. telnet <B server> 1433 : test OK ! 3. osql -U<xxxx> -S<B server> : test OK ! 4. run VB6 apps with the TCP connection string : test OK !
This is the error: "Unable to open database. Data source name not found and no default driver specified". But there's a catch! Read on...
Our application was written using MFC (ODBC CDatabase class) and the Open function takes a connection string like this:
"Driver={SQL Native Client};Server=%s\INSTANCE;Database=dbname;Uid=loginname;Pwd=password" The %s in the connection string is either set to "localhost" or in the case of a client/server setup, the user chooses a host from a list the first time they run the application, so it becomes "SOMECOMPUTERNAME".
Here's the catch: the application can connect to the remote server if SQL Server is installed on the client machine. When we install our application on a clean, freshly installed XP machine, we get the error.
However the ODBC Data Source Administration tool recognizes SQL Server and I can successfully create a DSN to our remote SQL Server using it.
What does installing SQL Server do to allow the connection string to work and what do I need to do to NOT install SQL Server on our client machines?
Hi,I have SQL Server Express Edition. I tried working out some ASP.NET Labs in my local system. Here is the link of the Virtual Lab which I tried. http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032286906&EventCategory=3&culture=en-US&CountryCode=USI recieve this error in my local system. 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)I tried working out solutions from various websites. But the no solution is effective. Could anyone help me in solving this issue.
