Orchestrator PaaS is throwing a 500.30 error post a recent Microsoft patching? How to resolve this?
Issue Description:
Sometimes a 500.30 error may be encountered while accessing a PaaS Orchestrator after a Microsoft patching due to potential app plan issues.
The exception observed in the logs looks like the following in this scenario:
Application startup exception: Castle.MicroKernel.ComponentActivator.ComponentActivatorException: ComponentActivator: could not instantiate UiPath.Orchestrator.Scheduling.Configuration.UiPathAbpQuartzConfiguration—> System.Exception: Could not instantiate UiPath.Orchestrator.Scheduling.Configuration.UiPathAbpQuartzConfiguration.
—> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
Application startup exception: Castle.MicroKernel.ComponentActivator.ComponentActivatorException: ComponentActivator: could not instantiate UiPath.Orchestrator.Scheduling.Configuration.UiPathAbpQuartzConfiguration
—> System.InvalidOperationException: Cannot run without an instance id.
at async Task Quartz.Impl.StdSchedulerFactory.Instantiate()
Resolution:
Since the Identity and Orchestrator app services are continually interacting, it's advantageous for them to share the same underlying infrastructure. When Microsoft conducts its regular system patching, both app services are included within the same update domains. This unified update strategy prevents any downtime and removes the need to restart the app services.
However, if the app services are configured on different service plans, there could be problems following a patch update. Depending on the patching sequence, one service may become inaccessible to the other service post-update. This scenario could lead the entire platform to interpret the application as being offline.
Hence, to maintain uninterrupted service and operation efficiency, it's essential to have both Identity and Orchestrator app services on the same App Service Plan. This setup ensures that both services are updated concurrently, reducing compatibility issues and potential downtime. This best practice enhances the reliability and stability of your UiPath Orchestrator deployment on Azure.
- Ensure that the app services are included within the same AppServicePlan, like in the example below: