Article ID: 2972927 - View products that this article applies to.
After installing Update Rollup 5 (UR5) to System Center 2012 Orchestrator Service Pack 1 (SP1) some Runbooks will fail and certain functionality will no longer work within the designer. This will occur if UR7 is installed on top of UR5. Below are two examples:
Within the Runbook Designer, the Invoke Web Services Web Method Selection dialog no longer works. When you click the ellipses button to the right of the Method textbox you will get "Class Not Found" on the initial use, while subsequent attempts show "An unknown error occurred".
Attempting to execute a Runbook containing the Query XML activity with the Runbook Tester will fail with "Failed to CoCreate IOpalisServerExtension". Running it on the server causes it to either never stop or hang. However, after stopping the Runbook the Log view indicates that it failed and investigation of the PolicyModule Log files will reveal logs containing entries similar to the following:
2014-05-26 12:50:22  1 Exception caught in void __thiscall MultiThreadedWorkflowThreadFactory::doTraversal(const class std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class std::allocator<wchar_t> >,const class WorkflowGraph &,unsigned int,class boost::optional<unsigned int>,class IWorkflowInstance &,class ExecutionDataTree)
struct std::pair<class boost::shared_ptr<class ExecutionDataBatch>,class ObjectInstanceStatus> __thiscall OpalisServerExtObjectRunner::run(const class Opalis::Uid &,class PropertyHelper::PropertyContainer &,const class LoopSpecificExecutionData &)
<MsgCode>Error while running an object</MsgCode>
class ATL::CComPtr<struct IOpalisServerExtension> __thiscall NativeObjectRunner::createExtension(long)
<MsgCode>Failed to CoCreate IOpalisServerExtension</MsgCode>
2014-05-26 12:50:22  1 Process terminated: exception caught.
There is a known issue within the UR5 installers for Orchestrator 2012 SP1. Any activities using the following binaries are impacted due to incorrect registry information:
1. Start an Adminstrative Command prompt.
2. Change the directory in the Command Prompt to the location of the Orchestrator DLLs affected and run the two regasm commands below. Note that they show the default location of the binaries in question:
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2972927 - Last Review: August 14, 2014 - Revision: 5.0