I get the same error on a VMware machine. Can you tell me what this means? There must be a reason why VM was questioned.

Thanks!

Yes, that did the trick. Thankfully, it was only 11 rows. Update statements did it. After restarting the SSIS service, the plans worked fine.

Just to add to the discussion, we had the same issue. We ran: select * from msdb.dbo.syssubsystems and noticed that the subsystem dll path was incorrect. Our path read mssql.7,...

I cannot see the code. Where should the attachment be?

Great article otherwise! Parts 1 and 2 were great too.

Thanks!