July 17, 2006 at 2:19 pm
We just did an upgrade in place for seven mssql 2000 servers on 7 separate machines to sql 2005. 5 upgrades went fine and two failed. The failure happened when the upgrade process tried to start up the mssqlserver service. The error message we got was "unable to update security policy". The two failures were on VM machines(but 2 on VM machines were ok). Anybody have any experience with this or any suggestions?
July 20, 2006 at 8:00 am
This was removed by the editor as SPAM
July 20, 2006 at 9:57 am
According to Microsoft the problem is caused by a corrupted password hash for a login. They sent us a work-around as follows:
<> Start the in place upgrade normally.
<> If the setup fails at the retry screen start the SQL Server from the background using following command:
net start MSSQLSERVER /T4606
<> Then hit retry again, if this also fails ignore the error and let the setup finish.
<> After the setup install the tools manually.
<> Start the server using:
net start MSSQLSERVER /T4606
<> And then disable any "enforce password policy" option from the logins manually.
<> After this the server should start normally.
The trace flag 4606 disables password checking at startup
July 24, 2006 at 12:34 am
Thanks for the feedback.
in this case, you didn't get the answer overhere, but now others will !
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply