Remotely Register SQL Server 2005 Express in Enterprise Manager

I have SQL Server 2005 Express installed on a windows server 2003 standard edition. I have configured the windows firewall to allow exceptions for sqlservr.exe and sqlbrowser.exe. I have enabled remote and local connections using tcp/ip & Named Pipes through the Sql Server Surface Area Connection utility. I am able to telnet into the server with: telnet <server ip> <1433>.

Here is the strange part: I am able to connect to the Sql Server remotely from a development machine via Sql Server Management Studio Express, but I am unable to connect to the Sql Server from the same development machine by registering it in Sql Server Enterprise Manager...Is it possible to register SQL Express through Enterprise Manager?

When registering the SQL Express DB in Enterprise Manager I tried both just the (IP Address) of the server and the (IP Address\SQLExpress) as the server/host but I am getting the following errors from enterprise manager:

Just the (IP Address) as the server/host:

Invalid Connection.

ConnectionOpen( Invalid Instance())

(IP Address\SQLEXPRESS) as the server/host:

Sql Server does not exist or access denied. ConnectOpen(Connect()).

Any idea why I can’t register/mount the instance remotely in Enterprise Manager

but I can in Sql Server Management Studio Express?

Thanks,

Greg

You can not use the Enterprise management tools with sql 2005, it is only for sql 2000 and below. The connection layer and management objects are different, but the SQL 2005 Management tools can read the lower version systems. Doing this you will notice that some functions can not be completed on the lower versions due to the differences in connections. For example you can not create a new maintenance plan in the sql 2005 tools to work on sql 2000, but you can edit it after it has been created using the old sql enterprise manager.

Remotely Register SQL Server 2005 Express in Enterprise Manager

I have SQL Server 2005 Express installed on a windows server 2003 standard edition. I have configured the windows firewall to allow exceptions for sqlservr.exe and sqlbrowser.exe. I have enabled remote and local connections using tcp/ip & Named Pipes through the Sql Server Surface Area Connection utility. I am able to telnet into the server with: telnet <server ip> <1433>.

Here is the strange part: I am able to connect to the Sql Server remotely from a development machine via Sql Server Management Studio Express, but I am unable to connect to the Sql Server from the same development machine by registering it in Sql Server Enterprise Manager...Is it possible to register SQL Express through Enterprise Manager?

When registering the SQL Express DB in Enterprise Manager I tried both just the (IP Address) of the server and the (IP Address\SQLExpress) as the server/host but I am getting the following errors from enterprise manager:

Just the (IP Address) as the server/host:

Invalid Connection.

ConnectionOpen( Invalid Instance())

(IP Address\SQLEXPRESS) as the server/host:

Sql Server does not exist or access denied. ConnectOpen(Connect()).

Any idea why I can’t register/mount the instance remotely in Enterprise Manager

but I can in Sql Server Management Studio Express?

Thanks,

Greg

You will not be able to register a sql2k5 on EM. EM uses sql2k dmo which can't be used to manage sql2k5.

You will have to use sql2k5 mgmt tool to manage sqlexpress/sql2k5 instances.|||

Hi OJ,

Thanks for the reply, I was afraid this was going to be the case. Well so here is the follow up to my question.

I am using Sql Server Management Studio Express (SSMSE)...so will I be able to connect/register a sql2k server to SSMSE?

Basically I want to export the data from my sql2K DB into my sql2k5 express DB so will I be able to do that with SSMSE or will I need the full version of Sql Server Management Studio?

Thanks,

Greg

|||I haven't explicitly looked at ssmse. However, I believe it uses smo. Thus, it's capable to connecting to sql2k and manage it.sql

remote server and local server - distributed queries?

I have a remote server that I'm able to successfully register on a local sql
2000 server through EntMgr, and make successful selects on both remote and
local server databases via odbc.
Here's the question - Can I have a local server with some database/tables, a
remote server with some database2/tables, and make a single select statement
using table relationships from each? Without having to use DTS to make
imports/exports into the local server's database?
It seems that the connection object is specific to a server, but is there a
way to handle the reference to the remote server's database through a
database in the local server so that the connection object thinks
everything's local and can remain one-database-server-specific?
Sorry if I've communicated this poorly. I'd appreciate any responses.
Yes...you can do this.
A query can include tables on a linked server by using 4
part naming conventions:
server.database(or catalog).owner(or schema).table
You can also use some of the other distributed query
functions such as Openquery to do this.
-Sue
On Thu, 10 Feb 2005 08:55:03 -0800, janetb
<janetb@.discussions.microsoft.com> wrote:

>I have a remote server that I'm able to successfully register on a local sql
>2000 server through EntMgr, and make successful selects on both remote and
>local server databases via odbc.
>Here's the question - Can I have a local server with some database/tables, a
>remote server with some database2/tables, and make a single select statement
>using table relationships from each? Without having to use DTS to make
>imports/exports into the local server's database?
>It seems that the connection object is specific to a server, but is there a
>way to handle the reference to the remote server's database through a
>database in the local server so that the connection object thinks
>everything's local and can remain one-database-server-specific?
>Sorry if I've communicated this poorly. I'd appreciate any responses.

remote server and local server - distributed queries?

I have a remote server that I'm able to successfully register on a local sql
2000 server through EntMgr, and make successful selects on both remote and
local server databases via odbc.
Here's the question - Can I have a local server with some database/tables, a
remote server with some database2/tables, and make a single select statement
using table relationships from each? Without having to use DTS to make
imports/exports into the local server's database?
It seems that the connection object is specific to a server, but is there a
way to handle the reference to the remote server's database through a
database in the local server so that the connection object thinks
everything's local and can remain one-database-server-specific?
Sorry if I've communicated this poorly. I'd appreciate any responses.Yes...you can do this.
A query can include tables on a linked server by using 4
part naming conventions:
server.database(or catalog).owner(or schema).table
You can also use some of the other distributed query
functions such as Openquery to do this.
-Sue
On Thu, 10 Feb 2005 08:55:03 -0800, janetb
<janetb@.discussions.microsoft.com> wrote:

>I have a remote server that I'm able to successfully register on a local sq
l
>2000 server through EntMgr, and make successful selects on both remote and
>local server databases via odbc.
>Here's the question - Can I have a local server with some database/tables,
a
>remote server with some database2/tables, and make a single select statemen
t
>using table relationships from each? Without having to use DTS to make
>imports/exports into the local server's database?
>It seems that the connection object is specific to a server, but is there a
>way to handle the reference to the remote server's database through a
>database in the local server so that the connection object thinks
>everything's local and can remain one-database-server-specific?
>Sorry if I've communicated this poorly. I'd appreciate any responses.

Remote instance not listed in Available Servers in Enterprise Manager

When using the register available servers in Enterprise Manager, the
named instances on a remote machine are not listed. The unnamed
instance is listed and will register successfully.
I have tried manually typing the names of the remote NAMED instances;
then tried to authenticate and get the message "SQL server does not
exist or access denied".
Local machine; SQL Server 2000 SP4 (Developer Edition) installed.
2 Instances
Unnamed
DEV\DB1
On the remote machine SQL Server 2000 (MSDE Edition) installed
3 Instances;
Unnamed
REM\DB1
REM\DB2
Both machines are on the same domain. All SQL server instances are
running.
I have also used the svrnetcn.exe tool to make sure the Named Pipes
and TCP/IP protocols are enabled. The port on the TCP/IP protocol has
been changed to 1433 on all remote instances. (both machines were
rebooted)
What else can I check ?
Thanks
D> I have also used the svrnetcn.exe tool to make sure the Named Pipes
> and TCP/IP protocols are enabled. The port on the TCP/IP protocol has
> been changed to 1433 on all remote instances. (both machines were
> rebooted)
Each instance on a machine must listen on a unique TCP port. Consequently,
all of the instances on your REM machine can't be listening on the same 1433
port. Check the errorlog file for those instances for related TCP port
binding errors and change the named instance ports, if needed.
The normal configuration is that the default (unnamed) instance listens on
1433 and named instance ports are determined dynamically. When a client
connects to a named instance, it firsts gets a list of running named
instances via a UDP 1434 request and then connects to the TCP port of the
specified instance. Make sure your firewall allows TCP 1433, UDP 1434 and
TCP traffic on the named instance ports. See
http://support.microsoft.com/kb/287932
--
Hope this helps.
Dan Guzman
SQL Server MVP
"DM" <dmcb73@.gmail.com> wrote in message
news:1190197075.363594.146870@.22g2000hsm.googlegroups.com...
> When using the register available servers in Enterprise Manager, the
> named instances on a remote machine are not listed. The unnamed
> instance is listed and will register successfully.
> I have tried manually typing the names of the remote NAMED instances;
> then tried to authenticate and get the message "SQL server does not
> exist or access denied".
> Local machine; SQL Server 2000 SP4 (Developer Edition) installed.
> 2 Instances
> Unnamed
> DEV\DB1
> On the remote machine SQL Server 2000 (MSDE Edition) installed
> 3 Instances;
> Unnamed
> REM\DB1
> REM\DB2
> Both machines are on the same domain. All SQL server instances are
> running.
> I have also used the svrnetcn.exe tool to make sure the Named Pipes
> and TCP/IP protocols are enabled. The port on the TCP/IP protocol has
> been changed to 1433 on all remote instances. (both machines were
> rebooted)
> What else can I check ?
> Thanks
> D
>

Remote Connection Problems

I am not able to register a remote server and connect to
it currently without going through this process:
1. Open "My Network" and click on "Entire Network"
2. Search for the SQL Server by host and domain name (i.e.
host.domain.com)
3. Sign in with a valid username and password
4. Connect to the SQL Server through MMC
Does anyone know why I need to establish the Windows
Authentication first? Shouldn't I be able to connect with
just SQL Authentication?Hi Shannon,
For Windows Authentication, SQL Server takes your current Windows user
details. That's useful if you are in the same domain. Sounds like you aren't
in the same domain and Windows is establishing a new set of credentials when
you navigate to the system. Those credentials are then being used by SQL
Server.
SQL Server authentication requires separate users to be set up inside SQL
Server (ie not Windows users).
HTH,
--
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Shannon Burns" <sburns875@.hotmail.com> wrote in message
news:068101c364c2$b38e3420$a301280a@.phx.gbl...
> I am not able to register a remote server and connect to
> it currently without going through this process:
> 1. Open "My Network" and click on "Entire Network"
> 2. Search for the SQL Server by host and domain name (i.e.
> host.domain.com)
> 3. Sign in with a valid username and password
> 4. Connect to the SQL Server through MMC
> Does anyone know why I need to establish the Windows
> Authentication first? Shouldn't I be able to connect with
> just SQL Authentication?