HELP: can't stop using Named Pipes!

[Matt C.]

I have deployed a test application (VS 2005) to several workstations.
They need to make a connection to our SQL Server 2000 server. Most work
fine. On one workstation, we keep getting the 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)"

I made a new .exe, incorporating the line ";Network Library=DBMSSOCN"
into the connection string. Same error. (Can post stack trace if it
helps.)

This workstation does connect successfully to the same server with a
different VS 2003 .NET application.

We tried reinstalling MDAC 2.8 SP1, in hopes that it would clear up the
library confusion. Did not work, same error.

Has anyone seen this before? Anyone have any suggestions? Ideas?

Matt

 

[Matt C.]

<snip story of apparently-forced named pipes>

Pretty sure I've got it. The plan was to add a shortcut from the app
directory to the desktop--on this workstation, a copy of the .exe got
copied to the desktop instead. There was no app.config on the desktop,
thus no server, and making changes to the .exe was completely beside the
point.

If I see this error again, I will make sure the app is actually hooked up
to the config file.

Matt