Re: more detail on issue

It isn't that it is "hard". It's a matter of information in connection
strings not being visible to the SQL Agent user. This was the solution that
Microsoft gave me. There may be other solutions, but the Microsoft support
technican I spoke with gave me this as the solution. This area of SSIS is
extremely undocumented. I'm sure in time we'll find better solutions, but
this appears to be the fix for now.


"SP" <SP@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A48246D1-9EF5-4059-95C3-14AD35F840EB@xxxxxxxxxxxxxxxx
Hi Matt,

I was just going put the same question where i found this discussion. I am
facing the same as CP-Buildog. Is it the only way to get around with this
problem. Then for each package we have to create a diffrent passoword. How
do
we remeber so many passowrords for which we have to create password
repository. Is it that complicated just to fire a SSIS package from sql
agent.

Thanks in advance
Swayam


"Matt Yeager" wrote:

I posted this in another thread, but this looks like the same issue so
I'm
copying the message here:

I encountered the same problem, even on the same server upon deployment.
I ended up contacting Microsoft and opening a support case. After a
couple
of hours on the phone, we found that if the SSIS Package's Security
setting
"ProtectionLevel" was set to EncryptAllWithUserKey or
EncryptSensativeWithUserKey that the passwords would actually be lost.
This
has to do with the fact that the SQL Server Agent process on your server
is
running as a different user and cannot validate the user key basically.
What
I ended up having to do is switch the Security ProtectionLevel to use
EncryptAllWithPassword or EncryptSensativeWithPassword and specify a
password for the package. I then re-deployed to SQL.

How I scheduled the Job also had to change. I could no longer specify my
package as a SSIS Step in a Job. I had to make my Job execute an
"Operating
System (CmdExec)". The command line was :

C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTExec.exe /DTS
"\MSDB\YOURPACKAGEHERE" /SERVER Q /DECRYPT YOURPASSWORDHERE
/MAXCONCURRENT
" -1 " /CHECKPOINTING OFF /REPORTING V

It seems like very much a work-around, but that's roughly the way I was
told
to keep the protected passwords. My support case person spoke with the
engineers and that was the desired result evidently. They are working on
documenting the Security Levels more though, as this seems to be coming
up a
lot. I honestly wouldn't be suprised if something in Security levels
changed
in SP2.


Hope this helps.

-Matt Yeager




"cp-bulldog" <cpbulldog@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6398C4B9-74A5-4258-924B-C0183B9DA201@xxxxxxxxxxxxxxxx
probably should have put all this info in the first post. we are using
SQL
2005. the sql job owner is set to my account right now for testing
which
is a
domain admin account. what is interesting is that although the job
owner
is
my account when the SQL agent tries to run it is tries to use the
server\SYSTEM account.

is this a known issue with a work around?

"cp-bulldog" wrote:
i have a dtsx package that runs fine from the the bus intelligence
studio
and
runs fine from within SQL environment when run manually. however,
when i
try
to shedule it via SQL Server Agent it fails. looks like it is trying
to
run
it as server\SYSTEM which is probably why it is failing.

any ideas on this?





.

Relevant Pages

  • Re: Cannot Restart SQL Server Agent
    ... Try to change the start up account for SQL Agent to ... "Local system account" and try starting the service. ... I even stopped the SQL Server and restarted it, ...
    (microsoft.public.sqlserver.server)
  • RE: SQLServer Error: 22046, Encryption error using CryptProtectData
    ... Tried using both the SQL agent service account and a proxy account created ... for the replication role. ...
    (microsoft.public.sqlserver.replication)
  • Error 87 from GetProxyAccount on line 604
    ... >the following User Right Assignments to the SQLCmdExec ... >service account for the SQL Agent in local security ... >of SQL Server. ... >Management>SQL Server Agent, ...
    (microsoft.public.sqlserver.programming)
  • Re: Funky Permissions Issue with ReplData Folder
    ... I've explicitly granted full control of the ReplData share to the SQL ... Service account as well as the SQL Agent account. ...
    (microsoft.public.sqlserver.replication)
  • Re: how to start mail session?
    ... You need to have the SQL Agent service run under an account (probably domain ... Wayne Snyder, MCDBA, SQL Server MVP ... The Mail session section was just greyed out. ...
    (microsoft.public.sqlserver.server)
Loading