Deploy SSIS package in SQL server

  • Hi ,

    Please help in the SSIS package deployment. I have followed the steps mentioned in the following link.

    i created package in 2008

    & deployed in 2008

    http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/DTS/Q_24012483.html

    I got the following error.

    Message

    Executed as user: DevTester. ...n 9.00.4035.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 11:41:59 PM Error: 2010-09-28 23:41:59.84 Code: 0xC001700A Source: Description: The version number in the package is not valid. The version number cannot be greater than current version number. End Error Error: 2010-09-28 23:41:59.84 Code: 0xC0016020 Source: Description: Package migration from version 3 to version 2 failed with error 0xC001700A "The version number in the package is not valid. The version number cannot be greater than current version number.". End Error Error: 2010-09-28 23:41:59.84 Code: 0xC0010018 Source: Description: Error loading value "<DTS:Property xmlns:DTS="www.microsoft.com/SqlServer/Dts" DTS:Name="PackageFormatVersion">3</DTS:Property>" from node "DTS:Property". End Error Could not load package "E:\TestingSSISJob\TestPackage.dtsx" because of error... The package could not be lo... The step failed.

    Please help ASAP.

    Thanks,

    Sasidhar P

  • Have you got an instance of SS2005 running on the machine you are deploying to?

    Check for the existence of multiple dtexec.exe files on the deployment machine.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • Hi,

    I have created Packega in BIDS 2008

    But the SQL server is of 2008 and having 2005 Integration services.

    So how can i deploy this package and run in SQL job.

    Thanks,

    Chowdary

  • Not easily. Rewrite in 2005 and deploy, or upgrade server to 2008 and deploy.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • Yeah..the version where you developed the package should be the same where you deploy it else it will never work.i also experienced this problem sometime back:)

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

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