![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, I am sure that someone has managed to do this. We have a 64_bit Clustered SQL2005 SP2 build 3175 server that we created as Latin1_General_Bin. We want to change it to the North American default but keep getting errors. The latest was: - SQL Server Setup is unable to run on this node as it is unavailable due to a SCC failure or other reason SQL Server Setup is unable to run. Either the owning node or all nodes that are currently part of the virtual server are not available. Review any SCC failures and validate that all nodes are online. Can someone help before we uninstall? Will we have problems if we uninstall? Thanks Chris |
#3
| |||
| |||
|
|
Ureka. We did it. We found that the registry key value as to where the install came from was different on the two nodes and we were using the sa password for the adminpassword instead of the Windows account we installed with. The build still shows 3200, where we had got to, even though BOL seems to think that this may not be right. It mentioned about having to re-apply the service packs and hotfix builds. Chris "Chris Wood" <anonymous (AT) microsoft (DOT) com> wrote in message news:uWLbw$EOIHA.2376 (AT) TK2MSFTNGP02 (DOT) phx.gbl... Hi, I am sure that someone has managed to do this. We have a 64_bit Clustered SQL2005 SP2 build 3175 server that we created as Latin1_General_Bin. We want to change it to the North American default but keep getting errors. The latest was: - SQL Server Setup is unable to run on this node as it is unavailable due to a SCC failure or other reason SQL Server Setup is unable to run. Either the owning node or all nodes that are currently part of the virtual server are not available. Review any SCC failures and validate that all nodes are online. Can someone help before we uninstall? Will we have problems if we uninstall? Thanks Chris |
#4
| |||
| |||
|
|
BOL is correct. The binaries on all the nodes are build 3200, but likely the procedures on Master (and possibly the resource database) are still at RTM. Reapply all service packs and hotfix/cumulative updates to guarantee binaries and data elements are all in sync. -- Geoff N. Hiten Senior SQL Infrastructure Consultant Microsoft SQL Server MVP "Chris Wood" <anonymous (AT) microsoft (DOT) com> wrote in message news:u0QWCrFOIHA.4272 (AT) TK2MSFTNGP06 (DOT) phx.gbl... Ureka. We did it. We found that the registry key value as to where the install came from was different on the two nodes and we were using the sa password for the adminpassword instead of the Windows account we installed with. The build still shows 3200, where we had got to, even though BOL seems to think that this may not be right. It mentioned about having to re-apply the service packs and hotfix builds. Chris "Chris Wood" <anonymous (AT) microsoft (DOT) com> wrote in message news:uWLbw$EOIHA.2376 (AT) TK2MSFTNGP02 (DOT) phx.gbl... Hi, I am sure that someone has managed to do this. We have a 64_bit Clustered SQL2005 SP2 build 3175 server that we created as Latin1_General_Bin. We want to change it to the North American default but keep getting errors. The latest was: - SQL Server Setup is unable to run on this node as it is unavailable due to a SCC failure or other reason SQL Server Setup is unable to run. Either the owning node or all nodes that are currently part of the virtual server are not available. Review any SCC failures and validate that all nodes are online. Can someone help before we uninstall? Will we have problems if we uninstall? Thanks Chris |
![]() |
| Thread Tools | |
| Display Modes | |
| |