February 19, 2008 at 1:15 pm
has anyone come across this when installing a named instance:
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.
My setup is a windows server 2003 enterprise x64 SP 2, with SQL 2005 standard x64 sp2. I already have a default instance running without issue, but i go to create a named instance I get the above error message.
I've tried to go online to find anything on this, but no one seems to have anything on this.
any help would be greatly appreciated.
February 19, 2008 at 1:30 pm
Are you allowing mixed authentication on the named instance and setting an sa password? It sounds like you are setting up the named instance to use the Domain password policy and you are not meeting that policy in the sa password. It may even be that the default instance is setup that way and the Named instance is using that as a default setting.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
February 19, 2008 at 1:44 pm
February 19, 2008 at 3:13 pm
Thanks for the quick response.
I've tried doing the install with mixed mode using a 16 character based password as well as doing the install with windows authentication. But nothing seems to work; I always seem to get the same error message.
I came across these in my research, any one?
Error: 50000 Severity: 20 State: 127 Cannot create ##MS_AgentSigningCertificate## in msdb. INSTMSDB.SQL terminating.
Product: Microsoft SQL Server 2005 (64-bit) - Update 'Hotfix 3024 for SQL Server Database Services 2005 (64-bit) ENU (KB000000)' could not be installed. Error code 1603.
February 19, 2008 at 5:40 pm
Here ya go, I was able to get through this and I hope either one of these will work for you if you come across this issue.
A. Prepare a dos window with this command replacing your instance name for the INST2 string.
osql /E /S.\INST2 /Q"dbcc traceon(4606,-1)"
As soon as the setup display the message Installing msdb
with "C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Install\instmsdb.sql"
execute the above command.
The install should succeed.
B. Install first instance, it is installed in MSSQL.1 in the registry and folder structure. SP2 needs to already be on the default instance.
Create the registry key: HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.2\MSSQLServer\Parameters with DWORD value SQLArg3 = -T4606
Install second instance (it goes in MSSQL.2)
It succeeds as the startup parameter for SQL prevents security checking
Remove the registry key after installing SP2.
February 20, 2008 at 5:10 am
the root casue of this issue lies in instmsdb.sql....
the mentioned sql has a sample password.....(dont remeber it exactly...search for yukon it is something similar to this).
and this password is not too complex password..and in most environemnts their domian settigns would find this apssword as a week password and say this does not meet the requirement ...and the installation fails...
solution...manually change the sample password to something complex in the instmsdb.sql..it can be anything....after this the installation will be successful..i have tried this before and have done it successfully..
let me know if this works for you
thanks
February 21, 2008 at 9:24 am
For the option B.
What if I need the first instance to start with the flag set and SP2 is already installed. Is there away around that.
This little error screwed up my whole implementation last night as I was installing on a Server that had the account policies locked. I mean, why is a local SQL user checking this policy even though the user settings say that is unchecked for password policy.
I am at a standstill though. This seems to be a large enough problem that Microsoft should have fix for already. What is the hold up?
February 22, 2008 at 3:44 am
Yes i agree that MS should have fixed this issue..however with my experience in installing many of sqlserver2005 instances...i faced this issue only when i applied SP2 on SQL server 2005. i never faced this issue while installing the instance as such. And as mentioned before after little research on internet ..we were able to find a workaround by changing the password in the sql .....just in case it is a showstopper for you try my suggested solution ......thanks
August 31, 2008 at 3:24 pm
thanks alot cspangler....
your tric worked for me...I have fedup with this error. finally I installed the 2nd instance.
This error is coming when I stop the all services except Browser service.
If I stop all the services including Browser service Iam getting the error like
The setup has encountered an error while Upgrading Components. The error: -2147019873
Error message: The group or resource is not in the correct state to perform the requested operation
Do you know what is the reason for this?
And whether we need to stop or stat the browser service while installing 2nd failover instance?
Because Iam getting different errors based on the browser service started or stoped
thanks
August 31, 2008 at 10:21 pm
Yeah Samule,
How to manually change the sample password to something complex in the instmsdb.sql..
I did not understand where to find instmsdb.sql..?and do we need change this before installation.? could you plz tell me that.
In my case iam getting this password policy error for every failover instance except the 1st instance.
Is this a bug?
Thanks
March 3, 2009 at 12:51 am
Hi,
has anyone come across this when installing a named instance:
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.
Is this really a BUG? is Microsoft confirmed that this error as a BUG? please advice me Iam getting this error while installing 2nd instance.The 1st instance installation has no errors.
Please advice me whether it is a BUG or NOT? based on your suggestion, we would like to open a ticket with Microsoft ,if it really a BUG need to find the solution from MS.
Yeah cspangler, with the workaround you followed,did you get any issues in real production?can we remove the -T4606 trace flag after the installation? did microsoft has mentioned this workaround in any KB article? please give me your advice as you done with this workaround
Thanx
March 3, 2009 at 2:00 am
Mani (8/31/2008)
Yeah Samule,How to manually change the sample password to something complex in the instmsdb.sql..
I did not understand where to find instmsdb.sql..?and do we need change this before installation.? could you plz tell me that.
In my case iam getting this password policy error for every failover instance except the 1st instance.
Is this a bug?
Thanks
Open the "instmsdb.sql" file and search for "Yukon90_". Then change "Yukon90_" with some complex password.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
March 3, 2009 at 12:01 pm
What will be the real problem? is the the workaround safe?
March 3, 2009 at 12:12 pm
well, you have two main things you can do.
1. look for instmsdb.sql, within the default install binaries, [DRIVELETTER]\Program Files\Microsoft SQL SERVER\MSSQL.1\MSSQL\Install.
Search for the sa password, i believe it's yukon_90, and change it according to your windows password security policy.
2.
A. Prepare a dos window with this command replacing your instance name for the INST2 string.
osql /E /S.\INST2 /Q"dbcc traceon(4606,-1)"
As soon as the setup displays the message Installing msdb
with "C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Install\instmsdb.sql"
execute the above command.
The install should succeed.
B. Install first instance, it is installed in MSSQL.1 in the registry and folder structure. SP2 needs to already be on the default instance.
Create the registry key: HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.2\MSSQLServer\Parameters with DWORD value SQLArg3 = -T4606
Install second instance (it goes in MSSQL.2)
It succeeds as the startup parameter for SQL prevents security checking
Remove the registry key after installing SP2.
If you are going to install additional instance the same technique applies, the next instance is installed to the next mssql. .
We've actually have all of the above and the first option is the quickest and has the least overhead.
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply