Isaac
Lifelong Learner
- Local time
- Yesterday, 17:32
- Joined
- Mar 14, 2017
- Messages
- 9,626
Anyone have any ideas on this?
I have an powershell script (very simple -create a text file - a test of sorts) which works fine on its own.
I have a .bat file which runs the powershell script (necessary to set -ExecutePolicy bypass), which when double clicked, works perfectly - text file is created.
Now I have an SSIS package with an Execute Process task. You can see the configuration, I've triple checked the paths they're all correct.
but what happens when I execute the SSIS package is the cmd window just comes up and sits there as shown in the second picture. Indefinitely. Bat file never seems to run, because end result does not occur.
Window (2nd picture) sits there indefinitely (ssis package does NOT err out), as if waiting for something. I finally x-out of it, and ssis err's because process terminated without success code.
I have an powershell script (very simple -create a text file - a test of sorts) which works fine on its own.
I have a .bat file which runs the powershell script (necessary to set -ExecutePolicy bypass), which when double clicked, works perfectly - text file is created.
Now I have an SSIS package with an Execute Process task. You can see the configuration, I've triple checked the paths they're all correct.
but what happens when I execute the SSIS package is the cmd window just comes up and sits there as shown in the second picture. Indefinitely. Bat file never seems to run, because end result does not occur.
Window (2nd picture) sits there indefinitely (ssis package does NOT err out), as if waiting for something. I finally x-out of it, and ssis err's because process terminated without success code.