I was working in a SQL Server 2005 setup case which failed while starting SQL Service with error:
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'. Refer to server error logs and setup logs for more information.
Then I reviewed the SQL Server error log and noted that
DateTime Logon Error: 18456, Severity: 14, State: 10
DateTime Logon Login failed for user 'sa'.
As per http://support.microsoft.com/kb/925744 State 10 corresponds to PASSWORD POLICY CHECK failure. The box I was working was in a workgroup. So we went ahead and used trace flag 4606 to byepass password policy check.
How to do that?
Create a reg key by name “SQLArg3” of type REG_SZ in the registry location
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<Instance ID Created by the install>\MSSQLServer\Parameters
and add the value “-T4606”
Note: SQLArg3 should be replaced with a value higher than existing keys. So if you already have SQLArg0, SQLArg1, SQLArg2, SQLArg3 then add the value above with SQLArg4
Now stop SQL Server Service and click “Retry” in the setup window and setup should proceed further and complete successfully.
Use of trace flag 4606 is documented in http://support.microsoft.com/kb/936892
Login failed for user 'sa'. (.Net SqlClient Data Provider)
Server Name: HARI
Error Number: 18456
Line Number: 65536
Hi, We encountered the same error when installing SQL Server 2005 EE on a windows 2003 Server, which is a Domain Member. Also, Password Policy check is disabled at the Domain Controller level. Adding the registry key as per your post helped complete the installation.Could you please guide us on finding the root cause of the issue or is it some kind of a bug with SQL 2005 Installer ? .. Because No password policy was enabled at the DC and we were able to install SQL 2005 EE successfully on other Domain Member servers with the same 'sa' password.. Thanks !
Please confirm whether you password policy settings are reflecting locally too.
You can do this by checking "password length" and "Password must meet complexity requirements" under "Computer Settings\Windows Settings\Security Settings\Account Policies\Password Policy" in gpedit.msc
Hi, Many thanks for the response !
The Password Policy 'Password Must Meet Complexity Requirements' is set to 'Disabled' under Group Policy of the Domain Controller.. The same password Policy is Grayed out locally for the Windows 2003 Domain Member server where SQL 2005 is installed. This local setting was verified using 'secpol.msc' and under Account Policy \ Password Policy..Same was the case when checked using 'gpedit.msc' also.. In addition, the settings are same on other Domain Member servers with SQL, which seem to have no problem with the 'sa' password at all.. Kindly advise if additional details are required. Thanks !