Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 Express Edition and Compact Edition (2005)
 sqlexpress not capable of remote?

Author  Topic 

jen
Master Smack Fu Yak Hacker

4110 Posts
Posted - 2006-02-22 : 03:21:21
I'm a noob in sql2005

I have successfuly (i think) installed mssql2005 express and management studio on server and client respectively.

I can connect from the client tools to the server locally (using proper named instances) but can't connect from client.

The error says that it is not possible to connect to the server remotely using the version installed (or something like that)

What combinations can I use then?

TIA

--------------------
keeping it simple...

karuna
Aged Yak Warrior

582 Posts
Posted - 2006-02-22 : 04:56:54
Jen,

I think its the same issue we discussed in the other thread right?

Let me get something clear here. Correct me if I missed something

BoxA                     BoxB
Sql Express              Sql Server 2005 
Sql Express Mgmt Studio  Sql Server Mgmt Studio

You are not able to connect from BoxA Sql Express Mgmt Studio to Sql Server 2005 on BoxB.

You are able to connect to Sql Express in BoxA from Sql Express Mgmt Studio BoxA

Is this your problem? If so, can you try this setup.

BoxA                     BoxB
Sql Express              Sql Server 2005 
Sql Express Mgmt Studio  Sql Server Mgmt Studio

that worked for me

Thanks

Karunakaran
Go to Top of Page

jen
Master Smack Fu Yak Hacker

4110 Posts
Posted - 2006-02-22 : 20:31:19
yep and you advised me to post here coz it's express

here's my setup:

server client
mssql2005 express sql management studio (express)
sql management studio (express)

i do not have any licensed version yet... the purpose of this exercise is for me to evaluate the product

unfortunately, the evaluation product we have is beta 2 and I want to evaluate the latest release (will there be a difference? If I start checking out the features and performance, will it be a close evaluation from previous and current version of mssql2005?)

TIA...



--------------------
keeping it simple...
Go to Top of Page

eyechart
Master Smack Fu Yak Hacker

3575 Posts
Posted - 2006-02-22 : 21:30:24
was sqlexpress installed with TCP/IP enabled? By default MSDE 2000 rev A started installing itself with tcp/ip disabled - I wonder if microsoft continued that trend when they released SQL Express. Anyway, worth a look if you haven't already done that.

The SSMSE is still beta, actually it is the November CTP, so I suppose that means it is closer to a release candidate than a beta. Why they couldn't call it a release candidate is anyone's guess..

Anyway, the SSMSE CTP works with the RTM releases of SQL 2005 and SQL 2005 Express.

Also, what is there to license with SQL Express? it is the free version right?




-ec
Go to Top of Page

jen
Master Smack Fu Yak Hacker

4110 Posts
Posted - 2006-02-23 : 01:17:44
i meant getting the licensed version not express,

ok one last question:

has anyone used the express edition on both server and client,
and successfully connected from client (a separate box from server)?

if yes, was it a straightforward installation? did you need to do some pre-installation activities?


TIA

--------------------
keeping it simple...
Go to Top of Page

mikewa
Microsoft SQL Server Product Team

84 Posts
Posted - 2006-02-23 : 01:25:06
Hi Jen,

Which product are you using Beta 2 of? SQL Express released last November. SQL Express is a free product so there is no reason to continue using the beta release; you can download the release version from http://msdn.microsoft.com/sql/express/.

There are a number of compatibility problems between pre-release products such as Beta 2 and post release stuff such as the Management Studio Express CTP. These could be part of your problems.

Once we figure out the version information, it will be easier to dermine what the problem with trying to connect is. For starters I'll let you know that SQL Express does not enable remote connection by default, if you haven't enabled them you won't be able to connect from a remote machine. You can find information about configuring SQL Express to accept remote connections in our blog at http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx.

Hope this helps.

Regards,
Mike Wachal
SQL Express

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Go to Top of Page

eyechart
Master Smack Fu Yak Hacker

3575 Posts
Posted - 2006-02-23 : 03:15:37
quote:
Originally posted by mikewa
For starters I'll let you know that SQL Express does not enable remote connection by default, if you haven't enabled them you won't be able to connect from a remote machine. You can find information about configuring SQL Express to accept remote connections in our blog at http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx.


Just as I thought! ;)

Good to have another expert from Microsoft participating here.




-ec
Go to Top of Page

karuna
Aged Yak Warrior

582 Posts
Posted - 2006-02-23 : 04:12:24
quote:
Originally posted by jen


unfortunately, the evaluation product we have is beta 2 and I want to evaluate the latest release
TIA...

--------------------
keeping it simple...


I suggest you to try with the latest release of express, and see how it goes.

Thanks

Karunakaran
Go to Top of Page

jen
Master Smack Fu Yak Hacker

4110 Posts
Posted - 2006-02-24 : 07:49:00
Thanks Mikewa,

I will try that on Monday (no friday nights for me anymore, i made it a rule ) and let you know what happens...

I appreciate your help and in advance also



--------------------
keeping it simple...
Go to Top of Page

mikewa
Microsoft SQL Server Product Team

84 Posts
Posted - 2006-02-24 : 12:23:47
Good rule Jen! I'll have to see about following that rule myself.

I look forward to hearing back on how this turns out.

Regards,
Mike Wachal
SQL Express

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Go to Top of Page

jen
Master Smack Fu Yak Hacker

4110 Posts
Posted - 2006-02-26 : 22:12:44
Thanks Mike!

You're an angel!

Everything seems to be in order...

And I like the way the ctp picked up the instance without me having to define it

I'll have a separate post for my next question, regarding security



--------------------
keeping it simple...
Go to Top of Page

jen
Master Smack Fu Yak Hacker

4110 Posts
Posted - 2006-02-27 : 02:24:31
I realized that sqlexpress is for developers

what I now need is an evaluation copy of mssql2005 to test out the sqlserver agent stuff like alerts and jobs and dts and replication and...

can somebody help me get to that site? pretty please??

--i tried but i get the wrong combination of ctp and server


thank you very much in advance

--------------------
keeping it simple...
Go to Top of Page

khtan
In (Som, Ni, Yak)

17689 Posts
Posted - 2006-02-27 : 02:50:05
Download SQL Server 2005 Trial Software at
http://www.microsoft.com/sql/downloads/trial-software.mspx#EFAA

----------------------------------
'KH'
Go to Top of Page

namviet
Starting Member

3 Posts
Posted - 2006-03-01 : 03:15:44
I still can not make connection to the SQL EXPRESS after do following the instruction in that blog: http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

STILL receive this error:

C:\>SQLCMD -E -S NAMVIET\SQLEXPRESS,1434
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 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..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.

Please help me to solve this problem!
Thanks!

(@~@)
"
Go to Top of Page

jen
Master Smack Fu Yak Hacker

4110 Posts
Posted - 2006-03-01 : 03:56:03
is 1434 your tcp port?

--------------------
keeping it simple...
Go to Top of Page

namviet
Starting Member

3 Posts
Posted - 2006-03-01 : 20:50:18
quote:
Originally posted by jen

is 1434 your tcp port?

--------------------
keeping it simple...


Sure!
The same error still happen when I remove the port in the command line (while I actived Browser services)
I do not know which reason for the error!

(@~@)
"
Go to Top of Page

jen
Master Smack Fu Yak Hacker

4110 Posts
Posted - 2006-03-01 : 21:17:56
Have you followed through the link that Mike provided?

Go through it one more time and step by step, also take note of the sqlexpress version you've installed

--------------------
keeping it simple...
Go to Top of Page

mikewa
Microsoft SQL Server Product Team

84 Posts
Posted - 2006-03-01 : 23:04:16
This seems like a firewall issue based on the error. Let's do the short version of the "remote connection" check list. It's a bit confusing so people sometimes miss something. (At least I do and it's my product! )

1. SQL Express is running (hey, gotta check)
2. SQL Browser is running
4. TCP/IP is enabled as a server protocol
3. You've created an Exception in your firewall for SQL Express
4. You've created an Exception in your firewall for SQL Browser

The most common mistake is to forget #4, the second most common would be to create an exception for the wrong copy of SQL in #3 since each instance of SQL has a separate executable file. (If you've only installed one, you probably haven't made this mistake.)

One final check, up till now I've assumed that you can actually successfully connect from the local computer; I guess I should verify that that is true. (Is it?)

Regards,
Mike Wachal
SQL Express

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Go to Top of Page

namviet
Starting Member

3 Posts
Posted - 2006-03-02 : 03:37:42
quote:
Originally posted by mikewa

This seems like a firewall issue based on the error. Let's do the short version of the "remote connection" check list. It's a bit confusing so people sometimes miss something. (At least I do and it's my product! )

1. SQL Express is running (hey, gotta check)
2. SQL Browser is running
4. TCP/IP is enabled as a server protocol
3. You've created an Exception in your firewall for SQL Express
4. You've created an Exception in your firewall for SQL Browser

The most common mistake is to forget #4, the second most common would be to create an exception for the wrong copy of SQL in #3 since each instance of SQL has a separate executable file. (If you've only installed one, you probably haven't made this mistake.)

One final check, up till now I've assumed that you can actually successfully connect from the local computer; I guess I should verify that that is true. (Is it?)

Regards,
Mike Wachal
SQL Express

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


Dear mikewa,
You right! I get mistake in #4 (4. You've created an Exception in your firewall for SQL Browser)
Everything is now done!
Thank all of you!


(@~@)
"
Go to Top of Page

mikewa
Microsoft SQL Server Product Team

84 Posts
Posted - 2006-03-03 : 22:37:25
Glad to hear things worked out namviet.

Regards,
Mike Wachal
SQL Express

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Go to Top of Page
   

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources

Articles

Forums

Blogs

Contact Us

About the Site