Unanswered: Named Pipes Provider: Could not open a connection to SQL Server
 => [Microsoft][SQL Server Native Client 10.0]Named Pipes Provider: Could not open a connection to SQL Server .
[message] => [Microsoft][SQL Server Native Client 10.0]Named Pipes Provider: Could not open a connection to SQL Server .
I see this in a wireshark trace when I try to hit our sql server from one of our pages. This is when trying to log into the site. I tried to enable named pipes and that did not help. I also tried repairing the installation of sql and that did not help. Also, I was able to start the SQL Browser in Windows services on that machine. But, when viewing the SQL Configuration, the SQL Browser was displayed as stopped. There was no instance name under the SQL connections. So, I tried to give the SQL Browser an object but I was not able to do so. So, there was still no instance name for the SQL Browser. Any ideas?
I found the order. I am using SQL 2008. So, I found the client order under SQL Native Client 10.0 configuration. Named pipes is actually disabled. It is also disabled on the server. But, it was lower in the order anyways.
Hmm...Error 53 is can not find network path. Is it possible there is an application that has a bad config that is looking for a non-existent machine? It would fit, in that the tcp/ip library would fail. Then the request would pass down to named pipes, which would also fail.
That definitely could be the case. Part of the problem is that I came into this with the machine already set up. So, the web files were already installed onto the machine and the SQL server was already installed onto the machine. I just reverted to the snapshot in a program we are using for that. So, basically, I did not set the machine up. Which in turn means that your question is very valid and very possible. That is actually why I ran the network trace to begin with. Unfortunately, I do not know where to dig into the code to see where it was pointing to. I was hoping for any config file, but I only saw one and there was nothing relating to this in this file.
But, this is still good information go know. At least knowing what you said about error 53 points me in a possible direction.