CODEWITHSUNDEEP
ssis
Swamy
Swamy

Reputation: 463

where to set the package password property

I have an SSIS package with protection level - EncryptSensitiveWithPassword and I can execute this package with in the BIDS.

While trying to deploy to file system using the Package Deployment Wizard I receive the error

The protection level of the package requires a password but the package password property is empty

Where should I set this password? (In BIDS in the designer I have set this password and while trying to open the project it even asks me for the password) So for deployment is there a another property to set?

Upvotes: 3

Views: 19144

Answers (4)

Shaji
Shaji

Reputation: 761

You can also easily set the package password by going into the 'Package Explorer' then right click on the package to go into the properties and set your protection level there.

enter image description here

Upvotes: 0

Abhijit P Malkar
Abhijit P Malkar

Reputation: 1

Set or change the protection level of the package or packages by using a command similar to the one of the following examples:

The following command sets the ProtectionLevel property of an individual package in the file system to level 2, "Encrypt sensitive with password", with the password, "strongpassword":

dtutil.exe /file "C:\Package.dtsx" /encrypt file;"C:\Package.dtsx";2;strongpassword

The following command sets the ProtectionLevel property of all packages in a particular folder in the file system to level 2, "Encrypt sensitive with password", with the password, "strongpassword":

for %f in (*.dtsx) do dtutil.exe /file %f /encrypt file;%f;2;strongpassword

If you use a similar command in a batch file, enter the file placeholder, "%f", as "%%f" in the batch file.

Upvotes: 0

user2339071
user2339071

Reputation: 4310

This error is generally caused due to the property PackagePassword being empty in your configuration. Kindly check it and if it's not set, set it.

Also change the protection level to DontSaveSensitive after opening the package using the password. Then add the packages to your solution and once you are done, make the protection level as SaveSensitiveWithPassword.

Try deploying your package with these settings.

Reference:Securing your SSIS Packages

Upvotes: 3

Nick.Mc
Nick.Mc

Reputation: 19245

As per the answer by user2339071, if you don't have any passwords in your connections (i.e. you use windows trusted security) then you don't actually need a password.

But, assuming you do... (perhaps you could calrify in the original question):

My understanding is that the package password is basically specified at runtime, not deployment time.

When your DTSX file exists in the file system (after deploying it or copying it there directly), then you need to execute it somehow and that's where you specify the package password.

For example if you use SQL Agent to run your package you will find a field in the job to enter that package password. If you use DTEXEC.EXE directly, there is a switch in there for your package password also.

Personally I don't use the package deployment wizard, I just copy the DTSX file to the target file location.

Upvotes: 1

Related Questions