SQL Server Performance Forum – Threads Archive

SQL 2000 SP4 installation to Server 2003 Cluster

When attempting to install the SQL Server 2000 SP4 update to a Virtual SQL Instance on a 2003 Active/Passive Cluster I get a failure message after inputing the Remote Access account details. This Remote Access account used has Domain Admin Rights, Has all the required Local Policy Settings, is also the Owner of the SQL Services, and the Cluster Service. But still the installation fails to validate the account. All Cluster Nodes, and Resource are Active and Online.
The installation process successfully takes the correct SQL Instance Resource offline to start the installation. But then fails, as if it does not like the Remote Access Account.
Note that the account was used quite happily for cluster installation and maintenance up to SP3a. Any ideas?

Refer to the readme.html files for cluster & 2003 installations, KBAhttp://go.microsoft.com/?linkid=3316089 for reference. SP4 installation now relies on Windows Task Scheduler to do it’s work on the other nodes of the cluster. if Windows Task Scheduler is disabled or not running on the remote nodes, the hotfix install on those nodes fails, but fails very silently. Try to enable it and apply SP, then disable WTS. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

Thanks Satya.
Task Scheduler Service is disable via GPO.
So Account would not even be able to start service. Have instigated temporary change to GPO to facilitate SP4 Installation. Thank you for your prompt help.

Let us know whether it worked or not, I have used this before and it worked and I would like to be sure about my solution too. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

Yes. It worked.
Basically I work in a very clamped environment.
GPO’s and policies used to provide the most secure environemnt I can.
Therefor the schedule service, among others, is disabled, as it is not required during normal operation. Basically I moved both servers into an active directory folder location that was free from GPO’s etc. Then did a "gpoupdate /force" on the Active and Passive nodes. Then started the Task Scheduler service on all nodes. The SP4 installed OK. The nodes could then be returned to the clamped environment and "gpoupdate /force" applied to reapply the GPO’s.
(note that depending on what the GPO’s contain, it may be wise to perform a controlled reboot of the cluster) Thank you for you help. I will be posting a question about the pitfalls of moving from Active/Passive clustering to Active/Active clustering in the next few days. Hope you will be able to help with that also. Thank you Satya

THanks for your detailed explanation that can help others too.
I can help as long as I’ve experience in the topic, if not I’m happy that this forum is equipped with very knowledgable peers. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

Yes good to see a detailed explanation. You can run into the same issue on Windows 2000 if the remote registry service is not running.

]]>