Enabling Network Protocols Urgent

Hello
I installed MSDE2000 sp3a which disabled network protocols is there a way i can enable them without having to reinstall th
whole thin
Thanks,H
Use the Server Network Utilit
eg
"C:\Program Files\Microsoft SQL Server\80\Tools\Binn\svrnetcn.exe
JBandi

Enabling Network Protocols Urgent

Hello,
I installed MSDE2000 sp3a which disabled network protocols is there a way i
can enable them without having to reinstall the
whole thing
Thanks,HI
Use the Server Network Utility
eg:
"C:\Program Files\Microsoft SQL Server\80\Tools\Binn\svrnetcn.exe"
JBandi

Enabling Network Protocols Urgent

Hello,
I installed MSDE2000 sp3a which disabled network protocols is there a way i can enable them without having to reinstall the
whole thing
Thanks,
HI
Use the Server Network Utility
eg:
"C:\Program Files\Microsoft SQL Server\80\Tools\Binn\svrnetcn.exe"
JBandi

Enabling Network Protocols in MSDE 2000

Hello,
I installed MSDE 2000 it's not accepting connections from
any machine i think the network protocols got disabled is
there a way to enable them rather than installing again
MSDE installs a tool called srvnetcn.exe that can be used to configure the
network protocols of an MSDE instance. It is located in
Program Files\Microsoft SQL Server\80\Tools\Binn
Jim
"sch" <anonymous@.discussions.microsoft.com> wrote in message
news:1a4e501c41d83$c6d49b80$a101280a@.phx.gbl...
> Hello,
> I installed MSDE 2000 it's not accepting connections from
> any machine i think the network protocols got disabled is
> there a way to enable them rather than installing again
|||Hi Jim,
Actually svrnetcn.exe.
HTH,
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jim Young" <thorium48@.hotmail.com> wrote in message
news:OYHIoBaHEHA.2300@.tk2msftngp13.phx.gbl...
> MSDE installs a tool called srvnetcn.exe that can be used to configure the
> network protocols of an MSDE instance. It is located in
> Program Files\Microsoft SQL Server\80\Tools\Binn
> Jim
>
> "sch" <anonymous@.discussions.microsoft.com> wrote in message
> news:1a4e501c41d83$c6d49b80$a101280a@.phx.gbl...
>
|||Thanks Very Much Guys!
|||
>--Original Message--
>MSDE installs a tool called srvnetcn.exe that can be
used to configure the
>network protocols of an MSDE instance. It is located in
>Program Files\Microsoft SQL Server\80\Tools\Binn
>Jim
>
>"sch" <anonymous@.discussions.microsoft.com> wrote in
message[color=darkblue]
>news:1a4e501c41d83$c6d49b80$a101280a@.phx.gbl...
from[color=darkblue]
is
>
>.
>works great, thanks Jim

enabled/disabled protocols for an msde instance

Hi folks,
Wondering if someone could help me out with an msde/windows sp2 problem.
Upon installing sp2, the network protocols for my msde instance become
disabled: Sm, Np, Tcp, Via. Is there a command line syntax I can use to
re-enable these network protocols? Or is there a windows interface to enable
them? basically my msde instance is now standalone, no other workstations
can talk to that sql instance. I can't install sp3 for msde because the
manufcaturer used merge modules (bleh!).
Any help would be greatly appreciated.
Thanks,
S. Purkiss
sheldon@.REMOVETHISthedoctorcompany.com
hi,
"S Purkiss" <shel@.shel.com> ha scritto nel messaggio
news:w7idnY9fmfsFnOLcRVn-rA@.rogers.com
> Hi folks,
> Wondering if someone could help me out with an msde/windows sp2
> problem.
> Upon installing sp2, the network protocols for my msde instance become
> disabled: Sm, Np, Tcp, Via. Is there a command line syntax I can
> use to re-enable these network protocols? Or is there a windows
> interface to enable them? basically my msde instance is now
> standalone, no other workstations can talk to that sql instance. I
> can't install sp3 for msde because the manufcaturer used merge
> modules (bleh!).
> Any help would be greatly appreciated.
please run Server Network Utility (svrnetcn.exe) and re-enable the desired
protocol...
with MSDE sp2 level you are exposed at Slammer/Saphire troubles, which have
ben solved with service pack 3 - 3/a..
lot of security problems has been addressed to with that sp, so please
"force" your ISV to ship sp3, as it's been out for quite 1 year, and it
should already had enougth time to test and ship it...
my $0.02
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

enable TCPIP Protocols by script

How do you enable TCPIP in Protocols for Network Config for the sql server
2005 and for all the specific IP addressses via T-SQL script.> How do you enable TCPIP in Protocols for Network Config for the sql server
> 2005 and for all the specific IP addressses via T-SQL script.
I do not know for T-SQL, but I guess you can do it with SMO or WMI. Here is
a VBScript script that uses WMI to enlist the protoclos and enable named
Pipes:
' enum protocols and show status
set wmi =
GetObject("WINMGMTS:\\. \root\Microsoft\SqlServer\ComputerManage
ment")
for each prop in wmi.ExecQuery("select * " & _
"from ServerNetworkProtocol " & _
"where InstanceName = 'mssqlserver'")
WScript.Echo prop.ProtocolName & " - " & _
prop.ProtocolDisplayName & " " & _
prop.Enabled
next
' enable named pipes
for each changeprop in wmi.ExecQuery("select * " & _
"from ServerNetworkProtocol " & _
"where InstanceName = 'mssqlserver' and " & _
"ProtocolName = 'Np'")
changeprop.SetEnable()
next
Dejan Sarka
http://www.solidqualitylearning.com/blogs/|||BTW, you have to restart the service if you want changes in network
protocols to take effect.
Dejan Sarka
http://www.solidqualitylearning.com/blogs/
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in
message news:eRGorcHRHHA.412@.TK2MSFTNGP02.phx.gbl...
> I do not know for T-SQL, but I guess you can do it with SMO or WMI. Here
> is a VBScript script that uses WMI to enlist the protoclos and enable
> named Pipes:
> ' enum protocols and show status
> set wmi =
> GetObject("WINMGMTS:\\. \root\Microsoft\SqlServer\ComputerManage
ment")
> for each prop in wmi.ExecQuery("select * " & _
> "from ServerNetworkProtocol " & _
> "where InstanceName = 'mssqlserver'")
> WScript.Echo prop.ProtocolName & " - " & _
> prop.ProtocolDisplayName & " " & _
> prop.Enabled
> next
> ' enable named pipes
> for each changeprop in wmi.ExecQuery("select * " & _
> "from ServerNetworkProtocol " & _
> "where InstanceName = 'mssqlserver' and " & _
> "ProtocolName = 'Np'")
> changeprop.SetEnable()
> next
>
> --
> Dejan Sarka
> http://www.solidqualitylearning.com/blogs/
>|||This does not enable the TCPIP, change the enable setting from NO to YES in
the TCP/IP properties. Do you have to do any update statement in WMI? I
haven't used WMI before. I did stop and restart my sql server.
I changed your code from Np to tcp as I think that was for named pipes not
tcp .
Any help would be gratefully received
thanks
"Dejan Sarka" wrote:

> I do not know for T-SQL, but I guess you can do it with SMO or WMI. Here i
s
> a VBScript script that uses WMI to enlist the protoclos and enable named
> Pipes:
> ' enum protocols and show status
> set wmi =
> GetObject("WINMGMTS:\\. \root\Microsoft\SqlServer\ComputerManage
ment")
> for each prop in wmi.ExecQuery("select * " & _
> "from ServerNetworkProtocol " & _
> "where InstanceName = 'mssqlserver'")
> WScript.Echo prop.ProtocolName & " - " & _
> prop.ProtocolDisplayName & " " & _
> prop.Enabled
> next
> ' enable named pipes
> for each changeprop in wmi.ExecQuery("select * " & _
> "from ServerNetworkProtocol " & _
> "where InstanceName = 'mssqlserver' and " & _
> "ProtocolName = 'Np'")
> changeprop.SetEnable()
> next
>
> --
> Dejan Sarka
> http://www.solidqualitylearning.com/blogs/
>
>

Enable Production SQL Server Express for SQLCacheDependency?

Q1: Can I just open these protocols I need (see web links below) and then close them down again after SQLCacheDependency has been enabled? Note: The website (asp.net 2.0/SQL server Express) operates OK right now with asp.net - but it does not have SQLCacheDependency enabled.

Problem: When I try to do this I keep on getting this error message:

"An error has occurred when 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."

None of these 3 commands have worked (all give the same message above):

aspnet_regsql.exe -U user1 -P pwd1 -S server1/SQLEXPRESS -d myDBName -ed
aspnet_regsql.exe -E -S server1/SQLEXPRESS -d myDBName -ed
aspnet_regsql.exe -E -S .\SqlExpress -d myDBName -ed

I am trying to run these commands via a MSTSC connection. Q2: Is that (terminal server) the problem (the "remote connection") complained of above ?

This is the command that worked on my local dev machine:

aspnet_regsql.exe -E -S .\SqlExpress -d myDBName -ed

Q3: Must I really go through the procedure "How to: Configure Express to accept remote connections" at:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277
http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

I don't really want to have SQL server accepting any connections as the last time it was listening on these ports we had so many attacks being made that it was filling up the logs!

What I can't understand is that every night the database is backed up with the following command line code (operating as a Scheduled Task):

sqlcmd -s server1/SQLEXPRESS -i MW4BAK.SQL -E

Q4: So if the server is happy receiving commands from 'sqlcmd.exe' why does it have such problems with 'aspnet_regsql.exe'

Q5: If I grouped those statements I need to setup SQLCacheDependency under a Scheduled Task would they work (as there would presumably be no remote connection then) or is it something in the nature of the connection established which allows sqlcmd.exe to work but stops aspnet_regsql.exe?

I was able to configure the database for cache dependency by just running the command with no parameters and letting the wizard take over:

aspnet_regsql.exe

But ICAN NOT enable the tables e.g.
aspnet_regsql.exe -E -S server1\SqlExpress -d myDBName -t myTable1 -et
continues to give the error message above (implying that it won't allow a remote connection).

What's the problem? Is it because I'm running the command remotely under terminal server?

|||

Apologies. I sorted it out.

The SQL instance is not called "server1/SQLEXPRESS". It is only
"server1" (on this server). So the following will work.

aspnet_regsql.exe -E -S server1 -d myDBName -ed
aspnet_regsql.exe -E -S server1 -d myDBName -t myTableName -et

etc. for each table