cannot establish a connection in sql server 2005 express

hi all

here is the following error, what should i do.

TITLE: Connect to Server

Cannot connect to KANGALERT\SQLEXPRESS.

ADDITIONAL INFORMATION:

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) (Microsoft SQL Server, Error: -1)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476

BUTTONS:

OK

Hi,

Please make sure you've followed all of the steps at http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx in order to enable remote connectivity.

Thanks

cannot copy sqlexpress to another pc for vb.net 2.0 project update

Hi. I have done alot of searching around but can't find answer to this specific problem.

Here is my connection string in vb.net app config

<connectionStrings>
<add name="myfile.My.MySettings.ffgscrmConnectionString" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\myfile.mdf;Integrated Security=True;Connect Timeout=30;User Instance=True"
providerName="System.Data.SqlClient" />
</connectionStrings>

The database is locally attached to the vb.net project residing in a data directory in the project. I am testing installation on a virtual pc - with no sql express managment or other sql server databases attached.

When I do a vb.net setup project and run this on, there is no problem. However, once having done that, when I want to update the app, I can't just copy in the new database along with exe. I get the error:"sql server does not allow remote connections (provider:sql network interfaces error 26 - error locating server/instance specified).

Is this a problem of the virtual PC? I am testing this because I need to be able to send updates to another local machine without using setup program.

Hi,

the destination machine where you copy the files on, does that have SQL Server Express installed ? Otherwise you won′t be able to use the .\SQLEXPRESS instance which points to a local SQLExpress instance on that computer. If there is a SQLExpress instance installed on that machine, make sure you enabled remote connections on this instance. I made a screencast for that, which can be found on my site in the screencast section which will show you how to enabled the remote conenction feature.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Cannot connect toMyserver\SQLEXPRESS

Hi,
i installed Sql server 2005 express edition on an Windows XP professionel
sp2 system, which is alos the IIS server..
Of course i first installed .net Framework 2.0.
I installed it with an administrator account and used following options:
local system
services sql server / sql browser
windows authentification
enable user instance
add user to sql server adminsys role
Further i went to Sql server Configuration Manager and did:
protocols for MSSQLSERVER (service): TCP/IP and shared memory enabled
Finaaly, i went to Sql server Surface Area and did: remote connections:
local and remote connections
using TCP/IP only (and later i also tried: using TCP/IP and named pipes)
My problem is:
--
when starting Sql server Management Studio express, everything seems ok: i
see the server name, authentification (windows), user name (the admin
account), but when clicking on "connect" button, after a while, i get the
error:
"Cannot connect to MYSERVER\SQLEXPRESS.
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) (.Net SqlClient Data Provider)".
1) the optiion 'remote connections' is enabled (with tcp/ip)
2) i even don't use remote connections because sql server is installed on
the same server as the IIS server.
I really have no idea what's the problem and how to solve this. I
uninstalled everything twice (.net framework included) but still same error.
Thanks for help.
CasperIs SQL Server Management Express running on the same system as IIS/SQL
Server? If not, it won't connect.
Again, it makes sense to get the Developer Edition ($50 or less) as it does
not have these limitations.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Casper" <cas@.per.df> wrote in message
news:%237gT%23XJeHHA.4596@.TK2MSFTNGP05.phx.gbl...
> Hi,
> i installed Sql server 2005 express edition on an Windows XP professionel
> sp2 system, which is alos the IIS server..
> Of course i first installed .net Framework 2.0.
> I installed it with an administrator account and used following options:
> local system
> services sql server / sql browser
> windows authentification
> enable user instance
> add user to sql server adminsys role
> Further i went to Sql server Configuration Manager and did:
> protocols for MSSQLSERVER (service): TCP/IP and shared memory enabled
> Finaaly, i went to Sql server Surface Area and did: remote connections:
> local and remote connections
> using TCP/IP only (and later i also tried: using TCP/IP and named pipes)
> My problem is:
> --
> when starting Sql server Management Studio express, everything seems ok: i
> see the server name, authentification (windows), user name (the admin
> account), but when clicking on "connect" button, after a while, i get the
> error:
> "Cannot connect to MYSERVER\SQLEXPRESS.
> 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) (.Net SqlClient Data Provider)".
> 1) the optiion 'remote connections' is enabled (with tcp/ip)
> 2) i even don't use remote connections because sql server is installed on
> the same server as the IIS server.
> I really have no idea what's the problem and how to solve this. I
> uninstalled everything twice (.net framework included) but still same
> error.
> Thanks for help.
> Casper
>
>|||Thanks for replying.
Yes, it's installed on the same server.
I reinstalled and now i can enter the Management Studio, but when i start an
asp.net application which uses a MDF file, when an aspx file tries to access
the MDF file, i get just the same error.
Even when doing debugging that page in VWD i get that error. This
application ran perfect on another machine.
What did i wrong during installation, where do i have to search? i'm very
confused.
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
news:uunyo6SeHHA.5056@.TK2MSFTNGP02.phx.gbl...
> Is SQL Server Management Express running on the same system as IIS/SQL
> Server? If not, it won't connect.
> Again, it makes sense to get the Developer Edition ($50 or less) as it
> does not have these limitations.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "Casper" <cas@.per.df> wrote in message
> news:%237gT%23XJeHHA.4596@.TK2MSFTNGP05.phx.gbl...
>|||Let's see your ConnectionString.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Casper" <ca@.qdq.dfv> wrote in message
news:uMGFqKWeHHA.3632@.TK2MSFTNGP02.phx.gbl...
> Thanks for replying.
> Yes, it's installed on the same server.
> I reinstalled and now i can enter the Management Studio, but when i start
> an asp.net application which uses a MDF file, when an aspx file tries to
> access the MDF file, i get just the same error.
> Even when doing debugging that page in VWD i get that error. This
> application ran perfect on another machine.
> What did i wrong during installation, where do i have to search? i'm very
> confused.
>
> "William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
> news:uunyo6SeHHA.5056@.TK2MSFTNGP02.phx.gbl...
>|||William, i found it:
i reinstalled sqk server express, but it changed the instance name to
MYSERVER (instead of .\SQLEXPRESS). So the connection strings didn't work
and generated that error which has nothing to do woth remoting connections.
Thanks anyway
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
news:OFIzPAXeHHA.3648@.TK2MSFTNGP05.phx.gbl...
> Let's see your ConnectionString.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "Casper" <ca@.qdq.dfv> wrote in message
> news:uMGFqKWeHHA.3632@.TK2MSFTNGP02.phx.gbl...
>

Cannot connect toMyserver\SQLEXPRESS

Hi,
i installed Sql server 2005 express edition on an windows xp professionel
sp2 system, which is alos the IIS server..
Of course i first installed .net Framework 2.0.
I installed it with an administrator account and used following options:
local system
services sql server / sql browser
windows authentification
enable user instance
add user to sql server adminsys role
Further i went to Sql server Configuration Manager and did:
protocols for MSSQLSERVER (service): TCP/IP and shared memory enabled
Finaaly, i went to Sql server Surface Area and did: remote connections:
local and remote connections
using TCP/IP only (and later i also tried: using TCP/IP and named pipes)
My problem is:
when starting Sql server Management Studio express, everything seems ok: i
see the server name, authentification (windows), user name (the admin
account), but when clicking on "connect" button, after a while, i get the
error:
"Cannot connect to MYSERVER\SQLEXPRESS.
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) (.Net SqlClient Data Provider)".
1) the optiion 'remote connections' is enabled (with tcp/ip)
2) i even don't use remote connections because sql server is installed on
the same server as the IIS server.
I really have no idea what's the problem and how to solve this. I
uninstalled everything twice (.net framework included) but still same error.
Thanks for help.
Casper
Is SQL Server Management Express running on the same system as IIS/SQL
Server? If not, it won't connect.
Again, it makes sense to get the Developer Edition ($50 or less) as it does
not have these limitations.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Casper" <cas@.per.df> wrote in message
news:%237gT%23XJeHHA.4596@.TK2MSFTNGP05.phx.gbl...
> Hi,
> i installed Sql server 2005 express edition on an windows xp professionel
> sp2 system, which is alos the IIS server..
> Of course i first installed .net Framework 2.0.
> I installed it with an administrator account and used following options:
> local system
> services sql server / sql browser
> windows authentification
> enable user instance
> add user to sql server adminsys role
> Further i went to Sql server Configuration Manager and did:
> protocols for MSSQLSERVER (service): TCP/IP and shared memory enabled
> Finaaly, i went to Sql server Surface Area and did: remote connections:
> local and remote connections
> using TCP/IP only (and later i also tried: using TCP/IP and named pipes)
> My problem is:
> --
> when starting Sql server Management Studio express, everything seems ok: i
> see the server name, authentification (windows), user name (the admin
> account), but when clicking on "connect" button, after a while, i get the
> error:
> "Cannot connect to MYSERVER\SQLEXPRESS.
> 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) (.Net SqlClient Data Provider)".
> 1) the optiion 'remote connections' is enabled (with tcp/ip)
> 2) i even don't use remote connections because sql server is installed on
> the same server as the IIS server.
> I really have no idea what's the problem and how to solve this. I
> uninstalled everything twice (.net framework included) but still same
> error.
> Thanks for help.
> Casper
>
>
|||Thanks for replying.
Yes, it's installed on the same server.
I reinstalled and now i can enter the Management Studio, but when i start an
asp.net application which uses a MDF file, when an aspx file tries to access
the MDF file, i get just the same error.
Even when doing debugging that page in VWD i get that error. This
application ran perfect on another machine.
What did i wrong during installation, where do i have to search? i'm very
confused.
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
news:uunyo6SeHHA.5056@.TK2MSFTNGP02.phx.gbl...
> Is SQL Server Management Express running on the same system as IIS/SQL
> Server? If not, it won't connect.
> Again, it makes sense to get the Developer Edition ($50 or less) as it
> does not have these limitations.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Casper" <cas@.per.df> wrote in message
> news:%237gT%23XJeHHA.4596@.TK2MSFTNGP05.phx.gbl...
>
|||Let's see your ConnectionString.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Casper" <ca@.qdq.dfv> wrote in message
news:uMGFqKWeHHA.3632@.TK2MSFTNGP02.phx.gbl...
> Thanks for replying.
> Yes, it's installed on the same server.
> I reinstalled and now i can enter the Management Studio, but when i start
> an asp.net application which uses a MDF file, when an aspx file tries to
> access the MDF file, i get just the same error.
> Even when doing debugging that page in VWD i get that error. This
> application ran perfect on another machine.
> What did i wrong during installation, where do i have to search? i'm very
> confused.
>
> "William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
> news:uunyo6SeHHA.5056@.TK2MSFTNGP02.phx.gbl...
>
|||William, i found it:
i reinstalled sqk server express, but it changed the instance name to
MYSERVER (instead of .\SQLEXPRESS). So the connection strings didn't work
and generated that error which has nothing to do woth remoting connections.
Thanks anyway
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
news:OFIzPAXeHHA.3648@.TK2MSFTNGP05.phx.gbl...
> Let's see your ConnectionString.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Casper" <ca@.qdq.dfv> wrote in message
> news:uMGFqKWeHHA.3632@.TK2MSFTNGP02.phx.gbl...
>

Cannot connect to sqlexpress from ssmse (ctp)

I have been using sqlexpress for several months and decided to upgrade the ssmse to the november ctp version. I uninstalled the old ssmse and installed the november release from ctp.

I verified that the tcp/ip and named pipes are enable in the config manager. I attempted using these connection strings:

\sqlexpress, (local)\sqlexpress, or server name\sqlexpress

All fail with the following message:

Cannot connect to WALLY1\sqlexpress

--
ADDITIONAL INFORMATION:

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) (Microsoft SQL Server, Error: -1)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476

BUTTONS:

OK

We need a little more information to troubleshoot your problem.

Are you running SSMSE and SQLExpress on the same machine? Are you able to connect to SQLExpress using SQLCMD?

Thanks,
Dan

|||Try to connect either with TCP/IP or named-pipes enabled and not with both the options enabled.
I have had this problem before and when used named-pipes alone it resolved the problem and ensure the ALIAS is defined properly and you can ping the server.|||

Are you running everything from the same machine or are you trying to connect to a remote SQL Server?

Cheers,
Dan

Cannot connect to SQLExpress

Hi, I'm using Microsoft SQL Sever Management Studio Express. But all of a sudden, if I clicked connect button, the messageBox pops up and it doesn't let me connect. It says "TITLE: Connect to Server

Cannot connect to YOUR-4105E587B6\SQLEXPRESS.

ADDITIONAL INFORMATION:

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) (Microsoft SQL Server, Error: -1)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476

BUTTONS:

OK

I didn't have such a problem before. If someone could help to solve to this problem, I appreciate it. Thanks.

YOu will have to enable remote ocnnections. if have a screencast for that on my site (which is currently not online due to server problems at my provider). The setting is made through Programs >MS SQL Server > Configuration Tools > Surface Area Configuration > ..for Services and Connections > SQL Server <Remote Connections > Protocols > ENbale the appropiate protocols > restart the Service. If you need additional help, I can send you the files of the screencast (flash).

HTH, jens K. Suessmeyer.

http://www.sqlserver2005.de
|||

Thank you for the tip Mr.Jens.

I'll try that!

Ken

|||

Hi Jens and KentaroM

i have the same problems, but i have tried to make the surgest from Jens but i can't find it.

I have open the Programs >MS SQL Server > Configuration Tools > Surface Area Configuration > Surface Area Configuration for Services and Connections > SQL Server > Remote Connections

i have this options:

local connections only or

Local and remote connections

Using TCP/IP only

Using Name pipes only

Using TCP/IP and name pipes

it it not possble for me to find Protocols > ENbale the appropiate protocols

Do anny have a surgestion to help me with my problems?

Alif

|||

I also have the same problem, and i have opened the remote connections and even so I cannot.

I have all the open ports and appears the same error.

Cannot connect to SQLExpress

Hi, I'm using Microsoft SQL Sever Management Studio Express. But all of a sudden, if I clicked connect button, the messageBox pops up and it doesn't let me connect. It says "TITLE: Connect to Server

Cannot connect to YOUR-4105E587B6\SQLEXPRESS.

ADDITIONAL INFORMATION:

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) (Microsoft SQL Server, Error: -1)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476

BUTTONS:

OK

I didn't have such a problem before. If someone could help to solve to this problem, I appreciate it. Thanks.

YOu will have to enable remote ocnnections. if have a screencast for that on my site (which is currently not online due to server problems at my provider). The setting is made through Programs >MS SQL Server > Configuration Tools > Surface Area Configuration > ..for Services and Connections > SQL Server <Remote Connections > Protocols > ENbale the appropiate protocols > restart the Service. If you need additional help, I can send you the files of the screencast (flash).

HTH, jens K. Suessmeyer.

http://www.sqlserver2005.de|||

Thank you for the tip Mr.Jens.

I'll try that!

Ken

|||

Hi Jens and KentaroM

i have the same problems, but i have tried to make the surgest from Jens but i can't find it.

I have open the Programs >MS SQL Server > Configuration Tools > Surface Area Configuration > Surface Area Configuration for Services and Connections > SQL Server > Remote Connections

i have this options:

local connections only or

Local and remote connections

Using TCP/IP only

Using Name pipes only

Using TCP/IP and name pipes

it it not possble for me to find Protocols > ENbale the appropiate protocols

Do anny have a surgestion to help me with my problems?

Alif

|||

I also have the same problem, and i have opened the remote connections and even so I cannot.

I have all the open ports and appears the same error.

Cannot Connect to SQLExpress

Hi everyone,

I'd like to ask some help. My prob may seem very basic but as a matter of fact i'm a newbie to .net and sql 2005. I'm trying out this product but I encountered an error. After installing sql server express 2005, and using my server instance name (the default name "SQlExpress" during install) and password to connect, I always get the error "Timeout expired. The timeout period elapsed prior to completion... blah blah blah". Though I entered the right user name and password (which I entered during install), I always get this error.

Additional: I indicated mixed mode during install and defined my sa account and password

Anyone who can help me.. like adjusting configs, etc...
Kobe

Is the SQL Server service started?

Also, refer to the blog posted here:

http://blogs.msdn.com/sqlexpress/

|||Thanks Rob! This helped me a lot.|||Chaps,

I have the same problem. (Including the novice attributes).

What was the fix? I looked through the blog as suggested but could not readily find the cure.

MRW

Cannot Connect to SQLExpress

Hi everyone,

I'd like to ask some help. My prob may seem very basic but as a matter of fact i'm a newbie to .net and sql 2005. I'm trying out this product but I encountered an error. After installing sql server express 2005, and using my server instance name (the default name "SQlExpress" during install) and password to connect, I always get the error "Timeout expired. The timeout period elapsed prior to completion... blah blah blah". Though I entered the right user name and password (which I entered during install), I always get this error.

Additional: I indicated mixed mode during install and defined my sa account and password

Anyone who can help me.. like adjusting configs, etc...
Kobe

Is the SQL Server service started?

Also, refer to the blog posted here:

http://blogs.msdn.com/sqlexpress/

|||Thanks Rob! This helped me a lot.|||Chaps,

I have the same problem. (Including the novice attributes).

What was the fix? I looked through the blog as suggested but could not readily find the cure.

MRW

Cannot connect to SQL express database ??

Dear all,
I have setup a database under SQLexpress 2005 which is install on a Vista OS
.
I can manage without any problem my database from the VIsta workstation.
Then on an other PC, I am trying to create a connection to that databse with
.NET 1.1, but no luck
I ma using similar conenction string as for an SQL server databse excpet
that Server="MyWorkStationName\SQLEXPRESS".
I have place the conenctionstring in a config file as follow :
" Database=Line_Config;Server=MyWorkStatio
nName\SQLEXPRESS;uid=rptuser;Pwd=re
porting"
What is wrong that prebvent me from connection to database ?
Is it possible to connect to an SQLExpress database located on an other PC ?
thnaks for help
regards
sergeProbably either the SQL Server Express instance has not enabled remote
connections, or a firewall is blocking the connection.
Run through the short tutorial in Books Online and see if that solves the
problem. The tutorial is also online at
http://msdn2.microsoft.com/en-us/library/ms345318.aspx Note that lesson 2 is
Connecting from Another Computer.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:067F10D8-72B1-4858-AE9F-E5EEF213BEF1@.microsoft.com...
> Dear all,
> I have setup a database under SQLexpress 2005 which is install on a Vista
> OS.
> I can manage without any problem my database from the VIsta workstation.
> Then on an other PC, I am trying to create a connection to that databse
> with
> .NET 1.1, but no luck
> I ma using similar conenction string as for an SQL server databse excpet
> that Server="MyWorkStationName\SQLEXPRESS".
> I have place the conenctionstring in a config file as follow :
>
> " Database=Line_Config;Server=MyWorkStatio
nName\SQLEXPRESS;uid=rptuser;Pwd=
reporting"
> What is wrong that prebvent me from connection to database ?
> Is it possible to connect to an SQLExpress database located on an other PC
> ?
> thnaks for help
> regards
> serge|||Thnaks for your reply...
I have check seetings as describe in this link.
What happen is that I have SQL express install on a Vista machine
Then I set use of tcp port from the surface configuration tool and set port
to 1500
From a simple remote machine running w2000, I try to establish an ODBC
connection to my VIsta machine where SQL express is installed.
For that I have install on my 2000 machine the SQL native client for 2005
and try to define a DSN name but when trying to connect...no way...
Any ideas ?
regards
serge
"Rick Byham, (MSFT)" wrote:

> Probably either the SQL Server Express instance has not enabled remote
> connections, or a firewall is blocking the connection.
> Run through the short tutorial in Books Online and see if that solves the
> problem. The tutorial is also online at
> http://msdn2.microsoft.com/en-us/library/ms345318.aspx Note that lesson 2
is
> Connecting from Another Computer.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "calderara" <calderara@.discussions.microsoft.com> wrote in message
> news:067F10D8-72B1-4858-AE9F-E5EEF213BEF1@.microsoft.com...
>|||Did you stop and restart SQL Server 2005 Express Edition after setting 1500
as the fixed port?
Are you attempting to connect to the Express Edition by name in the format
computer_name\SQLExpress ?
Is the SQL Server Browser service running?
Can you connect to the Express Edition by the port number using
computer_name,1500 or by IP address in the format 127.025.144.315,1500 ?
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:F1AB79D1-899E-40C6-BE14-21D0305C36CA@.microsoft.com...[vbcol=seagreen]
> Thnaks for your reply...
> I have check seetings as describe in this link.
> What happen is that I have SQL express install on a Vista machine
> Then I set use of tcp port from the surface configuration tool and set
> port
> to 1500
> From a simple remote machine running w2000, I try to establish an ODBC
> connection to my VIsta machine where SQL express is installed.
> For that I have install on my 2000 machine the SQL native client for 2005
> and try to define a DSN name but when trying to connect...no way...
> Any ideas ?
> regards
> serge
> "Rick Byham, (MSFT)" wrote:
>|||OK it works now rick...
I have made 2 mistakes...
Frist of all I forgot to open the port 1500 in my windows firewall.
Then I was accessing my server by using <myPCname>\SQLEXPRESS as I use to do
normally with SQL server.
SO in order to work I have to connect using tcp:<myPCname>\SQLEXPRESS,1500
But I like whem I undersatnd things. This connection string using sytax
above is use like that only for this express edition ? I guess not, I mean I
have made many connection like that with SQL server ( On a real server sure)
and I was juist using the instance and Pc name.
Or may be it would work also if I add left the default setting when you use
TCP as port 1443 and let SQL as dynamic mode and then just open the port 144
3
on my firewall. Then use as connection string :<myPCname>\SQLEXPRESS.
But of course dynamic means dynamic.
Does it means that this dynamic TP port seting should never be use with SQL
server ?
regards
serge
"Rick Byham, (MSFT)" wrote:

> Did you stop and restart SQL Server 2005 Express Edition after setting 150
0
> as the fixed port?
> Are you attempting to connect to the Express Edition by name in the format
> computer_name\SQLExpress ?
> Is the SQL Server Browser service running?
> Can you connect to the Express Edition by the port number using
> computer_name,1500 or by IP address in the format 127.025.144.315,1500 ?
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "calderara" <calderara@.discussions.microsoft.com> wrote in message
> news:F1AB79D1-899E-40C6-BE14-21D0305C36CA@.microsoft.com...
>|||Connecting to the server name (<myPCname>\SQLEXPRESS) should work, if the
SQL Server Browser service is running. However, yes, you are correct that if
SQL Server Express Edition is using dynamic ports, then the port could
change to one that is blocked by the firewall. So you will need to switch
SQL Server Express Edition to a fixed port.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:B778178D-FF1E-4827-981E-369B3C5C9AFE@.microsoft.com...[vbcol=seagreen]
> OK it works now rick...
> I have made 2 mistakes...
> Frist of all I forgot to open the port 1500 in my windows firewall.
> Then I was accessing my server by using <myPCname>\SQLEXPRESS as I use to
> do
> normally with SQL server.
> SO in order to work I have to connect using tcp:<myPCname>\SQLEXPRESS,1500
> But I like whem I undersatnd things. This connection string using sytax
> above is use like that only for this express edition ? I guess not, I mean
> I
> have made many connection like that with SQL server ( On a real server
> sure)
> and I was juist using the instance and Pc name.
> Or may be it would work also if I add left the default setting when you
> use
> TCP as port 1443 and let SQL as dynamic mode and then just open the port
> 1443
> on my firewall. Then use as connection string :<myPCname>\SQLEXPRESS.
> But of course dynamic means dynamic.
> Does it means that this dynamic TP port seting should never be use with
> SQL
> server ?
> regards
> serge
> "Rick Byham, (MSFT)" wrote:
>

Cannot connect to SQL express database ??

Dear all,
I have setup a database under SQLexpress 2005 which is install on a Vista OS.
I can manage without any problem my database from the VIsta workstation.
Then on an other PC, I am trying to create a connection to that databse with
..NET 1.1, but no luck
I ma using similar conenction string as for an SQL server databse excpet
that Server="MyWorkStationName\SQLEXPRESS".
I have place the conenctionstring in a config file as follow :
"Database=Line_Config;Server=MyWorkStationName\SQL EXPRESS;uid=rptuser;Pwd=reporting"
What is wrong that prebvent me from connection to database ?
Is it possible to connect to an SQLExpress database located on an other PC ?
thnaks for help
regards
serge
Probably either the SQL Server Express instance has not enabled remote
connections, or a firewall is blocking the connection.
Run through the short tutorial in Books Online and see if that solves the
problem. The tutorial is also online at
http://msdn2.microsoft.com/en-us/library/ms345318.aspx Note that lesson 2 is
Connecting from Another Computer.
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:067F10D8-72B1-4858-AE9F-E5EEF213BEF1@.microsoft.com...
> Dear all,
> I have setup a database under SQLexpress 2005 which is install on a Vista
> OS.
> I can manage without any problem my database from the VIsta workstation.
> Then on an other PC, I am trying to create a connection to that databse
> with
> .NET 1.1, but no luck
> I ma using similar conenction string as for an SQL server databse excpet
> that Server="MyWorkStationName\SQLEXPRESS".
> I have place the conenctionstring in a config file as follow :
>
> "Database=Line_Config;Server=MyWorkStationName\SQL EXPRESS;uid=rptuser;Pwd=reporting"
> What is wrong that prebvent me from connection to database ?
> Is it possible to connect to an SQLExpress database located on an other PC
> ?
> thnaks for help
> regards
> serge
|||Thnaks for your reply...
I have check seetings as describe in this link.
What happen is that I have SQL express install on a Vista machine
Then I set use of tcp port from the surface configuration tool and set port
to 1500
From a simple remote machine running w2000, I try to establish an ODBC
connection to my VIsta machine where SQL express is installed.
For that I have install on my 2000 machine the SQL native client for 2005
and try to define a DSN name but when trying to connect...no way...
Any ideas ?
regards
serge
"Rick Byham, (MSFT)" wrote:

> Probably either the SQL Server Express instance has not enabled remote
> connections, or a firewall is blocking the connection.
> Run through the short tutorial in Books Online and see if that solves the
> problem. The tutorial is also online at
> http://msdn2.microsoft.com/en-us/library/ms345318.aspx Note that lesson 2 is
> Connecting from Another Computer.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "calderara" <calderara@.discussions.microsoft.com> wrote in message
> news:067F10D8-72B1-4858-AE9F-E5EEF213BEF1@.microsoft.com...
>
|||Did you stop and restart SQL Server 2005 Express Edition after setting 1500
as the fixed port?
Are you attempting to connect to the Express Edition by name in the format
computer_name\SQLExpress ?
Is the SQL Server Browser service running?
Can you connect to the Express Edition by the port number using
computer_name,1500 or by IP address in the format 127.025.144.315,1500 ?
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:F1AB79D1-899E-40C6-BE14-21D0305C36CA@.microsoft.com...[vbcol=seagreen]
> Thnaks for your reply...
> I have check seetings as describe in this link.
> What happen is that I have SQL express install on a Vista machine
> Then I set use of tcp port from the surface configuration tool and set
> port
> to 1500
> From a simple remote machine running w2000, I try to establish an ODBC
> connection to my VIsta machine where SQL express is installed.
> For that I have install on my 2000 machine the SQL native client for 2005
> and try to define a DSN name but when trying to connect...no way...
> Any ideas ?
> regards
> serge
> "Rick Byham, (MSFT)" wrote:
|||OK it works now rick...
I have made 2 mistakes...
Frist of all I forgot to open the port 1500 in my windows firewall.
Then I was accessing my server by using <myPCname>\SQLEXPRESS as I use to do
normally with SQL server.
SO in order to work I have to connect using tcp:<myPCname>\SQLEXPRESS,1500
But I like whem I undersatnd things. This connection string using sytax
above is use like that only for this express edition ? I guess not, I mean I
have made many connection like that with SQL server ( On a real server sure)
and I was juist using the instance and Pc name.
Or may be it would work also if I add left the default setting when you use
TCP as port 1443 and let SQL as dynamic mode and then just open the port 1443
on my firewall. Then use as connection string :<myPCname>\SQLEXPRESS.
But of course dynamic means dynamic.
Does it means that this dynamic TP port seting should never be use with SQL
server ?
regards
serge
"Rick Byham, (MSFT)" wrote:

> Did you stop and restart SQL Server 2005 Express Edition after setting 1500
> as the fixed port?
> Are you attempting to connect to the Express Edition by name in the format
> computer_name\SQLExpress ?
> Is the SQL Server Browser service running?
> Can you connect to the Express Edition by the port number using
> computer_name,1500 or by IP address in the format 127.025.144.315,1500 ?
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "calderara" <calderara@.discussions.microsoft.com> wrote in message
> news:F1AB79D1-899E-40C6-BE14-21D0305C36CA@.microsoft.com...
>
|||Connecting to the server name (<myPCname>\SQLEXPRESS) should work, if the
SQL Server Browser service is running. However, yes, you are correct that if
SQL Server Express Edition is using dynamic ports, then the port could
change to one that is blocked by the firewall. So you will need to switch
SQL Server Express Edition to a fixed port.
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:B778178D-FF1E-4827-981E-369B3C5C9AFE@.microsoft.com...[vbcol=seagreen]
> OK it works now rick...
> I have made 2 mistakes...
> Frist of all I forgot to open the port 1500 in my windows firewall.
> Then I was accessing my server by using <myPCname>\SQLEXPRESS as I use to
> do
> normally with SQL server.
> SO in order to work I have to connect using tcp:<myPCname>\SQLEXPRESS,1500
> But I like whem I undersatnd things. This connection string using sytax
> above is use like that only for this express edition ? I guess not, I mean
> I
> have made many connection like that with SQL server ( On a real server
> sure)
> and I was juist using the instance and Pc name.
> Or may be it would work also if I add left the default setting when you
> use
> TCP as port 1443 and let SQL as dynamic mode and then just open the port
> 1443
> on my firewall. Then use as connection string :<myPCname>\SQLEXPRESS.
> But of course dynamic means dynamic.
> Does it means that this dynamic TP port seting should never be use with
> SQL
> server ?
> regards
> serge
> "Rick Byham, (MSFT)" wrote:

Cannot connect to server

Hi there.

I've been doing this SQLEXPRESS stuff peacefully for many months now and just yesterday I saved some tables in it. This morning my computer acts just weird. We have thunderstorm in the area and the sky is dark-maybe it is the reason but I do have a UPS that is supposed to smooth things out.

Anyhow, when I tried to connect I got rejected. The connection is local, on the same computer, same had disk. I haven't done anything to change the parameters. I have been saving the whole Server comprehensively but neglected to do it for the past 3-4 days perhaps.

What can I do? I do not even know how I can restore the databases if I cannot get in?

Shared Memory Provider, error 40 - Could not open a connection to SQL Server (Microsoft SQL Server, Error 2).

Thanks.

I had experienced a problem and here is my story. Our network admin in Sweden changed the network settings. Basically it shouldn't affect our daily process, however the SQL server doesn't work. At that time, I also uses the local connection and very standard settings but just cannot connect to SQL server. Then I reinstalled SQL server Express and attach my database files and it worked. No data was lost luckily. I guess when the thunderstorm came, you network have been changed (for example: reset). Please try to reinstall and attach database, hope it helps.

Br,

L

|||

Thank you L,

Actually the problem resolved itself a few minutes after I did posting. I could not delete the post on time and this is why. It turns out when I turned my computer on this morning MS started downloading 9 updates into my XP. I was not aware of it and was angry that my applications could not really start. CPU was 100% busy.

After the SQL Server fiasco I decided to turn the computer off and that was when it began installing them all. It took almost an hour and my computer is very fast. After it finished I restarted it and SQL Server responded immediately.

Apparently when the updates were put in but not installed yet it created a conflict. I was really scared.

- Alex

Cannot connect to MYSERVER\SQLEXPRESS

Hi,

i installed Sql server 2005 express edition on an windows xp professionel sp2 system, which is also the IIS server..
Of course i first installed .net Framework 2.0.

I installed it with an administrator account and used following options:
local system
services sql server / sql browser
windows authentification
enable user instance
add user to sql server adminsys role

Further i went to Sql server Configuration Manager and did:
protocols for MSSQLSERVER (service): TCP/IP and shared memory enabled

Finaaly, i went to Sql server Surface Area and did: remote connections:
local and remote connections
using TCP/IP only (and later i also tried: using TCP/IP and named pipes)

My problem is:
-----
when starting Sql server Management Studio express, everything seems ok: i see the server name, authentification (windows), user name (the admin
account), but when clicking on "connect" button, after a while, i get the error:
"Cannot connect to MYSERVER\SQLEXPRESS.
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) (.Net SqlClient Data Provider)".

I don't understand because:
1) the optiion 'remote connections' is enabled (with tcp/ip)
2) i even don't use remote connections because sql server is installed on
the same server as the IIS server.

I really have no idea what's the problem and how to solve this. I uninstalled everything twice (.net framework included) but still same error.

Thanks for help.
Tartuffe

check to make sure the service is started.

Start --> Control Panel --> Administrative Tools --> Services

In the "Services" window, make sure the service is started. If it is started, try re-starting it.

|||

Hi there!

I am also having a similar problem, but in my case management studio just does not detect any database engine instance (it is running and I checked it) and the drop-down list for servername is empty! I even tried rebuilding the OS and installed SQL server 2005 again, but in vain. Kindly post a solution if you arrive at it, so will I.

Regards

|||

Hello vraval, try this:

[HOSTNAME]\SQLEXPRESS example: SEAN\SQLEXPRESS

to get the host name, open the sql server configuration manager --> "SQL Server 2005 Services" on the left --> right click and select "properties" on 'SQL Server (SQLEXPRESS) - in the right window. In the properties menu, select the 'service' tab and you can find the Host Name property here. Put the HOSTNAME, followed by \SQLEXPRESS -- HOSTNAME\SQLEXPRESS as the server name when logging in.

|||

Hi Sean!

Many thanks for the reply and solving my problem. I am now able to connect to my database engine.

God knows why Microsoft People do not show these important directions.

Thanks and warm regards.

|||

Hi all,

glad for you Vraval, but i still have that error after restarting the service (which was started anyway).

i tried with shared memory, with tcp/ip, without Zone alarm, with a time-out of 60 sec etc ... still same error.

What can i try more?

|||Hello tartuffe,

Check out the following links, if them do not help .. im out of ideas. Im sure you have searched and most likely have found these post also from the way it sounds, but here they are:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=271795&SiteID=1

http://aspnet.tribe.net/thread/628e81d8-6a77-4687-ac16-085d54a376f2

have you asked your question on the MSDN forums? if not, you should search and ask the question there also :) They are also informative and the forums have a wealth of information.|||Sean, i found it:

i reinstalled sqk server express, but it changed the instance name to
MYSERVER (instead of .\SQLEXPRESS). So the connection strings didn't work
and generated that error which has nothing to do woth remoting connections.

Thanks anyway

Cannot connect remotely to SQLExpress via SQL Server Management Studio Express

Hi all,

I'm having a little trouble connecting to a SQLExpress instance on a remote domain using SQL Server Management Studio Express.

I've read that by default the program is set up locally only, so have edited the Surface Area Configuration. It only gives me the option to edit 'Services and Connections' on the localhost, but have edited the Remote Connections to use TCP/IP and Named Pipes.

In the Management Studio, I enter the server name, and login credentials. On the Connection Properties tab I changed the network protocol to TCP/IP though everytime I attempt to connect I get the following error message:

Any help would be greatly appreciated.

Rich

Hello,

Does this help you?http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

Regards,

Louis

|||

Hmm, I followed the steps through, the only difference seemed the firewall exceptions which I have now edited, but still get the same error message.

Any ideas?

|||

from the client machine, can you ping the database server? Can you log the denial on the sql server box when you connect to it?

|||

How would I go about doing this?

Cheers