March 4, 2009 at 12:49 am
Comments posted to this topic are about the item From the Real World: SQL Server 2000 SP4 Installation Failure
March 4, 2009 at 2:50 am
Hi
Thanks for your walkthrough Praveen.
After reading I have this one question :
Is it correct to summarize the article down to the claim that it was caused by someone "changing the SQL service account from services console instead of Enterprise manager". If that hadn't been done - the SP4 would have been applied fine ?
- But you listed the troubleshooting very educationally and I bet it will save other the time and hazzle 🙂
March 4, 2009 at 4:45 am
Thanks Praveen.I was too planning to upgraded one of our critcal server to sp4 . This would help me if i face similar issues.
March 4, 2009 at 8:25 am
Excellent article and explanation of this issue Praveen! We found out quickly how important it was to use EM vs. Svcs console to change the service account when we were doing domain migrations on our clusters. Thanks for sharing.
Mike K
March 4, 2009 at 9:48 am
well done. I have always distrusted 2000 clusters because MS was so picky about them. I am now using 2005 clusters and they are unproblematic except for their exclusive demand for kerberos in the domain. Again, well done.
March 4, 2009 at 5:59 pm
Nicely written.
Amit Lohia
March 4, 2009 at 9:36 pm
Praveen,
Thanks for submitting this, and it came out very well. I'm sure you're helping more than a few people with this.
March 6, 2009 at 10:06 pm
I'd say yes.. Normally it won't be the case where sql service account doesn't have permissions on its own registry key.. HKLM\Software\Microsoft\MSSQLServer..
This could have happened mainly due to wrong way of account change.
March 14, 2009 at 2:13 pm
Awesome piece of troubleshooting! Thank you for sharing.
July 20, 2009 at 11:56 am
Hey Praveen,
Superb man... Really helping ppl around U 😉
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply