Sql Server 2005 - Surface Area Configuration won't save
Has anyone ever see that?
An instance of Sql Server 2005 that I have is refusing connections with "No process is on the other end of the pipe". A bit of googling revealed that this might be because the instance was/is set to only accept local connections. Great, except for the fact that I was trying to connect locally!
Now, I tried opening up the Surface Area Configuration Manager and lo-and-behold, it's showing "Local Connections" as the only allowabe way in. Changing it to "Local and Remote" for both named pipes and TCP/IP, hitting save and restarting the instance resulted in the same error message from Sql Server Management Studio. Re-visiting the Configuration Manager, it appears that it either didn't bother to save the configuration, or it was being wiped by something.
Next thing to try: Sql Server 2005 Service Pack 2!!
An instance of Sql Server 2005 that I have is refusing connections with "No process is on the other end of the pipe". A bit of googling revealed that this might be because the instance was/is set to only accept local connections. Great, except for the fact that I was trying to connect locally!
Now, I tried opening up the Surface Area Configuration Manager and lo-and-behold, it's showing "Local Connections" as the only allowabe way in. Changing it to "Local and Remote" for both named pipes and TCP/IP, hitting save and restarting the instance resulted in the same error message from Sql Server Management Studio. Re-visiting the Configuration Manager, it appears that it either didn't bother to save the configuration, or it was being wiped by something.
Next thing to try: Sql Server 2005 Service Pack 2!!
