March 10, 2009 at 11:14 pm
Hello,
We are upgrading sql server 2000 default instance to sql server 2005 using in-place upgrade.Upgrade is failing with this error message while updating the "instmsdb.sql" in the setup wizard.
The error is as below:
[Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet Windows policy requirements because it is too short.. To continue, correct the problem, and then run
SQL Server Setup again
I went through this link http://www.sqlservercentral.com/Forums/Topic669605-146-1.aspx , discussing the same error and I did the registry hive as below.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\Parameters created string value SQLArg3->modify and entered the value -T4606.
But it is not working.As soon as I got above error, I went to the registry and look for the regestry hive that I created, surprisingly,it got deleted.
Suggest me where exactly i need to create this registry hive for the below scenario.
1)upgrading sql server 2000 default instance.I attached the screen shot,please tell me where exacly I need to create registry hive so that the upgrade will run smoothly.
In the screen shot, I created the registry hive Microsoft SQL Server\MSSQL.1\MSSQLServer\Parameters created string value SQLArg3. Is this right location to create the registry hive or something else?
thanx
March 11, 2009 at 1:28 am
Does your SA password match your domain password policy ?
(maybe even change it temporary during the upgrade only)
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
March 11, 2009 at 1:53 am
SA password is the place where we will give in the Service account page right? If this is the one you are asking, then Yes SA password following our domain policies.I have attached screen shot at http://www.sqlservercentral.com/Forums/Topic672864-146-1.aspx. You are talking about this password right?
thanks
March 11, 2009 at 3:02 am
No. SA is the sql user which is sysadmin !
It is not the service account!
Do you have your sqlinstance in Mixed authentication mode ?
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
March 11, 2009 at 10:55 am
We are using WIndows authentication only.
Thanks
March 12, 2009 at 3:04 pm
Could you give me some more info regarding this issue
March 13, 2009 at 3:10 am
Can you try to provide a valid password for the sqluser sa
IMO, even if sql auth is not actively in use for the instance, the upgrade will validate the password for sa and it has to match the domain policy !
My guess is you sa password hasn't been set at all, so if anyone switches your instance to mixed mode, that would cause a serious security risk because it still has the default password.
Use Query analyser or EM (as sysadmin)
EXEC sp_password @loginame = 'sa' , @new = 'newt0p$ecretp@$$w0rd'
If that doesn't work in "windows only" authentication mode,
I would try to switch it to mixed authentication, alter the sa password
and switch back to "windows only" authentication mode.
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
March 17, 2009 at 6:04 pm
The work-around is to edit the INSTMSDB.SQL script and change two instances of Yukon90_ to something more complex. In my case, I used: 1qaz@WSX3edc$RFV
MJ
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply