Re: Yukon: Password Validation Failed

From: Keith Wilson (keithwi_at_online.microsoft.com)
Date: 02/25/04

  • Next message: Geoff N. Hiten: "Re: Minimum rights for SQL Agent" 
    Date: Wed, 25 Feb 2004 08:19:01 -0800

    Is it possible that you are running a different operating system than the
    other person?
    Different operating systems utilize different password strength requirements
    by default.

    For Beta 2, the UI for creating logins, and for creating database users will
    offer more options.

    Regards, 

    -- 
Keith Wilson
This posting is provided "AS IS" without express or implied warranty,
guarantee, or rights.
"Kostil" <anonymous@discussions.microsoft.com> wrote in message
news:306D8E0B-89C5-4210-A979-3B5D612374F5@microsoft.com...
> On sqlservercentral.com we have been discussing a problem that hit one of
the forum readers. In SQL Server Yukon Beta, he was unable to create SQL
Server login, the error message read: Password Validation Failed, Does not
meet Complexity requirments. I was testing this problem on my own server,
and it turns out that if setting "Password Must Meet Complexity Requirments"
in Local Security Policy is enabled, than SQL Server will not allow weak
password (username: admin, password: admin). Although, it is a bad idea to
give this sort of password to user.
> Now, if the computer running Yukon was a part of the domain, but then was
disconnected, and Local Security Policy about complex passwords is disable,
why does SQL Server still does not allow to assign password the same as
username? I repeat, that I tested this problem on stand alone computer and
eveything worked with Local Security password complexity disabled. Why, this
person is experiencing this problem and I don't?
>
> Thank you,
> Kostil
  • Next message: Geoff N. Hiten: "Re: Minimum rights for SQL Agent"