Thanks! Its an idea, plus there already is some room to do something similar to what you described in order to avoid re-running a successful refresh in the event of...

we tie our database connections to specific SQL Server userid's for various security and auditing reasons.

By windows security, I mean active directory. We use sqlserver logons so that the userid remains consistent whether in development, staging, or production. That doesn't happen using the Windows/active directory...

same security.

I am thinking its my connection string, that I am trying to store it in the package configuration, but exactly what is off, is the thing I can't...

a double check with the DBA's confirms we are supporting mixed mode authentication.