• I ran into this problem, or at least a problem with the same symptom. The solution was to go back to the connection editor. On the All tab there is a property called "Application Name" that usually has a really long value that typically starts with SSIS, then your package name, then a GUID then the name of the connection. I usually remove all the stuff in the middle so that all I have left is SSIS.ConnectionName