RE: SSIS as part of scheduled job fails

Tech-Archive recommends: Fix windows errors by optimizing your registry

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,

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.
======================================================



--------------------
X-Tomcat-ID: 120198985
References: <45738B3D-3021-4E7C-A81F-155792D04CC5@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
From: v-xuwen@xxxxxxxxxxxxxxxxxxxx (Vincent Xu [MSFT])
Organization: Microsoft
Date: Fri, 28 Apr 2006 07:47:33 GMT
Subject: RE: SSIS as part of scheduled job fails
X-Tomcat-NG: microsoft.public.sqlserver.dts
Message-ID: <xCHX5fpaGHA.5300@xxxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.sqlserver.dts
Lines: 81
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.dts:65521
NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182

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.
======================================================



--------------------
Thread-Topic: SSIS as part of scheduled job fails
thread-index: AcZnzjd7jT0iIEsYS9mFSlAO5XNLfA==
X-WBNR-Posting-Host: 216.39.152.73
From: =?Utf-8?B?Sm9lIFMu?= <joecrew@xxxxxxxxxxxxxx>
Subject: SSIS as part of scheduled job fails
Date: Mon, 24 Apr 2006 11:38:01 -0700
Lines: 11
Message-ID: <45738B3D-3021-4E7C-A81F-155792D04CC5@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.sqlserver.dts
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.dts:65356
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.sqlserver.dts

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.





.

Relevant Pages

  • RE: SSIS as part of scheduled job fails
    ... cannot import the app event log into event viewer because it apeears to be ... Create an SSIS Package Execution Proxy and specify the credential to be ... Grant access to the proxy to the SQL Agent service account. ...
    (microsoft.public.sqlserver.dts)
  • Sql Server Job security problem
    ... When I run the SSIS package manually it works fine and I am login as the ... I also include this user in Sql Server 2005 as a login user with sysadmin ... I create a proxy with a credential that log as da with his password ... In the SSIS Package I have somme string connection with Integrity security, ...
    (microsoft.public.sqlserver.dts)
  • Scheduled SSIS package as job fails
    ... have a very simple SSIS package that I want to run as a scheduled job. ... created a proxy and gave the proxy SSIS package execution rights and told ... db_dtsoperator rights. ... I've tried this with the package saved as a file and to SQL Server. ...
    (microsoft.public.sqlserver.dts)
  • Proxy Failure to run SSIS job
    ... have a very simple SSIS package that I want to run as a scheduled job. ... created a proxy and gave the proxy SSIS package execution rights and told ... db_dtsoperator rights. ...
    (microsoft.public.sqlserver.dts)
  • Re: Exchange 2003 server not updating proxy addresses
    ... Anything in the app event log? ... bernardl wrote: ... the user is not created and no proxy addresses either. ... The user account is supposed to have this updated automatically from AD. ...
    (microsoft.public.exchange.admin)