SCORCH 2019 – ‘The Server Threw an Exception’ error after applying UR1\UR2

In this post, we’ll look into resolving an issue with System Center Orchestrator 2019 following the installation of UR1 and \ or UR2.

The Issue

After installing UR1 and \ or UR2 for System Center Orchestrator 2019, the Runbook Designer throws the following error on launch:

Upon further investigation, it appears that the Orchestrator Runbook Service will not start:

After examining the logs points towards a SQL back-end related issue:

For future reference Orchestrator logs can be found here: %ProgramData%\Microsoft System Center 2012\Orchestrator, with the above case the error was located in: %ProgramData%\Microsoft System Center 2012\Orchestrator\RunbookService.exe\Logs

Loading the Data Store Configuration Wizard, after inserting the server name and attempting to find the database, the follow error also occurs:

The Resolution

Easy to miss, however on the release notes for SCORCH 2019 UR1 & UR2, Microsoft state the following:

Before you install this update, make sure new SQL driver (MSOLEDBSQL) is installed on the Management server role. For more information, see the Microsoft OLE DB driver for SQL Server topic on the Microsoft Docs website. – Reference

To do this, download the Microsoft OLE DB Driver for SQL Server from here, install onto the SCORCH Runbook server(s), once completed, open the Data Store Configuration wizard, enter in the DB server hostname, now you should be able to select the existing data store and Finish the wizard:

Once completed, go to services.msc and it now will be possible to start the Orchestrator Runbook Service:

And finally, the Runbook Designer will now load without error: