Apologies if this has been asked a zillion times before - I looked but couldn't find an answer.
I've started using SSIS to import some files into database on my local PC sql server instance; I then copy that out to other servers as needed. It's all working OK so I thought I'd amend the packages and import straight into one of the development servers. I changed the connection managers to point to that server, tested them in the SSIS frontend, all seemed OK, but when I execute the package it fails "to acquire connection ... Connection may not be configured correctly or you may not have the right permissions on this connection". I think the difference is that when I execute the package on my local server it uses windows authentication - but on the dev server I need to provide user ID and password. I tested that theory by creating a new login using SQL rather than windows authentication - so I can now reproduce the problem when executing the package on my local instance.
I've found some articles about using package configuration to store a password but haven't been able to get this to work. I don't like the sound of storing a password in a plain text file but I'll worry about that after I get the dratted process working.