Post reply

Error while migrating the SSIS package

  • November 13, 2009 at 10:28 pm

    #206578

    Hi ,

    I have a package A. Inside Package A, I have used Execute Package task which is execute Package B in the same solution file.These files are in Machine A(Sql server2005). I need to move the solution file to machine B(Sql Server 2008). I moved the solution file and database to the Machane B. while opening the solution file in Machine B it automatically starts to upgrade but while upgrading it is asking password to decrypt. but In originally I am not setting any password in that Packages.

    I went on to the Machine A and checked the protection level. Package A has "Dont Save Sensitive",Package B has "EncryptSensitiveWithUserKey". I have changed the protection Level in Package B as "Dont Save Sensitve." Still the issue persist.

    Any solution most welcome..

    Thanks in Advance

    Anthuvan

  • November 14, 2009 at 1:01 pm

    #1079391

    Can you try this

    Copy the DTSX Files from the ServerA(2005) to ServerB.

    Go to the ServerB(2008) and then create a new solution and try to add the packages into that solution.

    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • November 21, 2009 at 3:40 am

    #1082629

    Hi Bru,

    I have tried to import the package from new solution file. still i got the same error "failed to decrypt the protected xml..."

    thanks,

    Anthuvan

  • November 21, 2009 at 11:19 am

    #1082670

    Hi,

    The PackageB was having earlier the protection level "EncryptSensitiveWithUserKey", so SQL Server stored it there and needs that Key (what ever password) was initially given.

    Who was the user who created those packages in the initial machine 2005?

    If it was you, you have to recollect what password (key you typed) was entered on that machine.

    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • November 22, 2009 at 10:07 pm

    #1082801

    Hi Bru,

    I have migrated the packages successfully.

    I have changed the protection level to "Dont save sensitive" in Package A and save it Machine A.

    I copied the modified file From machine A to machine B.Now the error gone.

    Thanks for u'r effort.

    thanks,

    Anthuvan

  • November 22, 2009 at 10:22 pm

    #1082803

    anthu_soft (11/22/2009)

    Hi Bru,

    Thanks for u'r effort.

    thanks,

    Anthuvan

    Glad I could help 🙂 🙂

    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

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

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