Okay. This post isn’t about configuring SQL to allow remote connections, but wait, I still may be able to help you out.
"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The 
server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)"
I love this exception. It summarized the issue and leads you down a path to solving the problem. I do wish the bit about allowing remote connections was left out of the message though. I can’t think of a time when having remote connections disabled caused me grief. Heck, I can’t ever remember how to enable remote connections unless I Google for the answer.
Anyway, 9 out of 10 times, SQL Server simply isn’t running. That’s why the exception occurs. The next time this exception pops up, open up the services console and make sure SQL Server is started. And if that’s not the problem, only then start digging into the other possible reasons for the failure.
Hmm it appears like your website ate my first comment (it was super long) so I guess I’ll just sum it up what I wrote and say, I’m thoroughly enjoying your blog. I as well am an aspiring blog writer but I’m still new to the whole thing. Do you have any recommendations for first-time blog writers? I’d really appreciate it.
How to make a spoiler button in blogger blog posts ?
Excellent post. I used to be checking constantly this blog and I am inspired! Very useful information specially the final phase
I handle such information much. I used to be seeking this certain information for a very lengthy time. Thank you and best of luck.
Heya! I’m at work browsing your blog from my new apple iphone! Just wanted to say I love reading through your blog and look forward to all your posts! Carry on the outstanding work!