NamedPipes error

  • Thread starter Thread starter Earl
  • Start date Start date
E

Earl

I have an app that connects fine to a SQL Server 2000 install using TCP/IP
only. When I tried to connect my app to the same database on a new SQL 2005
installation today on a client's laptop, I got a "Named Pipes provider"
error message. While I think I can resolve the SQL2005 setup on this
particular installation, what changes could I make to the connection string
to ensure I get thru to someone who has NamedPipes only enabled?
 
You can access from the network the computer where the SQL resides?
Connect using Windows Explorer to that machine and try again. This usually
does the trick.
 
Yes, this is a non-network issue. We installed the database and prototype on
a laptop. Getting the dreaded NamedPipes: 40 error. The strange thing is, we
can actually connect to the database and do a Select from within the app,
but Inserts and Updates fail. This appears to me to be a permissions issue,
but I've yet to find it.
 
Very strange, usually with pipes you are not able to access at all the
resource if not enough permissions.
If you run a SQL Server graphic tool on that machine, with same user and
password, you can do all the operations connect, insert, update etc?
Try also to use the mixed security mode, to diagnose the problem, (is not
recommended to use in the real world) to see if it works with the sa user.
 
Back
Top