SSIS Error Message HELP!

  • Here's our environment:

    SQL Server 2005 x64 SP2 with a 2 node cluster. As long as SQL Server is on node 1 everything works great. When it fails over to node 2, most everything works great. The one exception are scheduled jobs that run on the server. Below is one set of error messages we get when it fails over and runs a scheduled job. We can still run them from BIDS on our local machines and they run fine. Someone had mentioned permissions issues, however both nodes have the same permissions and accounts running all services (including the SQL Agent). The package is using an XML configuration file located on the shared drive along with the SSIS package. The job itself is being run from the file system. Any help would be greatly appreciated!

    - Brian

    Error Message from SSIS run:

    Executed as user: PS\sql2k5svcsAGT. ...n 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:25:01 AM Error: 2009-12-02 08:25:03.58 Code: 0xC0048020 Source: Load OllePermitsPreLoad APPERMITS Load OllePermitsPreLoad APPERMITS (DTS.Pipeline) Description: The version of component "Flat File Source" (363) is not compatible with this version of the DataFlow. End Error Error: 2009-12-02 08:25:03.69 Code: 0xC0048020 Source: Load OllePermitsPreLoad SLPERMITS Load OllePermitsPreLoad SLPERMITS (DTS.Pipeline) Description: The version of component "Flat File Source" (1) is not compatible with this version of the DataFlow. End Error Error: 2009-12-02 08:25:03.80 Code: 0xC0048020 Source: Load OllePermitsPreLoad SPPERMITS Load OllePermitsPreLoad SPPERMITS (DTS.Pipeline) Description: The version of component "Flat File Source" (1) is not compatible with this version of the DataFlow. E... The package execution fa... The step failed.

  • Concentrate on this error:

    "The version of component "Flat File Source" (363) is not compatible with this version of the DataFlow"

    It looks like there is a mismatch between the SSIS version you have used to create the package and the SSIS version you use to execute the package. Make sure they match.

    ---
    SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

  • At first blush, this was my thoughts too. Everything I've checked appears to be up to date. Any ideas on where I could check to make sure everything is up to date?

    - Brian

  • beezell (12/9/2009)


    At first blush, this was my thoughts too. Everything I've checked appears to be up to date. Any ideas on where I could check to make sure everything is up to date?

    - Brian

    You may compare the versions of DTS.dll library. Go to the following folder:

    Microsoft SQL Server\90\DTS\Binn

    on each machine and see if the versions match.

    ---
    SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

  • SSIS is not cluster aware so in a clustered environment, you are better storing the package in msdb, as the file system from the 1st node might not be seen the same from the second node.

    Facts are stubborn things, but statistics are more pliable - Mark Twain
    Carolyn
    SQLServerSpecialists[/url]

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

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