Look, I don’t like to mention this…but…this error can be caused because your SQL Server 2005 service is STOPPED. (Quickly pulls paper bag over head).
So have a look in SQL Server 2005 Configuration Manager and do the right thing before anyone notices.
But can I say this error message must be one of the more obtuse of its kind? Here it is in its full glory:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005 this failure can be caused by the fact that under the default settings SQL Server does not allow remote connections (provider: Shared Memory Provider, error 40: could not open a connection to SQL Server)
How about flamin’ well saying that the service is not running ???
For its coma-inducing combination of tendentiousness and irrelevance I vote THIS error message ‘Most Obtuse, 2009’ . Any seconders ?
More fixes for this problem are described at this excellent blog entry SQL SERVER – Fix : Error : 40 – could not open a connection to SQL Server by Pinal Dave.
Some More Obscure Error Messages
Here’s a great article called The 13 Other Greatest Error Messages Of All Time, with links to the original 13 Greatest and its comment list of 400 or so other wonderfully obscure and weird error messages.
Then try these from MYOB.
Tags: Error Messages