We have multiple hosted clients with each in there own little domain. I'm trying to setup a single DB server to catch reporting from the remote servers. I have to do it via IP. I want to disable named pipes on the servers when I'm adding the logging script to the individual SQL Servers. Using the configuration GUI is just plain slow.
This is what I have currently to change the "Protocols for <InstanceName>" and the associated registry key.
It is failing with
-------------------------------------------------------------------------------------------------------
Error executing xp_regwrite extended stored procedure: Registry Type Invalid
-------------------------------------------------------------------------------------------------------
The other for SQL Native Client --> Client Protocols doesn't error, but the registry doesn't change either.
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
Are you sure that remoteconn isn't something out of Red Gate?
I can't find any references to it.
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Unlimited question asking, solutions, articles and more.
Jim P.
ASKER
That is exactly what I was looking for. Googling has everyone just saying ignore the NP. I have had nothing but headaches from them since the day I started doing SQL. Turning them off on five servers using the GUI is not a big deal. Doing it on 40-50+ is another animal.
I can usually build my own routines, but this one was just baffling me.
Thanks for the assistance. May all your days get brighter and brighter.
http://technet.microsoft.com/en-us/library/dd206997.aspx