Runbook fails to run at scheduled time

Question

Runbook fails to run at scheduled time

LongLastingFlavor 226

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.

Thank you!

0 comments

Answer accepted by question author

Leon Laude 86,196

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

LongLastingFlavor 226 Reputation points

2021-08-03T16:27:03.733+00:00

Hello Leon and thank you for your response.

I do not see a conforms to schedule option when using the Monitor Date/Time. This is what the link shows...

This is the only Runbook and nothing else triggers it. If i run the script (Powershell) it is working so i believe the configuration is good. The Runbook Tester also run until completion. And the original Runbook that i imported from is working with these exact same settings.

Also ran the Health Checker and there are no queued runbooks.

Thank you,

Steve
LongLastingFlavor 226 Reputation points

2021-08-03T16:36:52.567+00:00

Could the amount of running runbooks be an issue? That number seems extreme?
Leon Laude 86,196 Reputation points

2021-08-03T16:39:25.693+00:00

Click on the underlined Start daily 3:30am within the Link Properties window, you will then be able to get more link condition properties.

According to the Orchestrator Health Checker (assuming you've configured it correctly) it seems you have a huge loads of running runbook instances, this can also be shown under the "Log" tab of each runbook, if it's a monitor runbook which is always running, it should only have one (1) running instance under the "Log" tab in the Runbook Designer.
LongLastingFlavor 226 Reputation points

2021-08-03T16:47:13.89+00:00

Here is a print screen of what i see when i click on the "Start daily 3:30am" link. I had to check Show common Published Data otherwise nothing is displayed.
Leon Laude 86,196 Reputation points

2021-08-03T17:01:27.15+00:00

My apologies, you were using a Monitor Date/Time activity at the start, this is why you don’t get the ”conforms to schedule” option in the link condition list.

I would definitely be worried about the amount of running runbooks, this can cause issues in your whole Orchestrator environment, there is a running statistics within the Orchestrator Health Checker and it is probably going to show that all your runbook servers are at max capacity (defaultnis 50 runbooks per server), hence the reason why Orchestrator cannot start more runbooks.
LongLastingFlavor 226 Reputation points

2021-08-03T17:07:18.27+00:00

Thank you, i agree that seems to be an issue. Something i am going to have to look into and resolve.
LongLastingFlavor 226 Reputation points

2021-08-03T21:35:32.717+00:00

I basically deleted all of my Runbooks but the Health Checker still displayed them in the list. I then ran the orphaned Runbook cleanup task and the Runbooks no longer displayed in the Health Checker. Then started the problem Runbooks that were the reason for my posting and they successfully ran! Thank you for your help and guidance Leon! Much appreciated! Thinking that my issue may have been cause by importing the old Runbooks although I cannot confirm that theory so I am just going to manually add them back and monitor the server.
Leon Laude 86,196 Reputation points

2021-08-04T06:23:16.347+00:00

That is great to hear, happy to be of help :-)

2 additional answers

Your answer

LongLastingFlavor 226 Reputation points

2021-08-03T16:27:03.733+00:00

Hello Leon and thank you for your response.

I do not see a conforms to schedule option when using the Monitor Date/Time. This is what the link shows...

This is the only Runbook and nothing else triggers it. If i run the script (Powershell) it is working so i believe the configuration is good. The Runbook Tester also run until completion. And the original Runbook that i imported from is working with these exact same settings.

Also ran the Health Checker and there are no queued runbooks.

Thank you,

Steve
LongLastingFlavor 226 Reputation points

2021-08-03T16:36:52.567+00:00

Could the amount of running runbooks be an issue? That number seems extreme?
Leon Laude 86,196 Reputation points

2021-08-03T16:39:25.693+00:00

Click on the underlined Start daily 3:30am within the Link Properties window, you will then be able to get more link condition properties.

According to the Orchestrator Health Checker (assuming you've configured it correctly) it seems you have a huge loads of running runbook instances, this can also be shown under the "Log" tab of each runbook, if it's a monitor runbook which is always running, it should only have one (1) running instance under the "Log" tab in the Runbook Designer.
LongLastingFlavor 226 Reputation points

2021-08-03T16:47:13.89+00:00

Here is a print screen of what i see when i click on the "Start daily 3:30am" link. I had to check Show common Published Data otherwise nothing is displayed.
Leon Laude 86,196 Reputation points

2021-08-03T17:01:27.15+00:00

My apologies, you were using a Monitor Date/Time activity at the start, this is why you don’t get the ”conforms to schedule” option in the link condition list.

I would definitely be worried about the amount of running runbooks, this can cause issues in your whole Orchestrator environment, there is a running statistics within the Orchestrator Health Checker and it is probably going to show that all your runbook servers are at max capacity (defaultnis 50 runbooks per server), hence the reason why Orchestrator cannot start more runbooks.
LongLastingFlavor 226 Reputation points

2021-08-03T17:07:18.27+00:00

Thank you, i agree that seems to be an issue. Something i am going to have to look into and resolve.
LongLastingFlavor 226 Reputation points

2021-08-03T21:35:32.717+00:00

I basically deleted all of my Runbooks but the Health Checker still displayed them in the list. I then ran the orphaned Runbook cleanup task and the Runbooks no longer displayed in the Health Checker. Then started the problem Runbooks that were the reason for my posting and they successfully ran! Thank you for your help and guidance Leon! Much appreciated! Thinking that my issue may have been cause by importing the old Runbooks although I cannot confirm that theory so I am just going to manually add them back and monitor the server.
Leon Laude 86,196 Reputation points

2021-08-04T06:23:16.347+00:00

That is great to hear, happy to be of help :-)

Answer 1

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

Answer 2

LongLastingFlavor 226

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

0 comments

Share via

Runbook fails to run at scheduled time

2 additional answers

Your answer