Weird deployment problem with Manifest

  • Hi all,

    This is not my first package I am deploying, even though I'm no SSIS expert. I have a package I've deployed with a manifest file, on the SQL Server depository. The deployment worked fine, even though it gave me "Validation errors": See the Image attached.

    Now, when trying to run the package using SQL Server agent, it gives me an error after 3 seconds of execution, saying:

    Started: 3:01:24 PM

    Error: 2009-09-21 15:01:25.78

    Code: 0xC0010018

    Source: Check files exist

    Description: Error loading a task. The contact information for the task is "". This happens when loading a task fails.

    End Error

    Error: 2009-09-21 15:01:25.90

    Code: 0xC0048020

    Source: Import Ctrl File Import Ctrl File (DTS.Pipeline)

    Description: The version of component "Read CTR020-COUNT CTRL file" (1) is not compatible with this version of the DataFlow.

    End Error

    See the attached file for complete error, but I guess this is the start, and most important part.

    Now, I've looked everywhere, it looks like a basic package, even though it's the most robust one I've built, it checks for files presence, and runs only if the files are there. Is there anything I'm doing wrong?

    If you cannot tell from the information I'm giving you, what do you require to help?

    Thanks in advance all,

    Cheers,

    J-F

  • Here are a few things to check out:

    1) Was this deployed from a 32 bit machine to a 64 bit one?

    2) Are you referencing objects in your script component that aren't installed on the target server?

    3) Do the versions of SQL Server in each environment match, including service pack level?

  • Erik Kutzler (9/21/2009)

    1) Was this deployed from a 32 bit machine to a 64 bit one?

    Both machines are 32 Bit. My dev environment and the QA Server.

    2) Are you referencing objects in your script component that aren't installed on the target server?

    I'm not sure what you mean, I do an import in 1 of the script (imports system.io) to check for a file existence.

    3) Do the versions of SQL Server in each environment match, including service pack level?

    Both versions are SP2 build 3042 SQL Server 2005, 1 of them is DEV (my machine) and the QA Server is Standard Edition, but with same build. Could that have an impact?

    Cheers,

    J-F

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

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