I'm trying to register an instance of MSDE on a remote machine using EM on my desktop. The remote machine has 2
named instances of MSDE running. I am able to register 1 instance with no problems. I had to register it using
"RemoteServer1\InstanceName" rather than just the remote machines name.
For the life of me I can not get the other instance to register. I get the "SQL Server does not exist or access
denied" error. I've tried just registering the 2nd instance without the first with the same results. I can see
no difference in the way either of the 2 instances were set up or in their properties. I am a machine admin on
the remote machine and am connecting using Windows Auth.
What am I missing and how can I register that 2nd instance?
Thank you.
gdr
Gary D. Rezek
University Networking Systems and Services
South Dakota State University
hi Gary,
Gary D. Rezek wrote:
> Hi All,
> I'm trying to register an instance of MSDE on a remote machine using
> EM on my desktop. The remote machine has 2 named instances of MSDE
> running. I am able to register 1 instance with no problems. I had to
> register it using "RemoteServer1\InstanceName" rather than just the
> remote machines name.
this is normal as a named instance full qualified name is
ComputerName\InstanceName...
> For the life of me I can not get the other instance to register. I
> get the "SQL Server does not exist or access denied" error. I've
> tried just registering the 2nd instance without the first with the
> same results. I can see no difference in the way either of the 2
> instances were set up or in their properties. I am a machine admin on
> the remote machine and am connecting using Windows Auth. What am I
> missing and how can I register that 2nd instance?
at least 1 difference must be present... the name... MSDE/SQL Server 2000
can be installed as a default instance or a named instance... but only a
default instance can be present, wit up to other 15 named instances per
computer...
as you already saw, a default instance is available as ComputerName, where a
named instance will be as ComputerName\InstanceName...
you can inspect your (remote) services for MSSQLSERVER and
MSSQL$InstanceName to see what is going on...
MSDE installs by default disabling network protocols, thus not allowing
remote connections... please verify using the Server Network Utiliy
(svrnetcn.exe) that the "failing" instance has enabled network protocols...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea,
Thanks for your answer. It eventually led me to http://tinyurl.com/8q95s this post. In that post I found this
quote...
"You need to look for a line in the error log which states:
"SQL server listening on TCP, Shared Memory, Named Pipes.
"If you only have Shared Memory on this list, then only local connections are allowed."
In the instance I have been trying to connect, Shared Memory is the only thing listed in the errorlog, so no
TCP/IP or Named Pipes. I asked the individual who is responsible for the application which created this instance
of MSDE (and also the one who asked me WHY can't he connect through EM), I learned that this is the way it
should be. :^/ I've worked with MSDE very, very little, but I still should have looked at the ErrorLog to
begin with.
Thank you very much for your help
gdr
Gary D. Rezek
University Networking Systems and Services
South Dakota State University
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message news:3jg2rjFpnmhnU1@.individual.net...
> hi Gary,
> Gary D. Rezek wrote:
> this is normal as a named instance full qualified name is ComputerName\InstanceName...
>
> at least 1 difference must be present... the name... MSDE/SQL Server 2000 can be installed as a default
> instance or a named instance... but only a default instance can be present, wit up to other 15 named instances
> per computer...
> as you already saw, a default instance is available as ComputerName, where a named instance will be as
> ComputerName\InstanceName...
> you can inspect your (remote) services for MSSQLSERVER and MSSQL$InstanceName to see what is going on...
> MSDE installs by default disabling network protocols, thus not allowing remote connections... please verify
> using the Server Network Utiliy (svrnetcn.exe) that the "failing" instance has enabled network protocols...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual interface)
> -- remove DMO to reply
>
|||h Gary,
Gary D. Rezek wrote:
> Hi Andrea,
> Thanks for your answer. It eventually led me to
> http://tinyurl.com/8q95s this post. In that post I found this quote...
> "You need to look for a line in the error log which states:
> "SQL server listening on TCP, Shared Memory, Named Pipes.
> "If you only have Shared Memory on this list, then only local
> connections are allowed."
you always have to verify (on the server using Server Network Utility
[svrnetcn.exe] and on the client using Client Network Utility
[cliconfg.exe]) that a common network protocol is available for the client
and the server to dialog...
> In the instance I have been trying to connect, Shared Memory is the
> only thing listed in the errorlog, so no TCP/IP or Named Pipes. I
> asked the individual who is responsible for the application which
> created this instance of MSDE (and also the one who asked me WHY
> can't he connect through EM), I learned that this is the way it
> should be. :^/
if Shared Memory is the only protocol that "must" be enabled, then no remote
connections will be available... but it can be ok in local scenarios
..MSDE will then actually be used as a local desktop database..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
No comments:
Post a Comment