Is SQL Server 2005 still using Named Pipes ?

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.

Answer this question

Is SQL Server 2005 still using Named Pipes ?

foobarX

Does the client have Named Pipes enabled

To allow (remote) TCP/IP connections you need to use the "SQL Server Surface Area Configuration" to enabled remote connections first.
Talaro

Yes, they are still supported. They need to be enabled on server, and if you are using firewall make sure it is open.

This forum may provide better trouble shooting help:

http://forums.microsoft.com/MSDN/ShowForum.aspx ForumID=87&SiteID=1
YuvalO

>>which version(s) of SQL Server 2005 were you using Which version did you reinstall which version(s) of SQL Server 2005 were you using Which version did you reinstall

The latest download from msdn for SQL Server 2005 Enterprise

reinstalled same version
DavidAWinter

issue resolved, reinstalled SQL Server 2005 completely

thanks for your inputs.
japreja
Ok Matt, sorry, I'll just keep my post in that forum next time.
Dave DeJonge
Named Pipes does not work when configured as the only client connectivity option for ASP.NET running in default circumstances. Have a look at the following article:

BUG: Named pipes do not work when worker process runs under ASPNET account
http://support.microsoft.com/default.aspx scid=kb;en-us;Q315159
Vitoto
I'm having the same issue, and will post this in the suggested forum shortly - but wanted to ask dba123 a couple of questions first: which version(s) of SQL Server 2005 were you using Which version did you reinstall

Here's our scenario:
1. Installed SQL Server 2005 Developer Edition on a machine with WinXP SP2 and enabled remote connections over TCP/IP
2. Installed SQL Server 2005 Standard Edition on a machine with Win2003 SP1 (remote connections over TCP/IP enabled by default)
3. Attempted to 'Copy Database' from Developer Edition TO Standard Edition using 'Detach and Attach' method and recieved the error on the Win2003 machine: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server
4. Attempted to 'Copy Database' from Developer Edition TO Standard Edition using 'SQL Management Objects' method and recieved the error on the Win2003 machine: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server
5. Reinstalled Standard Edition on the Win2003 Server
6. Same error
Thanks in advance,

Steve
WilliamStacey
This is an SSIS forum and would not have people monitoring it that are best suited to answer this question. As Michael stated previously you might want to post in
http://forums.microsoft.com/MSDN/ShowForum.aspx ForumID=87&SiteID=1

Thanks,

Matt
abdullah
No, what I mean is, if I enabled it then disabled it again, why is my error talking about pipes at all. I want to see if that's the problem with all the errors I'm getting. Why should I be getting this error talking about pipes when I have definitely disabled named pipes in SQL 2005
trobin
I have already checked and configured that 1000 times. Named pipes is disabled in the places you talk about. That's why I am wondering why it's still talking about named pipes when it has been disabled in the config manager.
Is SQL Server 2005 still using Named Pipes ?

Answer this question