IS Package doesnt ship with password

Hi,
I tried many times checking "Save password" in connection manager editor. But everytime I open the editor again and I see the password field blank.
I took it as normal, and deployed my IS Package, It couldnt run because of login failed for user 'sa'.

How do I force IS to save password on any ProtectionLevel ?

Thanks,
Fahad

Fahad349 wrote:

Hi,
I tried many times checking "Save password" in connection manager editor. But everytime I open the editor again and I see the password field blank.
I took it as normal, and deployed my IS Package, It couldnt run because of login failed for user 'sa'.

How do I force IS to save password on any ProtectionLevel ?

Thanks,
Fahad

You can't. You'll have to set it through dtexec. SSIS doesn't save passwords. There are plenty of threads in this forum on that topic.|||First, /SET option isnt working
I am trying it this way
U sa /P gama /SET "\Package.Connections[TRIMURTY.TMDB.SA].Properties[ConnectionString]";"Data Source=TRIMURTY;User ID=sa;Provider=SQLNCLI.1;Persist Security Info=True;Auto Translate=False;Password=gama"

Second, I have to run this IS Package from another IS Package as well by using Execute Package Task. How would I supply these things on there ?

Please help me
Thanks
Fahad

Phil Brammer wrote:

Fahad349 wrote:

Hi,
I tried many times checking "Save password" in connection manager editor. But everytime I open the editor again and I see the password field blank.
I took it as normal, and deployed my IS Package, It couldnt run because of login failed for user 'sa'.

How do I force IS to save password on any ProtectionLevel ?

Thanks,
Fahad

You can't. You'll have to set it through dtexec. SSIS doesn't save passwords. There are plenty of threads in this forum on that topic.

|||If you're promoting these packages to the MSDB database in SQL Server, have you looked at using ServerStorage for the ProtectionLevel property?|||I have read about ServerStorage, It has nothing to do with storing connections' passwords but storing the Package.|||

Fahad349 wrote:

I have read about ServerStorage, It has nothing to do with storing connections' passwords but storing the Package.

No, not true. it means it relies on SQL Server to match up the assigned user to the SQL server user account.

ServerStorage: "Protects the whole package using SQL Server database roles."|||Here I am not interested in package protection or package security. I am interested in saving password with package. or to avoid this error "login failed for user 'sa'"

ProtectionLevel ServerStorage doesnt let me save the DTS Package in designer.|||

Fahad349 wrote:

Here I am not interested in package protection or package security. I am interested in saving password with package. or to avoid this error "login failed for user 'sa'"

ProtectionLevel ServerStorage doesnt let me save the DTS Package in designer.

Right, but again, you cannot save the password with the package. Can't do it. When you save to the server, you can choose SQL Server role security. Or, try EncryptSensitiveWithPassword. Using that though, you'll have to issue the password everytime the package executes.|||

Phil Brammer wrote:

Right, but again, you cannot save the password with the package. Can't do it. When you save to the server, you can choose SQL Server role security. Or, try EncryptSensitiveWithPassword. Using that though, you'll have to issue the

Ok I will issue the password, but that password will be to execute dts and its separate from passwords in connection manager.
And my understanding with this error message is; the Executable is unable to open child package for executing, not connection manager inside this child has error.|||

Fahad349 wrote:

Phil Brammer wrote:

Right, but again, you cannot save the password with the package. Can't do it. When you save to the server, you can choose SQL Server role security. Or, try EncryptSensitiveWithPassword. Using that though, you'll have to issue the

Ok I will issue the password, but that password will be to execute dts and its separate from passwords in connection manager.
And my understanding with this error message is; the Executable is unable to open child package for executing, not connection manager inside this child has error.

Tough to say... I would think it's the connection managers that's throwing the error.|||

Search this forum for configuration files then use these to "freeze" the password.

Philippe