Runbooks not visible in SCO API

Leave a Comment / au2mator, SCO, SCSM, SQL

So, this is a quick one. We are talking about the “old” SCO Rest API, not the 2022 API. In former releases, It could happen that you cannot see newly created Runbooks with the API.

So for example, you cannot see the new Runbook in SCSM or au2mator. There is a quick Solution for this.

Run the following SQL Query against the SCO DB

TRUNCATE TABLE [Microsoft.SystemCenter.Orchestrator.Internal].AuthorizationCache

After the Command, rerun your SCSM Connector or check au2mator Runbooks.

NOTE: make sure that the actual load at the SCO is not that high, It can happen that active Runbooks are not reporting the correct state back to SCSM. See SCO Health Checker for Details: System Center Orchestrator Health Checker – TechGuy

The newly created Runbooks should appear now

Michael Seidl aka Techguy
au2mate everything

  1. Check and remove orphaned Runbooks To keep System Center Orchestrator up and running, and of course healthy, you need to take care of orphaned Runbooks....
  2. System Center Orchestrator Health Checker It is very important to take care of your System Center Orchestrator Environment. I have introduced multiple ways to do...
  3. Werte und Variablen an Runbooks übergeben und von Runbooks erhalten Ein tolles Feature und eines meiner meistgenutzten Funktionen im System Center Orchestrator ist es, Werte an ein Runbook zu...
  4. System Center Orchestrator SQL Query–Query failed Runbooks For your routine Orchestrator Checks, it can be vefy useful to see all failed Runbooks in a period. Of course...
  5. Upgrade to System Center Orchestrator 2016 System Center Orchestrator should be the first Product to upgrade to 2016, so we also will start with SCO. The...

Leave a Comment

Your email address will not be published. Required fields are marked *

CAPTCHA

*