running into error when install SCOM 2019 Evaluation version (2016RTMServer missing)

Yuan Lieu 21 Reputation points
2021-04-16T16:53:11.01+00:00

I'm trying to install SCOM 2019 Evaluation on our test VM (Windows 2019). I already installed the SQL Server 2019 on this same VM, and enabled IIS. I ran into these errors during the "Operational database configuration" stage of the install, does this mean i have install 2016 RTM Server on this VM as well? 2nd question is do I really have to create OmAA, OMDAS, OMAdmins users/groups in AD if we just want to build a simple standalone test environment?

:Info:2016RTMServer is installed: False
[07:06:46]: Info: :Info:Product check for 2016RTMServer failed.
[07:06:46]: Info: :Info:2016RTMConsole is installed: False
[07:06:46]: Info: :Info:Product check for 2016RTMConsole failed.
[07:06:46]: Info: :Info:2016RTMWebConsole is installed: False
[07:06:46]: Info: :Info:Product check for 2016RTMWebConsole failed.
[07:06:46]: Info: :Info:2016RTMReporting is installed: False
[07:06:46]: Info: :Info:Product check for 2016RTMReporting failed.

Operations Manager
Operations Manager
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
1,467 questions
0 comments No comments
{count} votes

Accepted answer
  1. CyrAz 5,181 Reputation points
    2021-04-17T11:43:07.32+00:00

    Did you update SQL server 2019 to latest CU? I remember posts with the same error back in the time where SQL 2019 was not compatible with SCOM 2019.
    It became compatible with SQL 2019 only starting with CU7, IIRC.


5 additional answers

Sort by: Most helpful
  1. Crystal-MSFT 47,536 Reputation points Microsoft Vendor
    2021-04-19T02:03:28.647+00:00

    @Yuan Lieu , For our error during installation, one possible cause can be that there's restricted memory (RAM) to the Instance hosting OpsMgr DB and DW.

    We suggest to check if there's any restriction on the RAM. If yes, try to increase the RAM allotted to the instance hosting the DB and ran the setup again.
    88894-image.png

    Please try the above steps and if there's any update, feel free to let us know.


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.