Thank you Erland for your input. We do use linked servers in our environment and this was something that I had not checked, but upon doing so, I found that there are no links between the production and development servers. I feel you are correct in thinking that this will likely be the result of incomplete or inaccurate passing of credentials between machines. I rechecked all rights that this user has on the production box, server and database and all showed only a standard membership in a Public Active Directory group with only connect and read rights. I am puzzled over this. I have dug around, but can find no specific documentation about exactly what actions are being performed when the DTS Package Designer executes a save as action. All security documents that I can find refer to the required permissions to create or alter a package. Because we are now aware and alert to the issue, we are talking over potential test scenarios to try to trap the failure, but will likely be a few weeks before we can do that kind of research. I will definitely post my findings here as discoveries are made and again, I appreciate your input.