I have a rather simple SSIS package that is supposed to read data from DB1, save that data to a CSV file and then also write that same data to DB1 - when I'm running said package from within Visual Studio it's working perfectly fine, CSV being created and DB2 being written to.
When I try to run the package via CMD however, I can't get it to work - that is, I can get it to work, but the moment I activate the "write to CSV" parts, it doesn't work anymore. Which is odd, since we have plenty of packages that already do pretty much the same job, it's just that this one is for some reason not working.
I'm correctly running the 32bit version and I've correctly aligned the target SQL server version. Again, the package is running perfectly fine when it's just "read from DB1 and write to DB2" - whenever I activate the CSV part it's giving me error 0xC000F427 (executing a package outside of SSDT requires IS standard edition yada yada) - it can't be missing software though since I already have other packages doing virtually the same.
Anyone any ideas on what's causing this behavior?
