were reported.
The instance is listed in the computer's services, and it is running.
However, neither the computer name nor the new MSDE instance is listed in
the SQL Server Service Manager (although an instance on a networked computer
is listed). And I cannot connect via osql.
Any suggestions?
hi Paul,
Paul Pedersen wrote:
> I installed a named instance of MSDE SP4. It seemed to go OK, and no
> errors were reported.
> The instance is listed in the computer's services, and it is running.
> However, neither the computer name nor the new MSDE instance is
> listed in the SQL Server Service Manager (although an instance on a
> networked computer is listed). And I cannot connect via osql.
> Any suggestions?
if you can not connect from remote client, it can be depending on disabled
network protocols (default for MSDE installation, you can bypass at install
time providing the DISABLENETWORKPROTOCOLS=0 paramenter or later, at run
time, using the Server Network Utility [svrnetcn.exe] to enable the
desired/required network protocol) or, for instance, firewall/network
problems (Windows XP sp2 Firewall requires to provide an exception for the
service or to the port)..
as you are reporting the SQL Server Service Manager does not list the
instances, I'd guess it's becouse the very first scenario
(http://support.microsoft.com/default...b;EN-US;814132)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||That did the trick. Thank you!
Is there some reason that disabling the protocols is the default? It seems
to me that without that, MSDE is completely unusable. Like I said before, I
couldn't even get osql to connect. Maybe that's a different problem.
One note: the Server Network Utility says that changes will take effect
after the service is restarted, but restarting MSDE didn't make it work. I
had to reboot the computer
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hjoumFh9q50U1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> if you can not connect from remote client, it can be depending on disabled
> network protocols (default for MSDE installation, you can bypass at
> install time providing the DISABLENETWORKPROTOCOLS=0 paramenter or later,
> at run time, using the Server Network Utility [svrnetcn.exe] to enable the
> desired/required network protocol) or, for instance, firewall/network
> problems (Windows XP sp2 Firewall requires to provide an exception for the
> service or to the port)..
> as you are reporting the SQL Server Service Manager does not list the
> instances, I'd guess it's becouse the very first scenario
> (http://support.microsoft.com/default...b;EN-US;814132)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Paul,
Paul Pedersen wrote:
> That did the trick. Thank you!
> Is there some reason that disabling the protocols is the default? It
> seems to me that without that, MSDE is completely unusable. Like I
> said before, I couldn't even get osql to connect. Maybe that's a
> different problem.
actually not... Microsoft provided a setup that should protect all "passive"
users from external malicious attacks (think of Slammer and the like) only
enabling trusted WinNT connections and disabling network protocols ...
and this is not a bad idea... always give the least required privilege
pattern :D:D
> One note: the Server Network Utility says that changes will take
> effect after the service is restarted, but restarting MSDE didn't
> make it work. I had to reboot the computer
stopping and restarding the service is usually enonght thought...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks again.
It took a fair amount of trial before I realized that to connect to a named
MSDE instance with osql, you have to preface the name with server\, even if
it's on the same machine.
Only one problem left. In testing, I uninstalled and reinstalled with
DISABLENETWORKPROTOCOLS=0. But the instance does not show up on the network.
In other words, I installed MSDE on Machine A. The Service Manager on
Machine A can see its own server, plus an instance of SQL Server on Machine
B. Machine B can see its own SQL Server instance, but cannot see the MSDE
instance on Machine A.
On Machine A, the Network Utility says the tcp/ip default port is 1059 (must
be some default, because I did not set it), and Hide Server is not checked.
Do you have suggestions about this?
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hk1c1Fhii6nU1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> actually not... Microsoft provided a setup that should protect all
> "passive" users from external malicious attacks (think of Slammer and the
> like) only enabling trusted WinNT connections and disabling network
> protocols ...
> and this is not a bad idea... always give the least required privilege
> pattern :D:D
>
> stopping and restarding the service is usually enonght thought...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Paul,
Paul Pedersen wrote:
> On Machine A, the Network Utility says the tcp/ip default port is
> 1059 (must be some default, because I did not set it), and Hide
> Server is not checked.
it's not a default... Microsoft only got 1 unique TCP/IP port for SQL Server
assigned by IANA, port TCP/IP 1433... but named instances never listen to
that port that is "reserved" for default instances... so Microsoft embedded
an additional service in order to allow dynamic ports assignemen/resolution
for named instance, and the MDAC stack had to be modified as well to
integrate this feature (MDAC 2.6 and above)
for named instance you have 2 options... dynamic (default) or fixed static
port assignement..
loosely speaking, for dynamic port, when the specified instance starts, it
always searches for an unused port (actually it always uses the very same
port, if free)... the SQL Server Resolution Service, listening on UDP 1434
port, intercepts all remote connections to the instances, asks the instance
for it's used port, and redirects all connections to that specific port,
adding some little overhead to the traffic...
again, very very loosely speaking, the client makes a query, which is
reloaded by the MDAC stack to the appropriate network protocol [we are
talking about TCP/IP], that intiates the connection over a random tcp port
greater than 1024 to destination port; the listener service is the first
hand-shaker and intercepts the foreign call, queries the instance for it's
used port and negotiates a TCP/IP port for the 2 end points...
for a static assigned port, the listener on UDP 1434 port is not required,
but you have to map a server alias on each remote client pointing to the
correct fixed assigned port.. and again, the client intiates the connection
over a random tcp port greater than 1024 to destination port (say 1059). The
Subscriber should be allowed to make inbound (ANY) connections to
{say 1059} on a random port. The Publisher should be allowed to establish
outgoing connections to the subscriber from (ANY) to {say 1059}...
> Do you have suggestions about this?
>
WinXP sp2 or personal firewall?
the Windows XP sp2 integrated Firewall closes all ports... you have to add
an exception for that in order to allow external access,
http://support.microsoft.com/default.aspx?scid=kb;[LN];841251 ,
http://support.microsoft.com/?id=841249 ,
http://support.microsoft.com/default.aspx?kbid=839980
please excuse my poor english... hope it's understandable
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.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
I am having the same problem, but I am using Enterprise Manager on the same
machine where the named instance is running. What can I do, please?!
TIA
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hjoumFh9q50U1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> if you can not connect from remote client, it can be depending on disabled
> network protocols (default for MSDE installation, you can bypass at
install
> time providing the DISABLENETWORKPROTOCOLS=0 paramenter or later, at run
> time, using the Server Network Utility [svrnetcn.exe] to enable the
> desired/required network protocol) or, for instance, firewall/network
> problems (Windows XP sp2 Firewall requires to provide an exception for the
> service or to the port)..
> as you are reporting the SQL Server Service Manager does not list the
> instances, I'd guess it's becouse the very first scenario
> (http://support.microsoft.com/default...b;EN-US;814132)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||Sorry, I forgot to mention that I am using win2000p for dev and win2000
server for production
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hjoumFh9q50U1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> if you can not connect from remote client, it can be depending on disabled
> network protocols (default for MSDE installation, you can bypass at
install
> time providing the DISABLENETWORKPROTOCOLS=0 paramenter or later, at run
> time, using the Server Network Utility [svrnetcn.exe] to enable the
> desired/required network protocol) or, for instance, firewall/network
> problems (Windows XP sp2 Firewall requires to provide an exception for the
> service or to the port)..
> as you are reporting the SQL Server Service Manager does not list the
> instances, I'd guess it's becouse the very first scenario
> (http://support.microsoft.com/default...b;EN-US;814132)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi,
dl wrote:
> Hi Andrea
> I am having the same problem, but I am using Enterprise Manager on
> the same machine where the named instance is running. What can I do,
> please?!
> TIA
what kind of exception are you reported with?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you for your help. Your English is fine.
I don't know why, but it started working. I didn't change anything. But if
it's working, I won't complain.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hldmoFhkqsrU1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> it's not a default... Microsoft only got 1 unique TCP/IP port for SQL
> Server assigned by IANA, port TCP/IP 1433... but named instances never
> listen to that port that is "reserved" for default instances... so
> Microsoft embedded an additional service in order to allow dynamic ports
> assignemen/resolution for named instance, and the MDAC stack had to be
> modified as well to integrate this feature (MDAC 2.6 and above)
> for named instance you have 2 options... dynamic (default) or fixed static
> port assignement..
> loosely speaking, for dynamic port, when the specified instance starts, it
> always searches for an unused port (actually it always uses the very same
> port, if free)... the SQL Server Resolution Service, listening on UDP 1434
> port, intercepts all remote connections to the instances, asks the
> instance for it's used port, and redirects all connections to that
> specific port, adding some little overhead to the traffic...
> again, very very loosely speaking, the client makes a query, which is
> reloaded by the MDAC stack to the appropriate network protocol [we are
> talking about TCP/IP], that intiates the connection over a random tcp port
> greater than 1024 to destination port; the listener service is the first
> hand-shaker and intercepts the foreign call, queries the instance for it's
> used port and negotiates a TCP/IP port for the 2 end points...
> for a static assigned port, the listener on UDP 1434 port is not required,
> but you have to map a server alias on each remote client pointing to the
> correct fixed assigned port.. and again, the client intiates the
> connection over a random tcp port greater than 1024 to destination port
> (say 1059). The Subscriber should be allowed to make inbound (ANY)
> connections to
> {say 1059} on a random port. The Publisher should be allowed to establish
> outgoing connections to the subscriber from (ANY) to {say 1059}...
>
> WinXP sp2 or personal firewall?
> the Windows XP sp2 integrated Firewall closes all ports... you have to add
> an exception for that in order to allow external access,
> http://support.microsoft.com/default.aspx?scid=kb;[LN];841251 ,
> http://support.microsoft.com/?id=841249 ,
> http://support.microsoft.com/default.aspx?kbid=839980
> please excuse my poor english... hope it's understandable
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.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