Back in 2013 Microsoft discovered a bug in the upgrade process from Microsoft System Center 2012 Orchestrator to Microsoft System Center 2012 R2 Orchestrator. More information can be found here.
This exact same problem can occur when Update Rollup 1 is applied to Microsoft System Center 2016 Orchestrator.
The web console displays this warning:
Error Executing the current operation
Running the following two SQL statements against the Orchestrator database will fix it:
WARNING – Run these statements at your own risk. Take all precautionary measures necessary!
GRANT EXECUTE ON object::[Microsoft.SystemCenter.Orchestrator].[GetSecurityToken] TO [Microsoft.SystemCenter.Orchestrator.Operators]
GRANT SELECT ON object::[Microsoft.SystemCenter.Orchestrator.Internal].[Settings] TO [Microsoft.SystemCenter.Orchestrator.Operators]
Stumbled across a great blog post today by Jan Van Meirvenne that provides good guidance on configuring RBAC for Service Manager. It’s also the first in a series of posts about configuring SCSM to be multi-tenant capable.
Occasionally you can get a Change Request or Service Request that has activities stuck in a pending state. This can occur for a variety of reasons the most common of which are:
- You use PowerShell that creates the Change or Service Request, and then applies a template that contains activities
- You manually apply a template with activities in it
- You use PowerShell or Orchestrator to create a Change or Service Request and set the status of the Change or Service Request to “In Progress”
Thankfully there is an easy fix without hacking individual activities. Put the parent Work Item (Change or Service Request) On Hold, then wait for all child activities to also take the On Hold status, then change the parent Work Item status to In Progress.
This can be achieved manually through the console, or via PowerShell.