January 5, 2009 at 6:34 pm
Hi,
I have encountered below issue many times
1. I have installed SQL Server 2005 named instance(Developer edition 64 bit) and applied SP2.
2 Trying to install 2nd named instance, Iam getting the following error:
SQL Server Setup has encountered the following problem: [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
And If I Install first named instance, do not apply SP2. Then second named instance and apply SP2 for both instances.
In this case it works fine. And if I want to install 3rd instance, again its giving me the same error:
SQL Server Setup has encountered the following problem: [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
could you please advise me about this issue.
January 6, 2009 at 7:16 am
Why don't you try by specifying the same 'sa' password tht worked with first named installation and change it later.
MJ
January 6, 2009 at 7:28 am
Or install all the instances and then upgrade them all to SP2 at once.
January 6, 2009 at 10:17 am
I used windows authentication. Installing 2 named instances and applying SP2 both at one time is working fine. After a month,If I want to install 3 rd instance, the same error occuring. Initially in the system configuration check it shows edition check warning and tells us to install SP2 after the installation. while installation, when it updating the system databases this password policy error occuring. Any idea plz?
January 6, 2009 at 10:20 am
How about use a longer password, or setup with Windows authentication only?
January 6, 2009 at 10:24 am
Are you using a password that does not conform to your Windows security configuration? Is the error message legitimate or objecting falsely to a valid password? Your posts don't indicate anything other than you receive this error. If your passwords are strong and you therefore believe that the error is a false error, report it to microsoft.
If, as one poster replied, your passwords are not up to snuff, then fix the passwords. You could always make the password the same as the windows password, when you setup the sa account.
January 6, 2009 at 12:47 pm
Mani (1/6/2009)
I used windows authentication.
doe this machine belong to a windows domain, supply more info please
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 18, 2009 at 11:47 am
Hi,
I did not solve this issue so far. I want to make sure that the password, we need to give in the setup installation page is Servis Account->Use a domain user account(See the attachment)
User name:ABC
Password:length = 10 characters(uppercase Letter,@,lowercase letter,lowercase letter,numric number,lowercase letter,$,lowercase letter,uppercase Letter,@)
Domain:XYZ
This is the place where we need to give strong password that we are discussing?
But with this password I have no problem with the first instance installation. Iam using this same password for second instance also, But getting the password pocily error.
I found a work around like below and its working. But my question is Every body has the same problem while installing second instance? what will be the impact of doing this work around? plz advice me...
A workaround solution has been discovered, in relation to this Microsoft KB (Knowledge Base) Article : Error message in the SQL Server Error log file after you upgrade SQL Server 2000 to SQL Server 2005 on a server that is running Windows Server 2003: "Unable to update password policy" – http://support.microsoft.com/kb/936892/en-us.Which provides us with the information that this Trace Flag (-T4606) can be used to bypass the Windows Server 2003 Local GPO Password Policy requirements for a SQL Server 2005 Installation. This Trace Flag is added into the Windows Server 2003 System Registry before any subsequent Instances of SQL Server 2005 (whether that be 2, 3, 4, 5, 6 etc) commence, it’s entered into this Registry Key Hive : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\MSSQLServer\Parameters
Where the ‘x’ represents the actual numerical increment to the SQL Server 2005 Multi-Instance Environment.
Thanks in Advance.
February 20, 2009 at 5:32 pm
SQL Server Setup has encountered the following problem: [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
Sql server Setup is looking the password we are giving at the setup page called:
Service Account
Service Accounts define which accounts to login
Customize for each service Account
Service
Drop down
Use the built-in system account dropdown
Use a domain user account
Username
password
domain
Iam using BOLDED Option. So this is where setup is telling that the password is not meeting windows policy requirements? or any other place?
But again with same password iam able to install the 1st instance but getting password error for 2nd instance installation?
Regards
Mani
February 21, 2009 at 11:03 am
Hi,
Could you please shed some light on this topic.I spoke to our system admin regarding this password issue and he is confident that the password meets the windows policy.Before opening a support case with Microsoft, I would like to hear some solution from SQL gurus.And also comments about the work around we are following which I mentioned earlier as below
A workaround solution has been discovered, in relation to this Microsoft KB (Knowledge Base) Article : Error message in the SQL Server Error log file after you upgrade SQL Server 2000 to SQL Server 2005 on a server that is running Windows Server 2003: "Unable to update password policy" – http://support.microsoft.com/kb/936892/en-us.Which provides us with the information that this Trace Flag (-T4606) can be used to bypass the Windows Server 2003 Local GPO Password Policy requirements for a SQL Server 2005 Installation. This Trace Flag is added into the Windows Server 2003 System Registry before any subsequent Instances of SQL Server 2005 (whether that be 2, 3, 4, 5, 6 etc) commence, it’s entered into this Registry Key Hive : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\MSSQLServer\Parameters
Where the ‘x’ represents the actual numerical increment to the SQL Server 2005 Multi-Instance Environment.
Thanks
Mani
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply