Re: SQL 2005 Password Expiration

From: Mike Epprecht \(SQL MVP\) (mike_at_epprecht.net)
Date: 10/01/05


Date: Sat, 1 Oct 2005 00:07:41 +0200

Hi

The application developer must code for it and handle it. New error codes
and messages are included in SQL Server 2005

>From SQL Server 2005 BOL:
 15113 Login failed for user '%.*ls' Reason: Password validation failed.
The account is locked out.
 18463 Login failed for user '%.*ls'. Reason: Password change failed. The
password cannot be used at this time.
 18464 Login failed for user '%.*ls'. Reason: Password change failed. The
password does not meet policy requirements because it is too short.
 18465 Login failed for user '%.*ls'. Reason: Password change failed. The
password does not meet policy requirements because it is too long.
 18466 Login failed for user '%.*ls'. Reason: Password change failed. The
password does not meet policy requirements because it is not complex enough.
 18467 Login failed for user '%.*ls'. Reason: Password change failed. The
password does not meet the requirements of the password filter DLL.
 18468 Login failed for user '%.*ls'. Reason: Password change failed. An
unexpected error occurred during password validation.
 18487 Login failed for user '%.*ls'. Reason: The password of the account
has expired.
 18488 Login failed for user '%.*ls'. Reason: The password of the account
must be changed.

Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland

IM: mike@epprecht.net

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

"Dweller" <Dweller@discussions.microsoft.com> wrote in message
news:4D0C5874-13ED-4C78-BE52-CA863EA906A0@microsoft.com...
> Hi,
>
> Everybody knows that on SQL 2005 password expiration can be enabled for
> SQL
> logins. The question is how to know on a Client side about password
> expiration date in advance? You know, to ask user something like "You
> password will expire in a 2 days, do you wanna change it now or what?" :)
>
> Thanks.