Unable to Install System Center Orchestrator 2022 - Database Configuration Fails

Question

We currently have a SCORCH 2012 R2 environment that we're replacing with Orchestrator 2022. We're not doing any in-place upgrades or data migration - we're just starting with a fresh install on a brand new environment (new management servers, runbook servers, and SQL servers). We intend to install Management Server and web components on one server, and install Runbook Server on separate machines.

The bare minimum has proven to be impossible. No matter how we dice it up - attempt to install all components or just Management Server, try different database compatibilities, different dependencies, different database servers, complete uninstalls, etc. - nothing works, it always fails on the same step, with the same completely unhelpful error:

Database configuration failed: : Threw Exception.Type: System.InvalidOperationException, Exception Error Code: 0x80131509, Exception.Message: C:\Program Files\Microsoft System Center\Orchestrator\Management Server\DBSetup.exe failed. Please check C:\ProgramData\Microsoft System Center 2012\Orchestrator for more detailed log.

C:\ProgramData\Microsoft System Center 2012\Orchestrator contains no logs:

If I try to run DBSetup.exe (Data Store Configuration Tool) directly from the Orchestrator Program Files, I receive this error:

The only thing I can put this down to is the SQL driver - Microsoft SQL Server 2012 Native Client (aka SQLNCLI) - not being able to connect to the database. Now, we're running SQL Server 2019 on Windows Server 2019 Datacenter. Strap in, this is where it gets infinitely frustrating.

SQL Server 2019 is not supported by SQLNCLI. SQL Server 2019 is, however, supported by the Microsoft-recommended OLE DB Driver 19. Easy fix, right? Just install OLE DB Driver 19? No.

Despite the fact that Microsoft explicitly provides support for SQL Server 2019 for Orchestrator 2022, you cannot install Orchestrator 2022 without SQLNCLI. SQLNCLI only supports up to SQL Server 2014. It does not matter whether or not you install OLE DB Driver 19, and/or ODBC Driver 18 - it will still not allow you to proceed with install if you don't have SQLNCLI installed, and it will still fail database setup regardless.

Now, to complicate things, if I try to configure a new database on SQL Server 2012 R2, it still fails. Moreover, despite the presence of all three SQL drivers, I recall seeing an error message in a logfile reading as such:

DBSetup.cpp: Provider cannot be found. It may not be properly installed.

I have tried re-installing the drivers, and installing just one of each - no cigar. I also can't seem to find the logfile containing that error message now.

I'm at a loss here.. I don't know how to fix this. It seems insane that Microsoft requires a piece of software that they themselves "deprecated and ... is not recommended [for use in] new development work" in order to install and use software presumably developed by Microsoft within the last 12 months.

I really need assistance in identifying any workaround(s) for this. I have invested days in this issue, and can't find a path forward. All Orchestrator components (such as Management Server, Runbook Server, etc.) install correctly.. the only part that fails is database configuration.

Here's some debugging information:

Management Server OS: Windows Server 2019 Datacenter
SQL Server: SQL Server 19 on Windows Server 2019 Datacenter
SetupWizard.log: https://pastebin.com/E9YPbtDq
Installed Programs (Target Management Server):

Answer 1

Well, how's this for timing.. I just fixed it.

For anyone else in the future who may experience this issue, the magical trio of drivers is as such; you must have ALL 3 SQL Drivers/Clients installed:

Microsoft SQL Server 2012 Native Client (aka SQLNCLI)
Microsoft OLE DB Driver for SQL Server
Microsoft ODBC Driver for SQL Server

For this to work for me, I also had to install SQL Server Management Studio (SSMS). I don't know why this worked, but it did.

The requirement to install additional drivers is not specified anywhere in the Microsoft documentation - it only states that you need SQLNCLI. Installation succeeded with all three drivers, and SSMS installed:

I guess the drivers + SSMS installs some random requisite in the background that causes installation to succeeed?

Answer 2

Hi @Bradley Hodges ,

thank you for sharing you steps. I had Meeting with Microsoft for this today: The problem is the Microsoft OLE DB Driver 19 for SQL Server . Version 19 causes changes.
With Microsoft OLE DB Driver 18 for SQL Server (Version 18, https://www.microsoft.com/de-de/download/details.aspx?id=56730) the setup works:

The version 19 of the Microsoft OLE DB Driver for SQL Server should NOT be installed on the system.

SQL Native Client is needed for the installation as well.

If you make the "Data Store Configuration" after the "Database configuration" failed separately "Orchestrator users configuration" the DCOM settings at omanagement are not configured and users must be member of the local admin group of the Management Server to connect with Runbook Designer from another system.

Regards,
Stefan

Answer 3

Glad to hear you got it working and thanks for sharing your steps.

Have a nice day.

Answer 4

@Bradley Hodges @Stefan Horz - Thank you both. Had this exact issue with Scorch 2022 on Server 2022 with SQL 2019 and installing the OLE DB Driver 18 with the SQL Native Client worked. Appreciate your time troubleshooting the issue. Microsoft needs to fix this and put it in the install documentation.

Answer 5

Thank you Bradley for this awesome guide on the Prerequisites for installing and ensuring the Orchestrator 2022 connects to the DB. I have a question though, now that .NET Core v5 runtime has gone end of support, has anyone had success setting up Orchestrator with version.Net Core v6?

The Orchestrator 2022 IPs are now available from Microsoft as of July 3rd 2022.

https://techcommunity.microsoft.com/t5/system-center-blog/system-center-2022-orchestrator-integration-packs/ba-p/3564571