Pipes -vs- Sockets

Nov 3, 1999

Assuming that IP/Sockets was added during the SQL installation.
Forgetting the known reasons for selecting them (Integrated security, etc.)


I've never fully understood why one connect method worked in some cases and the other did not. Can someone attempt to convey what the real differences are. What are required to use Pipes/Sockets. Do you need to be in same Workgroup/Domain, have a name server, etc.

I believe we all could benefit from a good explanation of this.

Thanks for any input,
Dano

View 2 Replies


ADVERTISEMENT

Dns/Wins & Tcp Sockets/named Pipes @ Sql 7

Sep 4, 2001

We would like to use dns entries (CNAME) to create transparency between server infrastructure and logical servernames. So we could physically move databases onto another server and changing the dns entry without reconfiguring all client applications.

Old situation:
- Financeapplication connects to SERVERA (wins) through a .ini file.

New situation:
- Financeapplication connects to finserver.mydomain.be (CNAME)
- finserver.mydomain.be points to servera.mydomain.be (A record) in dns
- servera.mydomain.be is refering to the ip address of SERVERA

We tried to connect and got a 'get_overlapped_results' (clientside) when using a dns name in combination with named pipes. At the server we are getting this error:

Error: 17832, Severity: 18, State: 8
2001-08-24 13:10:16.64 ods Connection opened but invalid login packet(s) sent. Connection closed.

Connecting to the wins name of the server does work! Connecting to the dns name also works when using tcp sockets instead of named pipes.

Though, on some client pc's this does work with named pipes too, but we couldn't find any regularity or logic when it works or when it doesn't (service packs, mdac versions, NT/95/98/2000, ... etc).

We also noticed that integrated security works with tcp sockets when using dns names, but it doesn't when using wins names.

Does anyone have a clue?

Kurt.

View 1 Replies View Related

Named Pipes Versus TCP/IP Sockets

Sep 25, 1998

We are having some problems using TCP/IP connection and was wondering what the benefits are to using this versus Named Pipes. The company that provides our software stated that this would improve performance but I do not see it and I am getting a lot of errors connecting. This also locks many of the users and I end up having to stop and start the database to clear the locks because there are so many. Would it be better to place the clients on Multi-protocol. It seems more powerful to use but I wanted to get some feedback from some people that may have dealt with this issue before.

Thanks,

View 1 Replies View Related

Problem With TCP/IP Sockets

Sep 21, 1998

A Win95 PC was having some TCP/IP problems that were corrected by the helpdesk. After that, SQL 6.5 client utilities were not working properly.
When trying to configure TCP/IP sockets in the Client Config, there is an error "Unable to locate the Net Library in Path". The necessary files appear to be in the correct path when I choose locate. I deinstalled and reinstalled the client utilities with no luck.

Also, when I enter the SQL Enterprise Manager, the error "Network Communications layer not loaded" appears.

Any ideas?

Thanks,
Christi Fischer
fischerc@mail1.monmouth.army.mil

View 1 Replies View Related

[TCP/IP Sockets] ConnectionRead (recv()) Error

Aug 9, 2001

Has anyone encountered this error and found a solution?
A batch process received this error for the first time last night.
We are running SQL 7 on an NT4 server, and the client machine is a Win2K box.
The process is a VB application, using ADO to connect to the database.
We are using TCP/IP protocol.
We were using the Named Pipes protocol in the past, but changed to TCP/IP a few weeks ago, because we kept getting a "ConnectionWrite(GetOverLappedResults)" error, and found information that stated the error was due to the Named Pipes protocol, and the solution was to switch to TCP/IP.
FYI, since switching protocols we have not seen the ConnectionWrite(GetOverLappedResults) error, and we used to get it everytime the process ran.

Any help or suggestions are appreciated.
If any further information about our systems or the process would help, let mw know and I will provide it.

Thanks.

View 2 Replies View Related

Fail To Connect Via Sockets To SQL Server

Apr 24, 2000

Background:

NT EE, MSCS, SQL 7.0 in Active/Passive environment. Add'l SQL installed on Passive server is hosting our Report database(any tips on Log Shipping?).
Anyway, I am unable to configure a client to connect to the secondary server via TCP/IP sockets.(Error 10061). I use the standard port 1433 and I've tried using both the name and the IP address for the server name.

What it looks like it's doing is only listening to port 1433 on the hearbeat nic. The reason I believe this is because when I ping the server name from that server, it returns a succesful ping, but using the heartbeat(seperate subnet)nics IP address.

Ping from a remote box works fine(DNS/Wins Resolution), and I connect fine with Named Pipes.

Both the primary and secondary server display the same results, the difference appears to be that only a virtual server in a clustered environment can have TCP/IP clients connect to it.

Can anyone verify this for me? Thanks a bunch...

MS says to go Active/Active and I am willing to do so, eventually.
Looking for a short term solution.

I'm not able to listen on a different port(again, appears only a Virtual server can).

Pete Karhatsu

View 3 Replies View Related

Error -[TCP/IP Sockets]ConnectionWrite (send())

Aug 21, 2007

Since we change the web server to window 2003, we occasionally receive the message
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite (send())

We use ASP and ODBC to access sql 2005. I have specified to use TCP/IP and port 1433 in ODBC.

Any idea to solve it?

Thank you in advance.

View 3 Replies View Related

How Can I Set SO_TIMEOUT On The Sockets Used By The JDBC 2005 Driver?

Jul 9, 2007

Hello,



One of our customers is experiencing a problem that makes me think there is a network problem, because we make a request and never return from the driver, but the transaction is still open on the server awaiting the next command (and holding locks blocking other processes). I see a number of other driver writers have described similar problems, and their "workaround" is to set SO_TIMEOUT on the sockets (setSoTimeout) they create which is a last defense so that the transaction won't block forever.



I do not see this in the API documentation- how can I set this? Many other drivers use a connection string parameter, do you offer the same?



Is there any logging I can enable that can show me for sure that the driver is waiting indefinately on socket.read (thats not terribly expensive)?



Thanks,



Steve

View 10 Replies View Related

ODBC SQL Server Driver TCP/IP Sockets SQL Server Does Not Exist Or Access Denied

Dec 3, 2004

I am running Windows 2003 Standard edition with IIS and SQL 2000 SP3a installed on it.

The web clients use ASP pages which use DSN to connect to SQL 2000 database. It has been working fine since last 1.5 years except 2 days ago when I faced this error suddenly on server:

In accessing any ASP page, it said:

[Microsoft][ODBC_SQL_Server_Driver][TCP/IP_Sockets_SQL_Server_does_not_exist_or_access_den ied.

On SQL Server error log, this was the entry at that time which I found:

SQLServer Error: 17, SQL Server does not exist or access denied. [SQLSTATE 08001]

The server (including SQL Server and agent service) were last stopped atleast a couple of days before, so it was not the problem about startup.

To troubleshoot, I restarted SQL Server and it worked for some time.

Then again on ASP pages, I found this error:

|80004005|[Microsoft][ODBC_SQL_Server_Driver][TCP/IP_Sockets]General_network_error._Check_your_network_document ation.

I checked the error logs of SQL server and didn't find anything.
Only entries were that the SQL is starting database, ports and IPs on which it is listening etc. The usual stuff. No errors in starting.

The SQL Agent log showed following errors:

2004-11-30 04:45:33 - ! [298] SQLServer Error: 2, ConnectionOpen (Connect()). [SQLSTATE 01000]
2004-11-30 04:45:33 - ! [382] Logon to server '(local)' failed (JobManager)
2004-11-30 04:45:36 - ! [298] SQLServer Error: 17, SQL Server does not exist or access denied. [SQLSTATE

I don't understand what was the problem. It first occured when nothing on server was changed, next it occured 30-32 hours later, and still now it hasn't happened again.

Does anyone know what can be wrong?

Thanks.

View 5 Replies View Related

Named Pipes Vs Tcp/ip

Oct 20, 1999

I am trying to run a sql script that was written by a third party to set up the tables and stored procedures of a 6.5 database. The script crashes
about half way through. The error looks like this...

The vendor said that I needed to change the client configuration to tcp/ip sockets instead of the named pipes that I was using. When I change
this setting I can no longer connect to the server through enterprise manager. The error message is...

I am not sure if the db-library is not set up correctly for the server or why it will not connect through the tcp/ip socket. I ran the ping command
from the command line and it returns a valid connection to the server. This doesn't make a lot of sense to me.

Does anyone have any experience with this problem or suggestions of something to try to fix this problem. Any ideas would be great. Thanks.

View 2 Replies View Related

Named Pipes Vs Tcp/ip

Oct 20, 1999

Sorry I forgot to attach the error messages.

This is the message when the script crashes...

DB-Library: Unexpected EOF from SQL Server. Connection broken.
Net-Library error 109: ConnectionCheckForData (PeekNamedPipe()).

DB-Library Process Dead - Connection Broken



This is the message when I try to connect to the server using tcp/ip sockets...

A connection could not be established to SERVERNAME - [DB-Library]Unable to connect SQL Server is unavailable or does not
exist. General network error.

View 1 Replies View Related

Named Pipes?

Aug 9, 2003

Hi Everybody,

Can anyone tell me what are named pipes? and what is a TCP/IP net library? Do these libraries work together or only one can be used at a time?

Thanx in advance.

Regards,

Samir.

View 1 Replies View Related

Named Pipes Vs. TCP/IP

Feb 11, 2004

Can anyone please tell me why i have one SQL 2000 server that is only accepting Named Pipes connections from clients? In the Server Network Configuration Utility both protocols are enabled, although Named Pipes in first and i cannot change the ordering.

TIA:confused:

View 6 Replies View Related

SQL Using Named Pipes Not TCP/IP

Apr 20, 2005

All - I have 2 SQL2K clusters, both have local applications and replication. The first cluster uses TCP/IP for all its connections when looking at SQL Management processes. The second is still using named pipes for all connections. How do I set or configure the second cluster to use TCP/IP on local connections and replication? Thanks.

View 4 Replies View Related

Named Pipes Vs. TCP/IP

May 23, 2001

In your experience and all things being equal, is connectivity using named pipes faster, slower, or the same as tcp/ip?

View 1 Replies View Related

Named Pipes Vs TCP

Dec 13, 2004

How would one go about adjusting the default connection to the SQL Server on the client side, using either Named Pipes or TCP as the default?

View 4 Replies View Related

Named Pipes Error

Apr 30, 2008

I'm working on an insert into a database and I barrowed this code stright from Microsoft, changing the info I need. I keep getting an 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)" This is the same connection string that I use for querying the database without a problem. Anyone have any ideas?
Jeff
SqlConnection con = new SqlConnection("Data Source=.SQLEXPRESS;AttachDbFilename=software.mdf;Integrated Security=True;User Instance=True;");SqlCommand cmd = new SqlCommand("INSERT INTO download_table (username, computer_name, computer type, install type, date, email, agree, title) VALUES (@username, @computer_name, @comptype, @installtype, @date, @email, @agree, @title)", con);cmd.Parameters.Add(new SqlParameter("@username", SqlDbType.VarChar, 50));cmd.Parameters["@username"].Value = username;cmd.Parameters.Add(new SqlParameter("@computer_name", SqlDbType.VarChar, 50));cmd.Parameters["@computer_name"].Value = computer_name;cmd.Parameters.Add(new SqlParameter("@comptype", SqlDbType.VarChar, 50));cmd.Parameters["@comptype"].Value = comptype;cmd.Parameters.Add(new SqlParameter("@installtype", SqlDbType.VarChar, 50));cmd.Parameters["@installtype"].Value = installtype;cmd.Parameters.Add(new SqlParameter("@date", SqlDbType.DateTime, 50));cmd.Parameters["@date"].Value = date;cmd.Parameters.Add(new SqlParameter("@email", SqlDbType.VarChar, 50));cmd.Parameters["@email"].Value = email;cmd.Parameters.Add(new SqlParameter("@agree", SqlDbType.VarChar, 50));cmd.Parameters["@agree"].Value = agree;cmd.Parameters.Add(new SqlParameter("@title", SqlDbType.VarChar, 50));cmd.Parameters["@title"].Value = title;cmd.Connection.Open(); <--- This is where I get the above errortry{cmd.ExecuteNonQuery();}catch (SqlException ex){}cmd.Connection.Close();

View 7 Replies View Related

Named Pipes...ASAP Please

May 21, 2001

Hi,

How do I find out on which path is the SQl server lisytening to on named pipes when I look at the registry?

Thanks,
Ganesh

View 1 Replies View Related

Named Pipes Error...

Jun 28, 2001

Can anybody help?
I have recently got any error -
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][Named Pipes]Connection Broken
/

Does anybody know how to resolve or point me in the right direction.....?

Thanks

View 4 Replies View Related

Named Pipes Under Alias

Feb 17, 2004

I have a SQLSERVER INSTANCE A, to which I want to connect from a Client as TEST, using the SQL Server alias functionality under the client network utility program. The alias is working fine with the TCPIP connection but it fails when I try to connect to the SQL Server using the named pipes. In my case I'm trying to connect to a named instance of SQL Server 2000 using the following pipe: \servernamepipemssql$instancenamesqlquery

Any help?

View 2 Replies View Related

Named Pipes Question

Aug 14, 2007

i have to admit I am not that familiar with named pipes, but i do have an issue with them that I would like to understand a bit better.

I installed the SQL 2005 express version on a machine and using a express manager i tried connecting to the instance i just installed. However i was getting an error message referencing the NAMED PIPES. after hours of trying to figure out what the problem was i found that using the SQL Server COnfiguration Manager, under the SQL Server 2005 Network Configuration there is a node called Protocols for SQLEXPRESS. there are four protocols, one of which is the NAMED PIPES. Under the properties for this protocol there is the PIPE NAME which is what i had to change to "\.pipesqlquery". the default was longer and if i remember it correctly it was something like "\.pipeMSSQLSERVEREXPRESSsqlquery".

Once i made that change i was able to connect. Can somebody please explain to me what I have done (i can't find the article that lead me to this) and if there is any way to make this change in some sort of a script or something.
reason being is that I have an VB app that deploys the SQL 2005 express version as well and i would like to eliminate this step from the user to configure before using the app.

many thanx

View 4 Replies View Related

Can Only Connect Using Named Pipes

Mar 14, 2008

We have migrated some users over to a new domain and when using SQL Management Studio, they can only connect using Named Pipes. Why?


Canada DBA

View 2 Replies View Related

Disabling Named Pipes

Jul 23, 2005

In the process of doing some routine monitoring/clean-up we'vediscovered that several (many?) users are apparently set to access ourSQL Server 2000 database instances via the Named Pipes protocol. Inreadings and recommendations we've decided that our WAN would be bestserved if we use the less "chatty" TCP/IP.As such we've also decided to try to enforce this decision to useTCP/IP exclusively using the domain login script used by all of ourend-users.Question: does anyone know what registry entries are created/used toindicate that TCP/IP is enabled and is the default protocol for SQLServer 2000? Our environment is: XP Pro SP2 and SQL Server 2000(typically SP3).TIAGlenn - newbie DBA

View 5 Replies View Related

Named Pipes Error

Dec 4, 2007



HI,

I am getting an error message when I have installed SQL server 2005 and trying to access it through my component. The error message is €œAn error occurred while establishing a connection to the server. When connecting to the SQL Server 2005, this failure may be caused by the fact that under the default settings SQL server does not allow remote connections (Named pipes provider)?€?

I would be obliged if anyone can help me in this regard.

Regards,
Nitin Bhansali

View 1 Replies View Related

Named Pipes Provider

Apr 4, 2007

Hi!

I tryed to make an silent mode install for SQL express edition, for example:



start/ wait setup.exe /qn ADDLOCAL=ALL SECURITYMODE=SQL SAPWD=***** SQLBROWSERAUTOSTART=1 DISABLENETWORKPROTOCOLS=0
When i run it from a .bat file it's ok but i'm using this command in a .ini file in some apllication.
It doesn't install all the SQL, i mean in services it appears only SQL Server VSS Writer.
I also get the error Named Pipes Provider. The application that i want to install gets installed but can't connect to server.
I really need some help.

View 1 Replies View Related

SQL Says Named Pipes Not Enabled But It IS

Apr 4, 2007

Hi,



I'm using bcp and sqlcmd against SQL 2005 engine. They both work fine for long periods of time, but every few days they stop working with an error something like this:



A connection could not be establed - actively refused - this might be because remote connections are not allowed or the named pipes protocol is not enabled.



The thing is, remote connections ARE allowed, and named pipes ARE enabled. I have to recycle the SQL serverice to make it start working again.



Here are the commands that stop working.



sqlcmd -Ulowcostbuy -Plcb01 -S127.0.0.1 -id:homeWeBuysql runcate_bid_request.sql


bcp low_cost_buy..bid_request in d:homeWeBuyuploadunzipped
equest.dat -S127.0.0.1 -Ulowcostbuy -Plcb01 -fd:homeWeBuyformatsid_request_in.fmt -ed:homeWeBuylogid_request_in.err



Another note: sql is listening on port 1737, not the standard 1433 (or whatever it is).



Can anyone please help!? This is a very high profile application; having it die every few days is NOT an option!!

View 2 Replies View Related

SQL Connection - Named Pipes Error

Dec 27, 2006

Hi all,
I've got a little problem.
I'm working on a ASP.NET project. The applications has 4-layers. When I look in the Data Access Layer and test the typed dataset, then the "Preview Data" works fine. I see the right records from SQL Server 2005.
But when I run the app (default.aspx) in debug-mode, then the system gives 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)"
Please help.....

View 9 Replies View Related

Need To Configure SQL Server For TCP/IP & Named Pipes

Feb 23, 1999

I have a question. When my SQL server was originally configured, it was only setup to use named pipes. Now I am needing to setup a P&M server (through Site Server 3.0), but I must have my SQL server to accept tcp/ip network connections. I don't know how to enable named pipes & tcp/ip. Any help would be greatly appreciated.

Steve Robitzsch

View 2 Replies View Related

Connectivity Issues (TCP/IP, Named Pipes Etc)

May 15, 2006

Hi all,

little connectivity problem, I hope this hasn't been asked before, I've tried searching and haven't found much sign of it.

We have an app which runs on sales reps laptops using MSDE (or in this particular case SQL 7 Desktop Edition) and uses merge replication to send up orders, pull down products etc. All worked fine untill we set it up for one particular customer who wanted to use their existing SQL 7 install with it and a VPN connection for replication.

The problem is that with the VPN connected nothing (the app, the merge dll or even enterprise manager) could connect to the local instance (but can see the main server across the VPN). It seems to be some kind of funny routing issue whereby the VPN software sends local traffic off across the VPN which has no idea what to do with it. Using the Client Network Utility I've been able to setup an alias for the local machine forcing it to use named pipes, which worked brilliantly allowing access when connected to the VPN and allowing replication to work. Unfortunatly with this enabled the problem now occurs when the laptop is disconnected, nothing can connect to the local instance.

I'm kind of a newbie wrt to managing SQL server, can anyone suggest anything on how I should be setting this up ?

Thanks in advance,
Steve.

View 1 Replies View Related

Doubt Reagrding Pipes In Sql Server2005

Sep 30, 2006

hi,
how can i create a pipe in sql server 2005 in which i want to place a couple of instructions and execute paralelly. i have little knowledge with pipes in dbms. pls tell me where i have to create a pipe and how to create and how to execute it?
thanx in advance,
rammohan

View 1 Replies View Related

Is It Possible To Turn Off Named Pipes In 2005??

Aug 9, 2007

For SRS??? If so, what's the work around?

View 12 Replies View Related

Named Pipes Disabled In SQL 2005

Jun 14, 2007

I see Named Pipes disabled by default in SQL 2005. Is this for any specific reasons?

View 1 Replies View Related

Is SQL Server 2005 Still Using Named Pipes ?

Dec 21, 2005

I keep getting errors.  It all started when I enabled named pipes on my SQL Server 2005 server.  Ever since then I've had connection problems up the butt.

Most recently I got this error so does this mean that SQL Server is still trying to use named pipes even if I only have TCP/IP enabled in SQL Server Configuration Manager?

Error:

TITLE: Connect to Server
------------------------------

Cannot connect to BG-SQL2005.

------------------------------
ADDITIONAL INFORMATION:

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: 2)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------


 

I get this when I try to connect to my DB period and I know the users are setup correctly, even tried both Windows Authentification and SQL authentification, no luck.  It was working happily for a few days it seemed before I enabled named pipes in the SQL Server Configuration Manager.

View 11 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved