In Job Step > Properties, only see two tabs: Package and Configuration — EncryptSensitiveWithPassword

All we need is an easy explanation of the problem, so here it is.

I am going to echo another question almost exactly, only my question has a different objective:

In Job Step > Properties, only see two tabs: Package and Configuration

I am trying to set a job step that executes a package requiring a package password, since the package protection level is set to EncryptSensitiveWithPassword. The job is running on SQL Server 2014. I see all kinds of examples of how to do this, where the job step properties page has 9 tabs (Set Values, Verification, Command Line, General, Configurations, Command Files, Data Sources, Execution Options and Logging). Command Line allows me to enter the password (with the /DECRYPT command line option).

When I look at my job step, logged in to the server as an Admin, running SSMS as administrator, all I see are two tabs: Package and Configuration. I deployed the packages using the Project Deployment method. How do I get those other tabs to show up?

(My ultimate goal is to give the SQL Agent who runs the job access to a MySQL DB password, and I understand setting the package protection level to EncryptSensistiveWithPassword is the correct way to do that, but I cannot find another way to provide the package password.)

How to solve :

I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.

Method 1

In the job step properties after selecting SQL Server Integration Services Package as the type, switch Package source to SSIS Package Store to get the 9 tabs. SSIS Catalog is the default and only has 2 tabs.

SSIS Package Store:

enter image description here

SSIS Catalog (the default):

enter image description here

Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply