SSIS package runs in BIDS but not in job

  • I have a package where it runs just fine in BIDS but when I run it in a job, I get the following error:

    Microsoft (R) SQL Server Execute Package Utility

    Version 10.50.1600.1 for 32-bit

    Copyright (C) Microsoft Corporation 2010. All rights reserved.

    Started: 7:07:32 AM

    Error: 2011-10-27 07:07:38.33

    Code: 0xC0202009

    Source: staging_LewisCardPro LewisCardPro [1]

    Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E09.

    End Error

    Error: 2011-10-27 07:07:38.33

    Code: 0xC02020E8

    Source: staging_LewisCardPro LewisCardPro [1]

    Description: Opening a rowset for "[dbo].[Cards]" failed. Check that the object exists in the database.

    End Error

    Error: 2011-10-27 07:07:38.33

    Code: 0xC004706B

    Source: staging_LewisCardPro SSIS.Pipeline

    Description: "component "LewisCardPro" (1)" failed validation and returned validation status "VS_ISBROKEN".

    End Error

    Error: 2011-10-27 07:07:38.33

    Code: 0xC004700C

    Source: staging_LewisCardPro SSIS.Pipeline

    Description: One or more component failed validation.

    End Error

    Error: 2011-10-27 07:07:38.33

    Code: 0xC0024107

    Source: staging_LewisCardPro

    Description: There were errors during task validation.

    End Error

    DTExec: The package execution returned DTSER_FAILURE (1).

    Started: 7:07:32 AM

    Finished: 7:07:38 AM

    Elapsed: 6.084 seconds

  • are you pointing to the same server/database in BIDS as in the Job ?

    because it looks from the error message that a table can't be found.

  • I am. I've deployed the package a couple times just to be sure everything is correct.

  • I believe the 0x80040E09 is a permission denied. What user is trying to access the database and does that user have permissions.

    I also noticed you are running 2008R2 RTM, have you considered applying SP1?

    CEWII

  • When a job fails and the BIDS works first culprit is almost always security. Check the login for the SQLAgent and confirm that login has the necessary rights, unless you used a proxy in the job step, then check that login instead.


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA

  • I think it's the security, so I'm going to chekc that

Viewing 6 posts - 1 through 5 (of 5 total)

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