can't connect to SQLEXPRESS locally

I have SQLEXPRESS installed on a Windows 2003 Server. The SQL Tools show that TCP and Named Pipes are Enabled. I can't connect using either the command line or the Mgmt Studio with either of these protocols.

Following is excerpt from program I'm trying to install:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

And this from the command line

C:\Documents and Settings\edulog>sqlcmd -E -S localhost
HResult 0x274D, Level 16, State 1
TCP Provider: No connection could be made because the target machine actively re
fused it.

Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establi
shing a connection to the server. When connecting to SQL Server 2005, this failu
re may be caused by the fact that under the default settings SQL Server does not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.

Thanks,

That's expected. Enable shared memory and you'll be good to go.

Paul

|||The MS documentation ( in the SQL Server Express Readme) says shared memory is enabled by default. I am trying to connect locally, and have named pipes, and tcp enabled as well as shared memory. All 3 methods fail.

Wendell

cant connect to Sql server 2000 sp3a in windows 2003 server

There is a way to find out - I think you should find out if the clients are
using "Named Pipes" or TCP/IP for connectivity.
Bring up the ODBC connection, then on the second page you should see a
button "Client connectivity". Go into this and make the bullet TCP/IP.
Please let me know if this fixed your problem.
=-Chris
On the clients that cannot connect, click the box "Client configuration"
"Rick" <ricardo.blanco@.indap.com.mx> wrote in message
news:ur4WMjStEHA.2688@.TK2MSFTNGP14.phx.gbl...
> hi guys im having troubles to connecto to sql server, my clients are win
xp
> and win 2000 pro, before i had the sql server 2000 on a windows 2000
server
> and all worked fine, but two days ago i changed to windows server 2003
> standard and the problems began...
> when i try to connect to sql by odbc or by another way its the screen that
> appears, the extrange is that in downstair there are 4 pcs and that 4 can
> connect to sql, (all winXP Sp1 in spanish), upstairs there are 3 winXp
> spanish, 2 winxp english(1 with SP2 the other Sp1) and 1 win2000 Sp4 pro
> english and just 1 XP in spanish can connect the other 2 not, i thought it
> was a problem with the server but now i connect a new laptop with winXP
> spanish SP2 and it works fine... so i dont know what to do, all pcs have
> mdac 2.8
> now i thought its problem with clients but i cant find difference between
> pcs except for the language
> what can be'
> i tried to connect by IP, i checked the port and nothing works =(
>
>Chris thanks a lot, but ive found other way to solve it, i know maybe its
not the more correct but i reinstalled the Sql server because i found at
microsofts web a tool to check the ports, its name is PortQuery, with it
you can check for Sql server if it is running on a server, or network
connectivity and other things, i saw that the server doesnt aswer to the
tool, the ports 1433 and 1434 not respond, so i decided to reinstal Sql
server, and it solved the problem =)
the tools url is http://support.microsoft.com/kb/310513/EN-US/
Rick =)
"Christopher Conner" <someone@.someplace.com> wrote in message
news:%23u554sTtEHA.3872@.TK2MSFTNGP15.phx.gbl...
> There is a way to find out - I think you should find out if the clients
> are
> using "Named Pipes" or TCP/IP for connectivity.
> Bring up the ODBC connection, then on the second page you should see a
> button "Client connectivity". Go into this and make the bullet TCP/IP.
> Please let me know if this fixed your problem.
> =-Chris
>
> On the clients that cannot connect, click the box "Client configuration"
> "Rick" <ricardo.blanco@.indap.com.mx> wrote in message
> news:ur4WMjStEHA.2688@.TK2MSFTNGP14.phx.gbl...
> xp
> server
>|||Rick, thanks for the tip about the tool.
Because you had to reinstall to fix it, tells me that next time you have
this problem, on the SQL Server itself, bring up the Server Network Utility
(located in Programs->Microsoft SQL Server) and double check that on the
enabled protocols list that TCPIP and Named Pipes is listed. I am betting
that they were not previously. If you want to stop clients from connecting,
this is the place to do so as you would just remove the protocols.
Cheers!
=-Chris
"Rick" <ricardo.blanco@.indap.com.mx> wrote in message
news:eN8LyBWtEHA.2788@.TK2MSFTNGP09.phx.gbl...
> Chris thanks a lot, but ive found other way to solve it, i know maybe its
> not the more correct but i reinstalled the Sql server because i found at
> microsofts web a tool to check the ports, its name is PortQuery, with it
> you can check for Sql server if it is running on a server, or network
> connectivity and other things, i saw that the server doesnt aswer to the
> tool, the ports 1433 and 1434 not respond, so i decided to reinstal Sql
> server, and it solved the problem =)
> the tools url is http://support.microsoft.com/kb/310513/EN-US/
> Rick =)
> "Christopher Conner" <someone@.someplace.com> wrote in message
> news:%23u554sTtEHA.3872@.TK2MSFTNGP15.phx.gbl...
win[vbcol=seagreen]
can[vbcol=seagreen]
pro[vbcol=seagreen]
have[vbcol=seagreen]
between[vbcol=seagreen]
>