I have created a simple import job that first truncates three tables and then
imports update data into those tables from an Access database. My problem is
that the job fails on when running the SSIS import package. The import works
when I create the package, but not from within the jop. I believe it might be
the account the job is run under, but I cannot change that, since it always
reverts back to running under the local system account. WHen looking at the
job history I see that the truncate step runs under NT Authority/system while
the SSIS package is listed as running under Athena/system (athena is the
server name). I had to correct a problem with the Reporting Service being
installed with a simular error and not being able to run until I changed the
config file to have NT Authority/system as the user account.

Hi,

I noticed that you have resolved a similar issue by changing to run under
NT Authority/system. How about this time? Please let me know your current
status more clearly.

Best regards,

Vincent Xu
Microsoft Online Partner Support

================================================== ====
Get Secure! - www.microsoft.com/security
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties,and confers no rights.
================================================== ====



--------------------

Hi,

Sorry for misreading your post. I noticed that you cannot change the user
account.

Please send me the job history and the Application Event log.

My email is: v-xuwen (AT) microsoft (DOT) com

Thanks.

Best regards,

Vincent Xu
Microsoft Online Partner Support

================================================== ====
Get Secure! - www.microsoft.com/security
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties,and confers no rights.
================================================== ====



--------------------

Hi,

I'm sorry but I cannot find anything useful from the job history and I
cannot import the app event log into event viewer because it apeears to be
corrupt.

Here is some thoughts:

1. Create a credential with the Identity set to the Windows user account
that designed and built the SSIS package.
2. Create an SSIS Package Execution Proxy and specify the credential to be
the one created in step one.
3. Grant access to the proxy to the SQL Agent service account. If the SQL
Agent service account is a member of the sysadmin role, this step is not
needed.
4. Open the job properties.
5. Edit the step executing the SSIS package.
6. The 'Run As' drop down should now give you a choice of the SQL Agent or
the proxy created in step two above.
7. Schedule the job. It should run as expected.


Thanks.

Best regards,

Vincent Xu
Microsoft Online Partner Support

================================================== ====
Get Secure! - www.microsoft.com/security

================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties,and confers no rights.
================================================== ====



--------------------

Hi,

Thansk for your clarifying.

However, I still find

Event Name: OnError
Message: There were errors during task validation.

Operator: PIKEPLACE\Administrator
Source Name: Data Flow Task
Source ID: {3CDADDB2-3905-4C1A-A28B-D007E9E47EEA}
Execution ID: {52797495-93D9-4B80-A274-BC47E405EA42}
Start Time: 5/1/2006 3:18:42 PM
End Time: 5/1/2006 3:18:42 PM
Data Code: -1073594105

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Note:There were errors during task validation.

Therefore, please refer to my previous reply to have a test. Meanwhile, I
will try to research based on the app event log.

Thanks.

Best regards,

Vincent Xu
Microsoft Online Partner Support

================================================== ====
Get Secure! - www.microsoft.com/security
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties,and confers no rights.
================================================== ====



--------------------

I followed the steps you outlined and still recieve this error. The logs i
sent you were from after I applied the proxy.

"Vincent Xu [MSFT]" wrote:

Hi,

This is a quick note to let you know that I am researching your issue and
will get back to you as soon as possible. I appreciate your patience.


Best regards,

Vincent Xu
Microsoft Online Partner Support

================================================== ====
Get Secure! - www.microsoft.com/security
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties,and confers no rights.
================================================== ====



--------------------
<cMdpYMcbGHA.4672 (AT) TK2MSFTNGXA01 (DOT) phx.gbl>

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.


"Joe S." <joecrew (AT) news (DOT) postalias> wrote

I tried the steps you outline and now I get an error that the package cannot
be loaded...the client cannot establish a connection...Encryption not
supported on SQL Server. What now.

"Matt Yeager" wrote:

This might be a silly question, but...are you trying to deploy to a SQL 2000
Server? If not, meaning it is SQL 2005, were you prompted for a password
when you installed the package on the server? Which ProtectionLevel did you
use in the package?

-Matt Yeager


"Joe S." <joecrew (AT) news (DOT) postalias> wrote