FAQ: Why Don't My New Folders/Runbooks Show Up in the SCSM - Orchestrator Connector?

FAQ: Why Don't My New Folders/Runbooks Show Up in the SCSM - Orchestrator Connector?

  • Comments 13
  • Likes

I had this problem at MMS and someboy else here in Microsoft just asked me about it.  In case this is a more common thing that might be happening out there, I'll drop this blog post out here to explain it and what the resolution is.

Scenario:

You create a SCSM- Orchestrator connector and sync some runbooks over.

You add a new folder in Orchestrator (underneath the one that you originally configured as the scope when you first created the Orchestrator connector) or a runbook somewhere in the folder hierarchy.

You run 'Sync Now' for the connector and the new runbooks don't show up OR you open the SCSM - Orchestrator connector properties dialog and try to update the folder hierarchy and don't see the child folders.

You double check the permissions for the connector run as account in Orchestrator and all seems OK.  "What's the problem?" you say as you tear out a clump of hair.

 

The problem may be that the Orchestrator permissions cache hasnt updated yet to grant the connector run as account user on the new folder/runbooks.

You can force an update of the cache by running this SQL query on the Orchestrator DB.

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

 

Let us know if this works for you in the comments below.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • <p>Have the same problem &nbsp;in Rc . Truncate table solve it every time</p>

  • <p>Have advised several people experiencing similar behavior in recent weeks and this has resolved every time.</p>

  • <p>Yep - someone had thankfully already posted this here - <a rel="nofollow" target="_new" href="http://hindenes.com/trondsworking/category/system-center/">hindenes.com/.../system-center</a> - which helped save a little bit of what remains of my sanity a couple of weeks ago ;-)</p>

  • <p>Awsome! thank you so much, this has been bugging me for awhile, i had to wait 12 - 24 hours before the runbooks show up in Service Manager.</p>

  • <p>Just tested in 2012 RTM worked like a charm</p>

  • <p>That did the trick, even though I&#39;m in a lab and using the same account for everything! Thanks.</p>

  • <p>Works like a charm :-). Thanks Travis</p>

  • <p>It works but we have to do it everytime when a new folder is created in Orchestrator. Is there a permanent solution for this. </p> <p>Thanking you in Advance. </p> <p>Travis You rock man</p>

  • <p>OMG ! it works thanks for the tip, i was about to become bold.</p> <p>Cheers</p> <p>Laurent</p>

  • <p>Thanks for the post. &nbsp;This fixed my issue!</p>

  • Hi Travis,<br/><br/>I am having a problem, where the runbook is showing in the SM library but in runbook automation activity template I am not able to edit the parameters, it shows blank.