Thank you for the digging to figure out what is happening.
I am already using the process task from SSIS so that part is good.
I ran a test where the only change was using the .exe instead of .com. That went well for the .exe version while the .com version failed.
Why we were using the .com version is down to legacy. Someone moved from using a windows task to run this to a ssis package and used the same code there to make it work as it used to.
No one thought there would be a difference so we suddenly had that problem appear.
Thank you for the help in figuring it out.
Regards
Anakardian
I am already using the process task from SSIS so that part is good.
I ran a test where the only change was using the .exe instead of .com. That went well for the .exe version while the .com version failed.
Why we were using the .com version is down to legacy. Someone moved from using a windows task to run this to a ssis package and used the same code there to make it work as it used to.
No one thought there would be a difference so we suddenly had that problem appear.
Thank you for the help in figuring it out.
Regards
Anakardian