Unable to invoke runbook
When trying to invoke a runbook in Runbook Designer I get the following error message:
Cannot start runbook 'RunbookName'. The specified account may be missing privileges required to invoke a runbook. Add the account to the Orchestrator System Group to give it the required authority.
The solution is to add the account that you are trying to invoke the runbook with to the local group OrchestratorSystemGroup.
I realized this after finding this error in the System event log:
Source: DistributedCOM
Event ID: 10016
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {2A16038A-77D5-4EAA-A7D5-12182AAF3932} and APPID {D1D9ECD5-8094-4FB8-8D69-A3AD701FF02C} to the user DOMAIN\accountName SID (S-1-5-21-1098006967-339498757-315576832-22368) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
When googling this I found the following page:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/dfc465bc-7bbd-483e-b98b-2ba56fa98313/the-applicationspecific-permission-settings-do-not-grant-local-launch-permission-for-the-com-server?forum=configmgrgeneral
1. dcomcnfg, expand Component Services -> Computers -> My Computer -> DCOM Config
2. Click View -> Detail -> Now you will get Application Name and Application ID in right side
3. Scroll down and find the application ID {D1D9ECD5-8094-4FB8-8D69-A3AD701FF02C} -> Right Click -> Properties and select the Security tab.
2. Click View -> Detail -> Now you will get Application Name and Application ID in right side
3. Scroll down and find the application ID {D1D9ECD5-8094-4FB8-8D69-A3AD701FF02C} -> Right Click -> Properties and select the Security tab.
This is where I found out that the OrchestratorSystemGroup is added here, and that my service account need to be added to this local group.
Cheers!
