System Center Orchestrator: The Server Threw an Exception

After upgrading System Center Orchestrator from 2012 R2 to 2016 CU4 or 1801, you may get the following error message:

Could Not Connect To The Specified Database Server

or

The Server Threw an Exception

FIX

The Runbook Management Server and the Database Server are no longer linked. First, you must install Microsoft® SQL Server® 2012 Native Client – QFE: https://www.microsoft.com/en-us/download/details.aspx?id=50402

Then you must take a look at your database security permissions and check if the Orchestrator Service Account still has full access on the DB. If not, then add your service account. Now, you can open the Runbook console and confirm if the error disappears.

 

Thanks for reading! You can follow me on Twitter @PrigentNico

About Nicolas 228 Articles
I work as a System Engineer, based in Switzerland with a primary focus on Microsoft technologies. I have 7 years experience in administering Windows Servers. . I am a Microsoft MVP for Cloud & Datacenter Management. I also received the PowerShell Hero 2016 award by PowerShell.0rg. And finally, I am "MCSE: Cloud Platform and Infrastructure", "MCSA: Windows Servers" and "Administering & Deploying SCCM" certified.