SSIS Error with duplicate IDs of copied packages
Hi, I recently encountered an error when I created several copies of one package. It's always nearly the same package with small modifications. I call this packages from a parent package which is part of our datawarehouseing-framework. The problem is, when copying a packages or using a packages as template the packages' IDs and Task's-IDs are the same. And this isn't only an issueconcerning logging!! : When the parent package calls one of the copied packages the first task is executed in every package parallely. Furthermore ... when I for example set a breakpoint on a data transformation task in one of the packages, the breakpoint is set in all packages on the same task! This is resulting in strange errors because the tasks-states and variable values seem to get mixed up. Unfortunately there is only a possibility to change the package's ID, but the IDs of tasks are readonly! One solution is, to create a new package and copy all the tasks to the new package which creates new IDs, but doing so, I have to manually recreate a long list of variables, all the configurations, all the connection-managers once again. Furthermore I loose the layout of tasks. I found some posts about it here http://groups.google.de/group/microsoft.public.sqlserver.dts/browse_thread/thread/6f85a31ea190608a/0eae312aa8440cf8?lnk=gst&q=pitfall&rnum=1&hl=de#0eae312aa8440cf8or http://groups.google.de/group/microsoft.public.sqlserver.dts/browse_thread/thread/760093d58bf6ccb5/32ced2f2020ef3f7?lnk=st&q=data+flow+task+id+copy&rnum=2&hl=de#32ced2f2020ef3f7 saying the issue will be fixed by SP2, but now I don't see any comment on it in the CTP of Service Pack 2. Is there any solution to this problem or official roadmap about a fix from Microsoft?? Greetings Monte
November 30th, 2006 6:44pm

As a result, I submitted a bug report...https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=241901Feedback: 241901Title: Copying packages results in duplicate package GUIDs and enclosed task GUIDs
Free Windows Admin Tool Kit Click here and download it now
November 30th, 2006 7:31pm

Phil Brammer wrote:As a result, I submitted a bug report...https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=241901Feedback: 241901Title: Copying packages results in duplicate package GUIDs and enclosed task GUIDs Good. There's also a very similar one here. -Jamie
November 30th, 2006 11:05pm

Hi, unfortunately the first answer only applied to logging, for which you can find workarounds, but the major problem still exists ... Hereunder I postedmy comment to this report ... I hope this report gets reducted once again ... Hi, logging wouldn't be the biggest issue here, I already implemented out some workarounds for that. Much bigger is the problem explained detailled here:http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=974055&SiteID=1 Tasks with the same ID in different packages get executed at the same time (even if the packages are called sequentially) when called from a parent packages.This is a major bug and causes fatal errors at runtime.Try to reproduce it via setting breakpoints on a task ... the task with the same id in different packages get "breakpointed" too. Any solution or comment on that? Greetings Montechristo
Free Windows Admin Tool Kit Click here and download it now
December 1st, 2006 12:08pm

montechristo wrote: Hi, unfortunately the first answer only applied to logging, for which you can find workarounds, but the major problem still exists ... Hereunder I postedmy comment to this report ... I hope this report gets reducted once again ... Hi, logging wouldn't be the biggest issue here, I already implemented out some workarounds for that. Much bigger is the problem explained detailled here:http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=974055&SiteID=1 Tasks with the same ID in different packages get executed at the same time (even if the packages are called sequentially) when called from a parent packages.This is a major bug and causes fatal errors at runtime.Try to reproduce it via setting breakpoints on a task ... the task with the same id in different packages get "breakpointed" too. Any solution or comment on that? Greetings Montechristo Hi Montechristo, Your link above links back to this thread :) Did you post your original problem to Connect? -Jamie
December 1st, 2006 6:17pm

Jamie Thomson wrote: Hi Montechristo, Your link above links back to this thread :) Did you post your original problem to Connect? -Jamie Yep. That was his posting to the Connect item.
Free Windows Admin Tool Kit Click here and download it now
December 1st, 2006 6:22pm

Jamie Thomson wrote: Hi Montechristo, Your link above links back to this thread :) Did you post your original problem to Connect? -Jamie Sorry, this was a bit confusing. I posted the blue text in the comments-part of the Connect post of Phil Brammer. I just wanted it to be displayed also there and the links should leed back to here to show the initial thread to the Microsoft supportagent. From your experience ... how likely is it, that this will be fixed in a timespan of two or three weeks? I was talking with my developers concluding, that this bug will at least double our time and effort for the current project part. In times of DTS we were always working with templates and copies of packages. For us, this is really an issue! Best regards Montechristo
December 1st, 2006 6:40pm

montechristo wrote:From your experience ... how likely is it, that this will be fixed in a timespan of two or three weeks? I was talking with my developers concluding, that this bug will at least double our time and effort for the current project part. In times of DTS we were always working with templates and copies of packages. For us, this is really an issue!I don't even know and am not an authoritative source, but I can say with certainty that this will not get fixed within a month's time.
Free Windows Admin Tool Kit Click here and download it now
December 1st, 2006 7:06pm

montechristo wrote: Jamie Thomson wrote: Hi Montechristo, Your link above links back to this thread :) Did you post your original problem to Connect? -Jamie Sorry, this was a bit confusing. I posted the blue text in the comments-part of the Connectpost of Phil Brammer. I just wanted it to be displayed also there and the links should leed back to here to show the initial thread to the Microsoft supportagent. From your experience ... how likely is it, that this will be fixed in a timespan of two or three weeks? I was talking with my developers concluding, that this bug will at least double our time and effort for the current project part. In times of DTS we were always working with templates and copies of packages. For us, this is really an issue! Best regards Montechristo If you can get Microsoft to agree that this needs to get fixed ASAP then there's always a chance they'll get a hotfix out. You'll need to raise it through PSS though I think. -Jamie
December 1st, 2006 7:10pm

Anyone come up with a workaround for the " duplicatetask ids "issue,perhaps called product support andinstalled a hotfix? Or just hacked the .dtsx xml with a xsl transform and/or some code to re-uniqify all its executable guids? Whencopied packages withduplicate enclosed container guids are run together as child packages (even after channging their package GUIDs), theprogress and execution window display a givencontainer'smessages way too many times. The number of timesa given container'smessagesdisplay are multiplied by the number of times thatcontainer id was executed, not multiplied by the number of times the package guid+container id was executed. This behavior can result in an cross-join effect of messages, particularly for looping containers.
Free Windows Admin Tool Kit Click here and download it now
July 16th, 2007 8:26am

The following worked as a mechanism to replace all the container ids. To replace all container ids (taskhosts, for/foreach loops, sequences, and event handlers), 1. Collect the container ids via "crawling the container hierarchy" viathe object model. 2.Update the packageas if it were a binary large object (not via the object model ) with a global search and replace for these container ids (stripped of curly braces), substituting them with new stringified GUIDs. This container id substitution eliminateda large number ofduplicative event messages,and allowed breakpoints to occur where they were placed. Updating the container ids using search and replace preserves the layout as well, since it seems you cannot get at the visual layout via the object model.
July 17th, 2007 11:26am

Here are some workarounds to generate new package guids and the add-on Bids helper can reset the guids of tasks. Please mark the post as answered if it answers your question | My SSIS Blog: http://microsoft-ssis.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
February 26th, 2011 8:45am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics