Dougie Brown (dougiebrown@xxxxxxxxxxxxxxxx) writes:
The Network Client Utility has been used to enable both TCP/IP and Named
Pipes in that order on all machines but still two use Named Pipes!
...
I've read that dbnetlib will change the protocol if the first one fails,
is there anyway to log these errors?
Well, what happen if you disable Named Pipes on the troublesome machines?
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Re: SQL 2000, Named Pipes and Windows 2003 Standard ...Named Pipes on new XP SP2 Pro machines. ... WinXP but not on new XP Pro machines.... controller to talk directly to the SQL server via Named Pipes. ... (microsoft.public.sqlserver.connect)
Re: msolap web access and the file sharing service ... When msolap.asp and Analysis Services are on different machines,... named pipes to communicate to the server, so whatever Windows needs in order ... for named pipes to function needs to be enabled. ... (microsoft.public.sqlserver.olap)
HELP - Connecting SQL Express Edition ... I have two machines and same problem. ... I installed SQL EE on XP HOME EDITION it is OK! ... I some how successed to connect with named pipes but TCP/IP is not working. ... For now anly named pipes working.... (microsoft.public.sqlserver.connect)
RE: [ODBC SQL Server Driver][Shared Memory]ConnectionWrite (send() ... the ODBC source using named pipe, but I don't know how to enable named pipes... If it is not working I am going to use ado to connect to sql server....Microsoft Online Community Support... (microsoft.public.sqlserver.connect)
