SQL Server 2005 (64-Bit) Multi-Instance Installations
When you start Installing a SQL Server 2005 (64-Bit) Multi-Instance Farm environment, you may encounter this particular error message during the Installation process itself. Your first SQL Server 2005 ‘Default’ Instance would be successfully installed and then patched upto Service Pack 2. However, when your second ‘Named’ Instance was started – this specific error message might be displayed during the SQL Server 2005 Database Services Installation process : [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. Launch script file C:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\Install\instmsdb.sql
The reason that this error message occurs is because your Windows Server 2003 GPO (Group Policy) may be stipulating a password which is greater than 8 characters and this particular password "Yukon90_" (located in the instmsdb.sql file) is only 8 characters in size :
create certificate [##MS_AgentSigningCertificate##] encryption by password = 'Yukon90_' with subject = 'MS_AgentSigningCertificate'
A workaround solution has been discovered, in relation to this Microsoft KB (Knowledge Base) Article : Error message in the SQL Server Errorlog 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.
Using BDF_Set_Key.exe
In order for this Registry Key entry to become consistent with any subsequent SQL Server 2005 Instances, a specific executable has been created which will provide us with some continuity here. This BDF_Set_Key.exe will need to be placed into the <Root_Installation_Path>\SQL Setup folder and executed (double-clicked) from this location before the next Installation (2nd, 3rd or 4th etc) of SQL Server 2005 – which will in essence add this Trace Flag (-T4606) into the System Registry to the appropriate position. For example:
-
During the First SQL Server 2005 (64-Bit) Installation Process as a ‘Default Instance’ –
-
Database Services would be Installed into the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\BINN folder
-
Analysis Services would be Installed into the C:\Program Files\Microsoft SQL Server \MSSQL.2\OLAP\BIN folder
-
Reporting Services would be Installed into the C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\Report Server\BIN folder
-
Second SQL Server 2005 Installation as a ‘Named Instance’ –
-
Database Services would then be Installed into this C:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\BINN folder
Therefore this Trace Flag (-T4606) would then be added to this System Registry Hive : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.4\MSSQLServer\Parameters
When you execute this BDF_Set_Key.exe, a Windows NT Command Window will ‘pop-up' - along with this Dialogue Box :
You can verify that this Trace Flag has been successfully added into the Windows Server 2003 System Registry by checking the output “BDF_Set_Key.log” file, which will be positioned in the same folder structure (<Root_Installation_Path>\SQL Setup) from where this BDF_Set_Key.exe file was launched.
Using BDF_Del_Key.exe
Once your next SQL Server 2005 Installation has completed successfully and received the Service Pack 2, this System Registry Key can then be removed from the Hive using this ‘BDF_Del_Key.exe’ executable file. The file should also be in this position <Root_Installation_Path>\SQL Setup folder and executed (double-clicked) from there. When this file is run, as before a Windows NT Command Window will ‘pop-up' along with this dialogue box :
You can verify that this Trace Flag has been successfully removed from the Windows Server 2003 System Registry by checking the output “BDF_Del_Key.log” file, which will be positioned in the same folder structure (<Root_Installation_Path>\SQL Setup) from where this BDF_Del_Key.exe file was launched.
These BDF_Set_Key.exe and BDF_Del_Key.exe files have been attached to this Web posting as "BDF_Keys.zip". There is also an MSDN forum posting here : Re: SP1 install problem with password - http://forums.microsoft.com/msdn/showpost.aspx?postid=2238519&siteid=1&sb=0&d=1&at=7&ft=11&tf=0&pageid=0
Thank you,
Gareth Ford
Premier Field Engineer - Microsoft | Services | Mob:+44(0)7791 191780 | 0870 501 0800 (Technical support UK only) http://www.microsoft.com/uk/support http://www.microsoft.co.uk/premierpeople/ Microsoft Limited (company number 01624297) is a company registered in England and Wales whose registered office is at Microsoft Campus, Thames Valley Park, Reading. RG6 1WG
Blog: http://sqlblogcasts.com/blogs/thepremiers/ People Talk, I deliver