Error: No process is on the other end of the pipe

I was minding my own business, working on an ASP.NET / Silverlight project in Visual Studio 2010, when I ran across this error:

The client was unable to establish a connection because of an error during connection initialization process before login. Possible causes include the following:  the client tried to connect to an unsupported version of SQL Server; the server was too busy to accept new connections; or there was a resource limitation (insufficient memory or maximum allowed connections) on the server. (provider: Named Pipes Provider, error: 0 – No process is on the other end of the pipe.)

Now, this is SQL Server Express, mind you, so there shouldn’t have been any fancy stuff I needed to do, like configure SQL Server, or restart services, or sacrifice virgins to Baal – any of that sort of thing.

And it was a simple issue – I checked out the .mdf file. You see, I use Visual SourceSafe for my local, personal projects. Yes, that’s right – VSS, baby. Now and forever.

So, getting a named pipe error when trying to connect to a SQL Server Express database in VS 2010 and have the project checked into VSS? Try checking out the DB file first.

  1. Leave a comment

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: