Named Pipes Provider: Could not open a connection to SQL Server [2]

Question

Hi
I'm a complete sql/asp.net newbie and want to try this tutorial:
http://beta.asp.net/GuidedTour/
First I installed:
Visual Web Developer 2005 Express Edition Beta 2
systemsettings\software shows the "sql server 2005 express edition ctp (sqlexpress)" installed
mmc\service shows me the SQL Server (SQLExpress) is running
Following the guided tour I use the commandline, type cmd, and type in the commandbox:
"C:\Program Files\Microsoft SQL Server\90\Tools\binn\SQLCMD90" -S "localhost\SqlExpress"
Instead of localhost I also tried computername.smallbusiness.local (thats my fully domain name).
However I always receive the error:
Named Pipes Provider: Could not open a connection to SQL Server [2]
Thank you very much for all your help

Answer 1

Typically I have found problems with connection strings as one of a few things:
1. Your instance is named different than the default.  I labeled mine BrettSQLServer instead of the regular instance.
2. Your default storage of the your database has a user the system does not like and won't give it access.
3. You have ports blocked that SQL Server is trying to access.
1. Your instance should show up under 'SQL Server Configuration Manager'.  Start>MS SQL Server 2008 > Configuration Tools> SQL Server Configuration Manager.  You should see a left view panel where you can click 'SQL Server Services'.  This
will show on the right all of your SQL services that are running.  The most important one is SQL Server({Your SQL Server Name}).  You will see column headers's displaying: "Name, State, Start Mode, Log on as,  ProcessID" by default.  If
you don't see a version of this you may have no installed SQL server properly and gotten SQL management studio but not the server.  If you have the server and it's off or not running that is another problem.  If your "LOG On AS" is a service account
is "NT ...." or something besides "Local System" that may be a problem.  Without getting into the symantecs of protection suffice to say you log in with less than system, yes you are more secure but some built in functions for connections may not work.
2. Going off of rights of your 'Log On As' I WOULD USE 'System' NOT "NT Authority....".  The reason is that you can access less things with 'NT Authority....' but yes you are more secure for that reason.  If you are just trying to connect at home
to test non secure things I don't see the harm.  If you are setting up a database for a multinational corporation than, Yes I would use a more secure account.  If you need to change it while still in SQL Server Confi Manager: Right Click> SQL
Server(Your Version) > On 'Log On' tab > Choose drop down for 'Built-in Account' select 'Local System'.  As extra steps make sure by some strange reason your database locales have this user by default(They should).  MS likes to install database
as default to: C:\Program Files\Microsoft SQL Server\MSSQL10.{instanceName}\MSSQL.  If you go to this location by going: right click>Properties>Security Tab .. and you fail to see your user that SQL server is defined as you may have lots of
issues.
3. Turn off Windows Firewall during SQL installation.  If you are scared of being attacked during this down window, disconnect your NIC and reconnect later.  I have not added a port manually in a while but it is simply easier to just
turn off your firewall during install.  Having your TCP/IP connection from SQL Server blocked is kind of bad if you need to connect to it that way later.
Problems most commonly encountered with SQL Server by users I have seen and I myself encountered a lot with full blown SQL Server Enterprise as well as Express versions of SQL:
Connection string DO not work for BIDS, ADO.net, Linq, etc...
Once you follow steps above just go {ComputerName}\{SQL Server Instance} as your connection name.   That mostly always works.  As a preliminary test you should install SQL Management Studio first before doing connection strings for a basic test
that it can access your server.  When you first boot it up and click 'New Database Engine Query' it will display Server Type: "Database Engine" and a blank field or autopopulated field for 'Servername'.  The {ComputerName}\{SQL Server Instance} almost
always works.  If it works and you can connect, you know that you have access, if you don't start there first before getting into connection strings through .NET languages.   I suggest just adding an easy alias, my local SQL box is simply called
'Brett'.  Go again back to SQL Server Configuration Manager.  On the left side click 'SQL Native Client ...' > 'Aliases' > New > type in whatever you want.  Go back to the left pane click on 'SQL Server Services' ensure the service
'SQL Server Browser' is running and set to run automatic.  Have fun accessing SQL Server with your alias.  
Help I can't get FileStream to work and I ran 'spconfigure' in SQL and it still doesn't work.
Kind of annoying that more sites don't list that it is entirely in the Configuration manager and has zilch to do with setting the option if the config has it off.  I am not a master of the sp_configure TSQL access method but I know during installs turning
it on fails to REALLY turn it on.  Once again go to SQL Config Manger > SQL Server Services > Right click your instance > Select FILESTREAM tab > enable both check boxes.  Restart SQL Server.  Install Adventureworks 2008 and whatever
else failed due to filestream access levels.
Medium to Advanced on some things, but always wanting to know more