April 9, 2010 at 2:25 am
Hi all,
For reasons of my own I have developed a SSIS Package in two parts, each comprising of a large number of Dataflow components etc, but using the same databases.
I am now looking at combining them into a single package, but of course when I copy and paste components I get the following error:
The runtime connection manager with the ID "{7AD0A503-8711-491B-92AB-A0BFC6DDA73F}" cannot be found. Verify that the connection manager collection has a connection manager with that ID
I then have to reconnects the components and remap the fields. The connection managers have the same names, but are not being found on that basis. I tried to copy the connection managers from the second package, but this too fails.
I know that I can call the second package from the first, and tbh this is the way that I may end up going as I cannot face reconnecting 100+ components!
Is there a way around this at all?
Paul
April 9, 2010 at 2:29 am
I believe that SSIS works with unique IDs for its components 'under the hood'. Like LineageIDs for the columns.
I've had the same problem when copy pasting items with connections, and I had to remap them everytime, since SSIS doesn't recognise the IDs.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
April 9, 2010 at 2:36 am
Yes, I fear that you are correct.
Oh well... sometimes the hard way is the best way to learn!!
April 9, 2010 at 9:06 am
I have copied and pasted from package to package before. da-zero was correct about ids under the hood. That is why when you change a connection name that change "flows" throughout the package, because all of the components use a GUID to reference it. In most of the cases to fix a pasted source/destination all I had to do was reselect the data source and they were fine.
CEWII
April 9, 2010 at 9:36 am
Dirty but maybe a "less time" solution:
If you're a little bit used to XML files (and nothing else are the package files) you may be able to open the packages in notepad (or any other editor) and find/change the connection manager IDs in node <DTS:ConnectionManager> in the first few lines of the files. If you know the connection manager IDs from the "old" file and copy the objects from there via SSIS to the other (new) file (where the other half of your objects is in) you can update the objects to the new IDs simply by doing a Search&Replace in your editor.
April 9, 2010 at 12:46 pm
I have to say that that solution *might* work, but it scares me a LOT. Copy and pasting from one to the other and fixing the connection managers is pretty easy and would definitely be the way I would strongly recommend.
CEWII
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply