MSDE sql express on laptop, error 26

hi, I am running Visual Studio.net 2005 on my laptop, MSDE sql express was
installed during the installation, finally trying to get an sql database to
work, i am a newbie to both Visual studio and SQL, anyway i can see the
database inside server explorer and all its talbles, but when i try to run
the application i get an error has occured while establishing a connection
the 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
locatiang server/instance Specified
i read similar posts in this forum and tried the following
enabled TCP/Ip on the server and client, do i need any of the other
protocols enabled: shared memory is enabled, named pipes is disabled, tcp/i
p
is enablaed and VIA is disabled, this is for the server, for the client
shared memory, tcp/ip, named pipes are all enabled while via is disabled
i ran the SQL server surface area configuration and choose the Surface area
configuration for servcies and connections, under there, the radio buttion
for local and remote connection/Using TCP/IP only are selected. so i think
that is ok
i copi8ed a SQL database to a folder in the database and set the connection
using the wizard, i tested the connection and it is ok.
are there other things to do are other places to check,Possibility 1:
Start the SQL Server Browser Service. SQL Server 2005 Express installs as a
named instance called sqlexpress. The SQL Server Browser Service resolves a
connection attempt of <computer_name>\sqlexpress to a port number. Without
SQL Server Browser, when connecting to a named instance you need to specify
the port number when you connect. And all named instances like SQL Server
2005 listen on dynamic ports, so the port may change when SQL Server is
started.
Possibility 2:
If you are running on a laptop, you may be running on Windows XP, service
pack 2 which automatically turns on the Windows firewall. If you are
connecting from the same server, you should be connecting using Shared
Memory so that won't matter. If you are connecting from another computer,
you may need to open a TCP port, or allow sqlservr.exe to communicate
through the firewall.
If this information is helpful, more information is available at
http://msdn2.microsoft.com/en-us/library/ms345318(en-US,SQL.90).aspx
--
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Frank Bruhn" <FrankBruhn@.discussions.microsoft.com> wrote in message
news:E96EEA76-4277-4D80-8B75-79D945744E95@.microsoft.com...
> hi, I am running Visual Studio.net 2005 on my laptop, MSDE sql express was
> installed during the installation, finally trying to get an sql database
> to
> work, i am a newbie to both Visual studio and SQL, anyway i can see the
> database inside server explorer and all its talbles, but when i try to run
> the application i get an error has occured while establishing a connection
> the 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
> locatiang server/instance Specified
> i read similar posts in this forum and tried the following
> enabled TCP/Ip on the server and client, do i need any of the other
> protocols enabled: shared memory is enabled, named pipes is disabled,
> tcp/ip
> is enablaed and VIA is disabled, this is for the server, for the client
> shared memory, tcp/ip, named pipes are all enabled while via is disabled
> i ran the SQL server surface area configuration and choose the Surface
> area
> configuration for servcies and connections, under there, the radio buttion
> for local and remote connection/Using TCP/IP only are selected. so i think
> that is ok
> i copi8ed a SQL database to a folder in the database and set the
> connection
> using the wizard, i tested the connection and it is ok.
> are there other things to do are other places to check,
>
>