Share via

Runbook fails to run at scheduled time

LongLastingFlavor 216 Reputation points
2021-08-02T21:05:35.893+00:00

Hello, just built a new Orchestrator 2019 server and migrated the Runbooks from the previous 2012 Orchestrator. Everything working well except for the Runbooks that are scheduled to run at a scheduled time. After checking them in and running them they never kick off. Nothing shows in the log history or events. But if i run the Runbook tester it runs and completes with no issues. I have even manually recreated them with no change. It is a very basic and am kind of needing some guidance on how to troubleshoot.

119965-o1.jpg

119887-o2.jpg

119945-o3.jpg

Thank you!

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.
217 questions
0 comments
Accepted answer
  1. Leon Laude 85,686 Reputation points
    2021-08-03T08:33:35.45+00:00

    Hi @LongLastingFlavor ,

    Can you confirm that your link between Start daily 3:30am and Run .Net Script has the correct configuration, it should have Conforms to schedule equals true in the link condition.

    Do you also have any other runbooks triggering your runbooks? If yes can you show them and their settings?

    You can use the Orchestrator Health Checker tool which will show you your running runbooks, if there are too many queued runbooks which could also be one reason why your runbooks are not starting.

    https://github.com/LeonLaude/SCORCH/tree/master/Orchestrator%20Health%20Checker

    ----------

    If the reply was helpful please don't forget to upvote and/or accept as answer, thank you!

    Best regards,
    Leon

    1 person found this answer helpful.

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Stefan Horz 3,461 Reputation points
    2021-08-05T19:41:17.207+00:00

    Hi @LongLastingFlavor ,
    there was a problem with "Monitor Date/Time" activity in SC 2019 RTM Orchestrator, fixed in UR 1 (https://support.microsoft.com/en-us/topic/update-rollup-1-for-system-center-orchestrator-2019-3b629a38-3959-258e-3ef5-e94943e75d33):
    "Monitor Data/Time triggers runbook immediately even when configured to trigger at a specific time. "
    I recommend to install the Update Rollup 3 for System Center 2019 Orchestrator: https://support.microsoft.com/en-us/topic/update-rollup-3-for-system-center-2019-orchestrator-70bc1df6-adbc-9b89-68bf-df5a6eefca5f

    Important!: The Microsoft OLE DB Driver for SQL Server must be installed on Management Server and every Runbook Server and "Data Store Configuration" must be done after the upgrade.

    Regards,
    Stefan

    1 person found this answer helpful.
    0 comments
  2. LongLastingFlavor 216 Reputation points
    2021-08-05T20:12:55.683+00:00

    Thank you Stefan! UR3 and the OLE DB Driver for SQL was already installed. So far things are working well now.

    0 comments