Forum Discussion
Solved
SCO running Runbook gets orphanded after 2 to 3 Minutes and initiates the runbook new
So I had the issue, that it appeared that suddenly a runbook was running multiple times. All instances apearing in 2 to 3 minutes.
The new runbook was really running, the "older" once got orphanded...
In my case that was a runbook with the command get-scsmobject -class System.User from the smlets in it. There are about 40000 Users in this system.
When executing the command in the 32 bit ISE, the ISE crashed.
As a workaround, I reduced the the amount of data loaded by get-scsmobject and the effect has gone in the ISE and the Orchestrator runbook is working fine again.
In my case that was a runbook with the command get-scsmobject -class System.User from the smlets in it. There are about 40000 Users in this system.
When executing the command in the 32 bit ISE, the ISE crashed.
As a workaround, I reduced the the amount of data loaded by get-scsmobject and the effect has gone in the ISE and the Orchestrator runbook is working fine again.