cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Shell execute pass - Powershell Hanging

brandonbollin
Active Participant
0 Likes
2,295

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?

View Entire Topic
lambert-giese
Active Participant

Brandon,

in the task parameters of your Shell Execute pass, try adding a line:

Parameter name: CLOSEOUTPUTSTREAM
Parameter value: 1

Kind regards,
Lambert

brandonbollin
Active Participant
0 Likes

Can you share a screenshot of what something like this would look like? I'm not sure I understand this answer. Do you just put, "CLOSEOUTPUTSTREAM = 1" on a new line under the Powershell execution line?

lambert-giese
Active Participant
0 Likes

You don't find it because "Shell Execute" doesn't offer task parameters at all. My answer was misleading, sorry.

You'll need to use a "To Custom" pass instead of "Shell Execute", like so:


brandonbollin
Active Participant
0 Likes

I see where you're going with this. Is ToShell a preexisting Java class or would I need to create the class so IDM can call it?

lambert-giese
Active Participant
0 Likes

It exists and is the same class that would be called when using a "Shell Execute" pass. It's just that "To Custom" is more generic and hence allows passing of parameters like "CLOSEOUTPUTSTREAM", which the more specialized "Shell Execute" UI of MMC doesn't offer - for whatever reason.

brandonbollin
Active Participant
0 Likes

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!