SQL: February 2009 Archives
Previously: Sql Server 2005 - Surface Area Configuration won't save
Just a quick update; installing Service Pack 3 (yes, I know I said SP2 in the previous post, my bad!) was a non-starter as the SP install attempted to connect to the instance and failed. The message did point me in the direction of the Sql Native Client being corrupted.
Uninstalling and reinstalling the Native Client allowed the service pack to install, allowed the local Sql Server Management Studio to connect and also allowed me to change the "allow external connections" from "Local Only" to "Local & Remote Connections" on both named pipes and TCP/IP. Unfortunately, I can't prove that this allowed external connections to succeed as I didn't have access to another machine on the network.
This morning, the machine is once again refusing to save the "external connections" settings in the Surface Area Configuration Manager, again! :( (This may have something to do with anothe person working on SSL on IIS on the box concerned though, perhaps?)
Just a quick update; installing Service Pack 3 (yes, I know I said SP2 in the previous post, my bad!) was a non-starter as the SP install attempted to connect to the instance and failed. The message did point me in the direction of the Sql Native Client being corrupted.
Uninstalling and reinstalling the Native Client allowed the service pack to install, allowed the local Sql Server Management Studio to connect and also allowed me to change the "allow external connections" from "Local Only" to "Local & Remote Connections" on both named pipes and TCP/IP. Unfortunately, I can't prove that this allowed external connections to succeed as I didn't have access to another machine on the network.
This morning, the machine is once again refusing to save the "external connections" settings in the Surface Area Configuration Manager, again! :( (This may have something to do with anothe person working on SSL on IIS on the box concerned though, perhaps?)
