Probe timeout on Powershell Activity

[TimbitGrrl]

While executing a Powershell activity on a MID Server via a workflow, every so often it fails due to a probe timeout.

Fault: Probe timeout reached: terminating


Any idea how to configure the probe timeout? I want to increase it as it's erroring in about 2 minutes. I want to increase it and see what happens (AD scripts could run a bit longer sometimes.)

[TimbitGrrl]

This still happens from time to time. I'm just wondering if anyone out there has any information...anything? Is there a setting somewhere that could change this?

[TimbitGrrl]

The message in my log on the mid server was:

Probe: Powershell:Windows - Powershell:[ip address] WARNING *** WARNING *** ProcessRunner terminated due to interrupt

The default timeout value is set for 300 ms. This may be changed by adding the wmi_timeout probe parameter to probe "Windows - Powershell":

Under the related list "Probe parameters" > New
name = wmi_timeout
active = true
Probe = Windows - Powershell
value = 900
- this will extend the timeout value to 900 ms.

[JamesEcoStratus]

A couple of our users have experienced some quirky activity lately and wondering if any one else in community has experienced similar and could offer some suggestions?

* KB articles being updated and present one day and gone the next? Then back?
* Changes to Service Catalog from update sets in TEST to PROD. Present and working on day one and gone day 2?
* Various others issues of similar nature that just seem to question integrity internally.

--We have tested this quirky issues multiple times and still not able to replicate. Maybe its a SNC issue on back end? checked Logs, and done a few others things on check list..

Any suggestions?

Thanks

JamesN903

[TimbitGrrl]

d