Share via

System Ceter Orchestrator Runbook not stopping

Bijesh Venugopal 1 Reputation point
2020-11-26T12:48:35.247+00:00

Hi Team,

I am using SCORCH 2012 version, and recently the workflow are running in infinte loop, in more clear way, stop button in runbook designer is not working, if we click stop nothing happen. If we try to checkout, it showing please stop the runbook first.

If we try to do in Orchestration console, then it is showing, failed to assign null value to system GUID error. I can able to start a workflow, but cant stop

Also some of the runbook are auto trigerring, same workflow with same inout infinetley. Seems somehing wrong. Can anyone help me on this.

Bijesh V

System Center Orchestrator
System Center Orchestrator
A family of System Center products that provide an automation platform for orchestrating and integrating both Microsoft and non-Microsoft IT tools.
216 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Stefan Horz 3,461 Reputation points
    2020-11-26T19:15:30.923+00:00

    Hi,

    check if the Orchestrator DB ist working (https://social.technet.microsoft.com/Forums/en-US/096fdd1c-bef0-4204-8e84-487e2d1a4808/runbook-not-running-and-wont-stop?forum=scogeneral): Perhaps the DB or tempDB is out of space?
    Can you also check in tab "Log History" if an instance is stopped when you click ob "Stop"? Perhaps the Runbook is in the queue for starting caused by an external trigger or "Invoke Runbook".

    Regards,
    Stefan

    0 comments
  2. Bijesh Venugopal 1 Reputation point
    2020-11-27T17:50:12.443+00:00

    Yes Stefan,

    TempDB have 2GB space, i think it more sufficient(not sure, if not please suggest)

    When i click on stop button nothing is showing up for the stop runbook in Log History

    When i tried through Console sometimes it is showing no active jobs, or the following error
    "The null value from P{roperty JobID cannot be assigned to a type System.GUid."

    Bijesh V