COPY/PASTE From Project To Project

Howdy again...

Do I need to re-create a new package from scratch after doing what I did?
It seems I've made what is probably a typical newbie mistake: I used COPY/PASTE
to
consolidate containers from two packages into a single new project/package.

Now my new package generates multiple duplicate errors (23 of each...) whenever I open it:



Warning loading LoadBillingData.dtsx: Process configuration failed to set the
destination at the package path of "PackageData Flow Task to Load
Profiles, Versions, and
Transactions.EventHandlers[OnError].Variables[System::Propagate].Properties[Namespace]".
This occurs when attempting to set the destination property or variable fails.
Check the destination property or variable.



Error loading LoadBillingData.dtsx: Changing the name of a variable failed
because it is a system variable. System variables are read-only.



What happened:



new guy (goes without saying...) creates:

01. PROJECT A
02. add PACKAGE
A to PROJECT A
03. add some
containers, figger out what the heck is going on, get containers working
04. create
PROJECT B
05. create
PACKAGE B
06. add
containers, they work fine
07. whoops!
Want to consolidate the packages. Unix guy naively expects Bill has made MS
Visual Studio like all windows products (of which newbie is aware€¦):
08. create
PROJECT C
09. create
PACKAGE C
10. <ctrl
a> PACKAGE A
11. <crtl
c> PACKAGE A
12. <ctrl
v> PACKAGE C
13. <ctrl
a> PACKAGE B
14. <crtl
c> PACKAGE B
15. <ctrl
v> PACKAGE C
16. copy Flat
File Connection Managers
17. copy
Database Connection Manager
18. drag the
arrows around, fix the flat file sources, renew the column maps, etc
19. whoops! the
connections all look like a registry number! Fix the OLE DB Destinations,
Execute SQL Task containers by selecting the DB Connection Manager copied from
PROJECT A

20. successfully
execute PROJECT C/PACKAGE C
21. save all
22. exit
23. start MS
Visual Studio
24. Open
Solution
25. ERRORS!!!



Is this fixable?





Thanks,
Bill