We have updated the System Center 2022 Orchestrator to Update Rollup 2 few days back. After updating we tried creating a Runbook with the Get Alert activity of System Center Integration Pack for System Center – Operations Manager (SCOM) in Runbook designer as part of our internal activity. Everything was working as expected before the update but suddenly during the configurations of Runbook, while clicking on properties of any activity, the Runbook Designer would crash, and a much amusing part is Operation console of System Center Operations Manager would open. To resolve the issue, we restarted the server since we felt the issue might be due to memory utilization. But the issue persisted.
When we tried to open Deployment Manager to check whether Integration Pack is installed correctly, Deployment Manager would go in Not Responding state. We tried to kill the process numerous times, but we couldn’t open the Deployment manager.
Upon investigation we learned that this is a known issue of Update Rollup 2 for System Center 2022 Orchestrator. Microsoft has provided the following resolutions for this issue:
- Install this hotfix KB5033783 https://www.catalog.update.microsoft.com/Search.aspx?q=5033783 for SCO 2022 Orchestrator UR2 for Runbook designer crashing while updating existing runbooks or creating new runbooks with some Integration packs.
- For Deployment Manager not responding or crashing we have a workaround in place. Copy C:\Program Files\Microsoft System Center\Orchestrator\Management Server\Deployment Manager\OrchestratorRemotingService.exe to C:\Windows\SysWOW64\OrchestratorRemotingService.exe
After applying the above patch and workaround, we were able to create new Runbook as well as run the Deployment Manager and check for Integration Packs.
References:
Written by Sneha Kotak, TopQore