Tuesday, November 15, 2011 11:30 AM
I have a problem that Runbooks get invalid when I edit them. When I undo the change and resync the Orchestrator Connector the runbook is still invalid in the Service Manger 2012 console. If I delete a Return Data string and add a new Return Data string the old (deleted) is still preset in Service Manager 2012 console and the whole runbook status is set to invalid.
How can I fix or troubleshoot this problem?
Wednesday, November 16, 2011 8:13 AMI had the same issue, it was fixed by deleting the invalid runbook in SCSM. It reappeared after resyncing the Orchestrator connection.
- Marked As Answer by Mikael O Karlsson Wednesday, November 16, 2011 10:26 AM
Wednesday, November 16, 2011 10:26 AM
I had the same issue, it was fixed by deleting the invalid runbook in SCSM. It reappeared after resyncing the Orchestrator connection.
Thank you that worked. I hope that this will be fixed to the final release so I don’t have to do this workaround every time I manage to get a runbook to get invalid J
Tuesday, March 27, 2012 7:48 AMModerator
If you are linking the SCO Runbooks with SCSM Service requests then this happens when you change the settings in Initialise Data in the SCO runbook. Travis explains this towards the end of this video and how to use the get runbook activity ID to minimise \ better control the data that is passed from Service Manager to SCO