Hello, SQL 2005 EE SP3 64 bit on Windows 2003 EE. We switched SQL service services accounts and provided same as before access for SQL Agent account. it also sysadmin on SQL and used in proxy. Now some SSIS are broken. Error : [Flat File Destination [61]] Error: No destination flat file name was provided. Make sure the flat file connection manager is configured with a connection string. If the flat file connection manager is used by multiple components, ensure that the connection string contains enough file names. it's not working in BIDS as well. If I drop the files first - package can recreate them and load data, if the files exists - I got the mentioned error. Account before was working but had domain admin rights, so for security reason we trying to eliminate this. I tried to login on server using credentials for Agent account and play with package from BIDS in order to see connection managers and folders under this account. In connection manager I can see folders but cannot use files in it. If I select file and click Ok it's warn me "A valid file name must be selected".. In Windows Explorer I can see account has full rights, as a result I can create new folder, files, delete existing etc(since I connected under this account) .. Target server is on remote site, but still in same domain. What am I missing here..?Vladimir

Most likely your new proxy does not have enough rights on the folder where the files need to be manipulated on. I am guessing the delete privilege is missing.Arthur My Blog

My proxy using same account as Agent, job owner is sa...Vladimir

Obviously SA has no rights over the file system because it is a SQL Account. Instead, use a Domain Account based proxy.Arthur My Blog

Proxy account is using AD account, same which is SQL Agent account useVladimir

Change the job owner.Arthur My Blog

Tried to use Agent account as job owner, same issues. It's not working from BIDS, like I mentioned in first post.. Vladimir

Do not use Agent account, use Domain based proxy account. Revise and adjust the security rights for it over the directory using advanced properties.Arthur My Blog

I said proxy account is under domain based account... And folder properies verified like I said in first topic.. Vladimir

Please tell how do you delete the files in the package? Arthur My Blog

Package has connection managers as flat files. It just write info inside. With previously used account for SQL Agent we had no problem with this. Now only workaround is to manually delete the files and run package, which can recreate the files and write data in it. If the files exists - it will produce error mentioned in first post... BTW, account for SQL agent was changed using SQL Server Configuration Manager... Using File System task inside package will produce error as it cannot see destination folder etc.. Vladimir

So you set the conn manager to overwrite the target, right? Can you instead try to delete the files using a File System Task? What will happen? PS: Under rare circumstances a conn manager could became corrupted, delete and re-create it as another workaround. Arthur My Blog

I guess you replied before I updated my post ;-) Vladimir

Just in case, opened case with MS, waiting for responce, will try to update when resolved.. But if someone have any ideas - please, provide.. Vladimir

Yes, try the options I mentioned above.Arthur My Blog

In Addition to what I've already said, creating new connection manager in same package or even create new package with new connection manager pointed to same file - produce same issue.. MS contacted me and I will use process monitor to see what is going on during execution..Vladimir

Ok, I don't really understand why, but it start working this morning, witout any additional steps, I'm guessing replication in AD or something did not propagate it properly.. I can run package from server or BIDS, can see files etc.. So problem solved close topic, if possible.. Thank you ArthurZ for stepping in for help..Vladimir