Phil Parkin (2/26/2013)

---

What version of SSIS are you using?

I THINK the answer is 2005, or Visual Studio 2005, pkgs save as DTSX

I sympathise. Can you confirm that you have got to the point where:

a) Package 1 works.

:w00t: Works well but when I tried to create a new connection and use it, that part died. The solution was to create a second DTSX package that called the connection I needed. That worked. Hmmmm... I see a pattern here.

b) Take a copy of package 1 (as per my first post) and save as package 2. No other changes are made to package 2.

:crazy: Correct. Save As, no other changes made other than the new connections. There's a bunch of containers and the only real change is the connection.

c) Package 2 fails.

:sick: It dies kicking and screaming, code spraying everywhere.

If so, this is surely a meta-data issue. Other than firing up an XML editor or text -file differencer and putting your Sherlock Holmes hat on, I'm not sure what to do next. Actually, considering upgrading to 2012 would be good - there seem to be fewer problems like this with it 🙂

➡ I'm rather new to this shop and recently finished a push to upgrading our main VM's to 2008, they're a little behind. Then again, I was at Deloitte for a while and even that multi-billion dollar company only recently started rolling to 2012.