I like the intent of the question, but alas poorly executed.

At first sight, it looks OK.

(except that the passwords are missing, but I think SQL Agent leaves them out for security reasons).

The connection name still uses ".NET" though. Try removing...

It's with the Hobbit included.

I'll probably read all those SQL Server 2012 books first that come out in the following months, and then LOTR.

Apparently there's a problem, otherwise the job wouldn't crash 🙂

Can you post the command line? (you can find it in the command line tab of the jobstep)

Did you do something special in the Agent jobstep configuration?

Did you select the checkboxes in the connections tab?

100 books? I'm glad I can read 2 on a whole year (technical books not included).

Don't get me wrong, I love to read (read the whole Dexter series last year),...

Are there packages that you still can open?

Not sure that will work, but you need to right click on your SSIS project and select properties.

Samuel Vella (7/19/2012)

---

With regards to the relevancy and a "catch all" resume..

I've been using a catch all for the past 6 years as a contractor and I've never been out...

Well, the only thing that makes sense is CPackage::LoadFromXML, which only pops up if a package cannot be opened for some reason, usually corruption.

Try renaming your ADO.NET connection from .NET to ADONET.

Is this the only error? The message itself points out there should be more:

Nice write-up John.

@mohammed: it depends. One employer will love your community involvement and your ambition to broaden your knowledge, while another employer might think you're wasting company's time online.

edit: fixed...

If you look at the XML code behind the package, you'll see this for a 2008 package:

<DTS:Property DTS:Name="PackageFormatVersion">3</DTS:Property>

2005 has code 2.

In which version are you trying to run the package?

My guess is that you are trying to run 2008 packages in a 2005 environment.