Password validation failed

Hello Group,
we got the following message when running execute sp_adduser
Server: Msg 15118, Level 16, State 1, Line 1
Password validation failed. The password does not meet Windows policy
requirements because it is not complex enough.
Server: Msg 15007, Level 16, State 1, Procedure sp_adduser, Line 15
is there a way to turn this off on sql server(2005sp2) level.
Thanks in advancedTal shalom
Firstv of all in SQL Server 2005 using CREATE USER ... is recommended way
instead of sp_adduser.
Now regarding to the error you are getting, it is because you created LOGIN
with 'weak' password.
Please run in query builder (take a look at CHECK_POLICY=OFF parameter in
the BOL)
create login tal with password ='t',
go
create user Joe for login tal
drop user joe
drop login tal
"Tal Bar-Or" <tal_baror@.hotmail.com> wrote in message
news:%23sZnW6gkHHA.3452@.TK2MSFTNGP04.phx.gbl...
> Hello Group,
> we got the following message when running execute sp_adduser
> Server: Msg 15118, Level 16, State 1, Line 1
> Password validation failed. The password does not meet Windows policy
> requirements because it is not complex enough.
> Server: Msg 15007, Level 16, State 1, Procedure sp_adduser, Line 15
> is there a way to turn this off on sql server(2005sp2) level.
> Thanks in advanced
>
>
>
>|||Shalom Uri,
Thanks for the answer. I understand that CHECK_POLICY=OFF can be done per
individual login . However can it be done on the SERVER level for ALL
logins. This would help us not nodify the
code when migrationg from SQL 2000 to SQL 2005
Thanks in advanced
Tal,
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eApc3BhkHHA.2272@.TK2MSFTNGP02.phx.gbl...
> Tal shalom
> Firstv of all in SQL Server 2005 using CREATE USER ... is recommended
> way instead of sp_adduser.
> Now regarding to the error you are getting, it is because you created
> LOGIN with 'weak' password.
> Please run in query builder (take a look at CHECK_POLICY=OFF parameter in
> the BOL)
> create login tal with password ='t',
> go
> create user Joe for login tal
> drop user joe
> drop login tal
>
>
> "Tal Bar-Or" <tal_baror@.hotmail.com> wrote in message
> news:%23sZnW6gkHHA.3452@.TK2MSFTNGP04.phx.gbl...
>|||Hi Tal
By default CHECK_POLICY=ON.CHECK_POLICY are only enforced on Windows Server
2003 so I have no idea how to change it .
"Tal Bar-Or" <tal_baror@.hotmail.com> wrote in message
news:%23n$ddThkHHA.4904@.TK2MSFTNGP05.phx.gbl...
> Shalom Uri,
> Thanks for the answer. I understand that CHECK_POLICY=OFF can be done per
> individual login . However can it be done on the SERVER level for ALL
> logins. This would help us not nodify the
> code when migrationg from SQL 2000 to SQL 2005
> Thanks in advanced
> Tal,
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:eApc3BhkHHA.2272@.TK2MSFTNGP02.phx.gbl...
>

password sql 2005

I am creating an db login called test to test some sripts. When I try to set
that password it says password validation failed. The password does not meet
windows policy requirenments because it is too short.
In sql 2005 is the password policy based on your windwows policy?
stoney wrote:
> I am creating an db login called test to test some sripts. When I try to set
> that password it says password validation failed. The password does not meet
> windows policy requirenments because it is too short.
> In sql 2005 is the password policy based on your windwows policy?
>
It can be, but doesn't HAVE to be. Study the options that are available
when you create a new login.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||I think that this is the behvior if the OS is windows 2003. In any
case you can use the option CHECK_POLICY = OFF when you create the
login. Here is an example:
CREATE LOGIN MyLogin WITH PASSWORD = 'MyPass', CHECK_POLICY = OFF
Adi
stoney wrote:
> I am creating an db login called test to test some sripts. When I try to set
> that password it says password validation failed. The password does not meet
> windows policy requirenments because it is too short.
> In sql 2005 is the password policy based on your windwows policy?

password sql 2005

I am creating an db login called test to test some sripts. When I try to se
t
that password it says password validation failed. The password does not mee
t
windows policy requirenments because it is too short.
In sql 2005 is the password policy based on your windwows policy?stoney wrote:
> I am creating an db login called test to test some sripts. When I try to
set
> that password it says password validation failed. The password does not m
eet
> windows policy requirenments because it is too short.
> In sql 2005 is the password policy based on your windwows policy?
>
It can be, but doesn't HAVE to be. Study the options that are available
when you create a new login.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I think that this is the behvior if the OS is windows 2003. In any
case you can use the option CHECK_POLICY = OFF when you create the
login. Here is an example:
CREATE LOGIN MyLogin WITH PASSWORD = 'MyPass', CHECK_POLICY = OFF
Adi
stoney wrote:
> I am creating an db login called test to test some sripts. When I try to
set
> that password it says password validation failed. The password does not m
eet
> windows policy requirenments because it is too short.
> In sql 2005 is the password policy based on your windwows policy?

Password in config file

Hi

Config files doesn't seem to work for me :( i want to make a common config file for all of my packages but it is giving me error

Validation error. The AcquireConnection method call to the connection manager failed with error code 0xC0202009

I have placed pasword in my config file too. Following is config file which i m using, server name n password are masked.

<?xml version="1.0"?>
<DTSConfiguration>
<DTSConfigurationHeading>
<DTSConfigurationFileInfo GeneratedBy="SSBKD\955688" GeneratedFromPackageName="DTS_ACPM_MarkIT_Indices_Composites_TRAC_X_Asia_Index" GeneratedFromPackageID="{CB3660A1-5E6C-4D08-A7F5-4D6CE83578E2}" GeneratedDate="2006/10/19 14:05:20"/>
</DTSConfigurationHeading>
<Configuration ConfiguredType="Property" Path="\Package.Connections[ssmgn838.ACPM.acpmuser].Properties[ConnectionString]" ValueType="String">
<ConfiguredValue>server=########;user id=sa;password=******;database=ACPM;
</ConfiguredValue>
</Configuration>
<Configuration ConfiguredType="Property" Path="\Package.Connections[Text File (Source)].Properties[ConnectionString]" ValueType="String">
<ConfiguredValue>C:\acpm\filetoupload\Copy of ACPM_MarkIT_Indices_Constituents_Composites_1_ITRAXX_ASIA.tab
</ConfiguredValue>
</Configuration>
</DTSConfiguration>

If you take the ConnectionString from the configuration file and use it does the AcquiredConnection works?

The failure happens when you using DTExec or from designer?

Thanks,
Ovidiu

|||

problem came in AcquiredConnection

DTexec throws this error

even in designer it doesnt't identify password, i have to give it manually in my connection object.

|||

Can you tell me what type of connection is this? Oledb ADO.net?

Also can you check what is the value for the Package property ProtectionLevel?

Thanks,
Ovidiu