Deploying ssis package

  • Hi All,

    Am trying to deploy a package. which is created in VS2010 into sql server 2012. but am getting below error while execution of the job.

    Date

    LogJob History (Abdc)

    Step ID1

    ServerJob NameABCD

    Step Name ABCD

    Duration00:00:01

    Sql Severity0

    Sql Message ID0

    Operator Emailed

    Operator Net sent

    Operator Paged

    Retries Attempted0

    Message

    Executed as user: XYZ. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: Error: Code: 0xC00291CB Source: Send Mail Task Send Mail Task Description: Either the file "C:\Users\***\Desktop\&&&\ynmd.txt" does not exist or you do not have permissions to access the file. End Error Error: Code: 0xC0024107 Source: Send Mail Task Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: Finished: Elapsed: 0.375 seconds. The package execution failed. The step failed.

    when i execute it without sql job it executes but it is not working in sql job?

    Thanks in Advance.

  • Looks like a validation error. Is it safe to assume that any paths to the attachment file are determined dynamically at runtime? Many times the problem with deploying to a server is that paths are different from the machine where the Packagewas developed.

    Try setting the DelayValidation property on your file connection manager to true and redeploying the package before trying again. If that does not correct the issue you may also try setting the property to true on the Send Mail Task as well.

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • In addition to opc.three's comments, you probably also need to configure a SQL Server proxy to run your SSIS package using a job. That proxy account will also need permissions to whatever files/folders your package will access.

    Also the path to the problem file indicates it is sitting in some User's Desktop - a pretty unlikely location for external files on a production system. I would suggest also looking at implementing package configurations.

    ____________
    Just my $0.02 from over here in the cheap seats of the peanut gallery - please adjust for inflation and/or your local currency.

  • I will Try on That!!

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply