Occasionally after the Orchestrator for Service Manager connector has run the status of some of your Runbooks may change to “missing” or “invalid”. Typically this is for one of the following reasons:
- You’ve renamed a Runbook
- You’ve deleted a Runbook
- You’ve moved a Runbook
Highlighting the Runbook with a “missing” or “invalid” status in the Service Manager console and delete them. Then synchronise the Orchestrator connector again and they should reappear and all should be well again.
However, sometimes your Runbook(s) just don’t appear at all. This is usually after you have recently created the Runbook(s). This occurs because the authorisation cache within Orchestrator hasn’t updated yet. To resolve the problem run the following command against your Orchestrator database and synchronise your connector again, or just wait a few hours:
TRUNCATE TABLE [Microsoft.SystemCenter.Orchestrator.Internal].AuthorizationCache