Thanks very much for this - I never would have guessed there would have been so many issues moving from 2005 to 2008 R2! We're moving in January, so I'm...

As a woman in technology, I've been fortunate to work in generally enlightened workplaces. What I've struggled against is the perceived career path for women in IT, which is to...

As it turns out, all was not lost. I found this forum thread, and found a solution (or a good enough one) within it: http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/96a2c8d9-6a9e-4f31-9449-0712f9bc2cbc

The solution that was the easiest...

We've now tried running this package on two different servers, with two different accounts, but the results are the same. The problem seems to be that we can acquire a...

UPDATE: I found the following link: http://blogs.conchango.com/jamiethomson/archive/2005/10/10/SSIS-Nugget_3A00_-Verify-a-data-source-before-using-it.aspx which was very helpful. However, I'm adding logging to capture the exception object info, but am not able to get the...

Could just be recency bias, but I highly recommend Gran Torino. Not for the wee little kids, but excellent for the adults. Clint Eastwood is ridiculously good in it, and...

Re: consuming a web service from inside a script task, you can generate the proxy code from the WSDL & reference it in your script task, which is nicely documented...

Actually, our experience with this particular package has been the opposite -- the DLL had to exist in the .NET framework folder in order for dtexec to run it successfully....

Thanks, Michael! It's good to have a clear answer on this, though it's a surprise, in a way. I'll keep your "extra step" suggestion in mind, too.

Thanks again!

Sorry, let me clarify-- the package is not on a SQL Server per se (no databases), it's on a shared application server that has SSIS running/certain SQL Server 2005 components...