Bug in ProtectionLevel?

Hi all,

I am trying to start a package as a job and this does not work...

Referring to http://support.microsoft.com/?kbid=918760 I have checked the certain settings and I do not have set the ProtectionLevel to another setting then "DontSaveSensitive" - but my default setting in the template is "with encryption"

While starting the package from the package store using the technical user which is also used for the different service accounts all works fine.

After I created a NEW package and have set ProtectionLevel to DontSaveSensitive before doing any other step it works well also being started as a job...

BTW:
Copying objects from one package to another is really a big mess!
Is there hope that this issue will be solved shortly?

any hints why the new package works well?

cheers
Markus

Markus Fischer wrote:

Hi all,

I am trying to start a package as a job and this does not work...

Referring to http://support.microsoft.com/?kbid=918760 I have checked the certain settings and I do not have set the ProtectionLevel to another setting then "DontSaveSensitive" - but my default setting in the template is "with encryption"

While starting the package from the package store using the technical user which is also used for the different service accounts all works fine.

After I created a NEW package and have set ProtectionLevel to DontSaveSensitive before doing any other step it works well also being started as a job...

BTW:
Copying objects from one package to another is really a big mess!
Is there hope that this issue will be solved shortly?

What exactly is the issue?

If you want something improved then mentioning it on here will not get it done. you need to request it at Microsoft Connect.

Markus Fischer wrote:

any hints why the new package works well?

cheers
Markus

I'm guessing that you don't have any password stored in your package. Am i reght?

-Jamie

|||

Hi Jamie,

the "thing" is, that the package does not seem to recon my change of settings regarding the ProtectionLevel.

Otherwise the the fact that the first package does not run but the second does wouldn′t be explainable...

I do not have passwords stored in the package because I am using the Integrated Security in the connections.

Shouldn′t starting the package from the package store using the technical user proof, that the package with the technical user should also work started as a job?

cheers
Markus

|||

If you are using integrated security then there are no passwords stored in the package so it will run fine under DontSaveSensitive (assuming of course that the user has access to all the external sources).

Put simply, if there are no passowrds then there is nothing to be encrypted.

Being able to execute the package manually doesn't prove anything about running it from a job if SQL Server Agent is running as a different user.

-Jamie

|||

Jamie,

to summarise it:

- the technical user has access to all external sources
- there are no passwords used
- the technical user is the one also used for the service
- the technical user also is administrator

I did not have set the ProtectionLevel to DontSaveSensitive in the first steps, after doing it it also did not run as a job.

After building my package from scratch with first step setting the ProtectionLevel to DontSaveSensitive it now works well though I presume that there is a bug in this setting

Thanks for your assistance!

cheers
Markus