Microsoft's password complexity requires only 3 of the 4 conditions be met. (http://support.microsoft.
This makes me think the issue is with the SQL applicaiton, not the password.
Main Topics
Browse All TopicsI have created several SQL accounts on a SQL 2005 server, enforcing password policy, but not enforcing password expiration or "user must change password at next login."
I did not encounter any errors when setting up these accounts. However, the accounts lock when trying to use these accounts to make connections against the databases.
When I unlock the SQL account and hit ok, I get the following error:
Password validation failed. The password does not meet Windows policy requirements because it is not complex enough. (Microsoft SQL Server, Error: 15118)
In Active Directory Group Policy our password policy is set as follows:
Enforce password history: 10 passwords remembered
Maximum password age: 90 days
Minimum password age: 7 days
Minimum password length: 8 characters
Password must meet complexity requirements: Enabled
Store password using reversible encrption for all users on the domain: Disabled
The same settings are in place on the SQL server's local security settings.
For one SQL account I created, the password was 9 characters long, and contained symbols, numbers, and lower-case letters. The other account was 10 characters long, and contained upper-case letters, lower-case letters, and numbers.
Both passwords meet the password policy defined, and meet Microsoft's password complexity rules.
Can someone explain what I might be doing wrong, or what I'm missing?
Thanks
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Microsoft's password complexity requires only 3 of the 4 conditions be met. (http://support.microsoft.
This makes me think the issue is with the SQL applicaiton, not the password.
Ended up opening a case with Microsoft. This is a bug with SP2, and is supposed to be fixed in SP3.
The "password complexity" error only occurs once an account gets locked. The error does not appear when creating the account and setting the password.
The work-around for now, when an account is locked, is to uncheck the "enforce password policy" checkbox and hit ok. Go back in to the account and it should no longer be locked. You can then reapply the password policy enforcement.
Business Accounts
Answer for Membership
by: KCTSPosted on 2008-01-17 at 07:52:42ID: 20682429
Try creating a password that is
8 or more characters long
Contains an UPPER CASE letter
Contains a LOWER case letter
Comtains a NUMBER 0-9
Contains a symbol eg @, #, % or !