April 26, 2010 at 4:05 pm
We've installed the 1st Instance of SQL Server 2005 as a 'named Instance', patched it to SP3 - all is fine.
Whilst trying to Install Second Instance of SQL Server 2005 64 Bit Edition, the Setup fails with the below error. And also same error occurs, while upgrading SQL Server 2000 instance SQL Server 2005 using inplace upgrade.
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
Then we contacted Microsoft and MS suggested the below solution for both the cases:
1.
Run the script "instmsdb.sql" from the location C:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\Install\instmsdb.sql after the installation or
2.
Add the Trace Flag (-T4606) to this System Registry Hive: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\MSSQLServer\Parameters
Where X represents the instanceID your going to install. In mycase, the first instance has MSSQL1, so we added the Trace flag -T4606 in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.2\MSSQLServer\Parameters and then installed the second instance
We kept on asking MS to give a permanent solution rather than the workaround But MS did NOT tell why this error occurring. So we went with workaround. Now we are planning to upgrade the same instance to SQL Server 2008. So do we need to keep the trace flag -T4606 for ever or Can I remove it and try the inplace upgrade to SQL Server 2008?
Please advice
April 27, 2010 at 12:14 am
Why the issue occurs:
To 'solve' it, just stop enforcing the password policy using
Alternatively, consider using stronger passwords, that do meet the policy requirements 😉
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply