on ‎2017 Aug 24 8:37 AM
Good morning experts,
I swear I've seen this problem before but I cannot pinpoint where and searching SCN hasn't yielded results.
Anyway, I have a client who's got a Shell execute pass that's doing some work with a CSV file. When the line executes, the Powershell.exe program doesn't seem like it's closing. The instance stays resident in memory until so many instances of it are running in memory that an intervention is necessary to close all the hanging Powershell sessions.
Anyone have any ideas how to make sure the Powershell.exe instance exits once the pass has concluded?
Request clarification before answering.
Brandon,
in the task parameters of your Shell Execute pass, try adding a line:
Parameter name: CLOSEOUTPUTSTREAM
Parameter value: 1
Kind regards,
Lambert
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A year ago when I asked this question, we ended up finding another way to do what needed to be done so the PowerShell script portion was eliminated and I forgot about this question. Today, I was running into the same problem but with a different client and came back across this question. I implimented your answer and it worked! Many thanks!
| User | Count |
|---|---|
| 8 | |
| 6 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.