none
Installation error on SCOM 2019 RRS feed

  • Question

  • Hi All,

    I am trying to install SCOM 2019 on Windows Server 2019 OS. My SQL DB and DWs are also installed on OS2019 and SQL version 2017. I have enabled TLS 1.0 and TLS 1.2 via registry in both the management server and the DBs as well. However I am receiving the below error message when I try to install.

    ==========================================

    [17:32:35]: Error: :PopulateUserRoles: failed : Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Value does not fall within the expected range.
    [17:32:35]: Error: :StackTrace:   at Microsoft.Mom.Sdk.UserRoleSetup.SetupProgram.populateUserRoles(String adminRoleGroup, String sdkAccount, InstallTypes installType, String installDirectory, Boolean overwriteExistingUsers)
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.ServerConfiguration.PopulateUserRoles(String adminRoleGroup, String sdkAccount, String installDirPath)
    [17:32:35]: Error: :FATAL ACTION: PopulateUserRoles
    [17:32:35]: Error: :FATAL ACTION: DatabaseActions
    [17:32:35]: Error: :ProcessInstalls: Running the PostProcessDelegate returned false.
    [17:32:35]: Always: :SetErrorType: Setting VitalFailure. currentInstallItem: Database Configuration
    [17:32:35]: Error: :ProcessInstalls: Running the PostProcessDelegate for OMDATABASE failed.... This is a fatal item.  Setting rollback.
    [17:32:35]: Info: :SetProgressScreen: FinishMinorStep.
    [17:32:35]: Always: :!***** Installing: OMSERVER ***
    [17:32:35]: Info: :ProcessInstalls: Rollback is set and we are not doing an uninstall so we will stop processing installs

    ===================================

    Has anybody encountered similar situations and do you know of any fix that I can refer to?


    Thanks, Shreeram

    Wednesday, October 16, 2019 6:54 AM

Answers

  • You could try Kevin's TLS script over here to check if everything is OK:

    https://kevinholman.com/2018/05/06/implementing-tls-1-2-enforcement-with-scom/

    The script will:

    1. Ensure the environment is supported for TLS 1.2

    2. Ensure the SCOM Roles are patched with the correct UR level

    3. Ensure that SQL is a supported version for TLS 1.2

    4. Ensure the software prereqs are installed

    5. Install software prereqs if they are missing

    6. Configure the registry for SCHANNEL protocols, .NET hardening, and ACS ODBC driver where required.

    7. Prompt for a reboot and reboot the server.


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by Shreeram S Wednesday, November 27, 2019 8:25 AM
    Wednesday, October 16, 2019 10:28 AM
  • As Kevin stated in his blog post over here: 
    https://kevinholman.com/2019/03/14/scom-2019-quickstart-deployment-guide

    Under the "Known / Common issues:

    1. Management Server installation fails when TLS 1.0 is disabled, and prerequisites for TLS 1.2 are missing. 

    On the first management server being installed, the UI will return a failure, and in the OpsMgrSetupWizard.log (found at C:\Users\<username>\AppData\Local\SCOM\LOGS), you see the following:
    [09:41:56]:    Info:    :Info:GetLocalizedAdminGroupName: Administrators Group Name is: BUILTIN\Administrators

    [09:42:12]:    Error:    :PopulateUserRoles: failed : Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057

    On the any additional management servers being installed, this will show up by hanging on “Registering Management Server” and never completing.
    This is caused by having TLS 1.0 disabled on the SCOM management server or SQL server. If TLS 1.2 is enforced or TLS 1.0 disabled, you must FIRST install the software prerequisites for TLS 1.2 for SCOM.

    TLS 1.2 Protocol Support Deployment Guide for System Center 2016


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by Shreeram S Wednesday, November 27, 2019 8:25 AM
    Tuesday, November 12, 2019 7:05 AM

All replies

  • Hi Sheeram,

    After enabling TLS 1.0 in the registry of all servers, did you reboot all servers and try installing SCOM 2019 again?

    Make sure you meet all the system requirements:
    System requirements for System Center Operations Manager

    And also make sure you have all the required firewall ports opened:
    Configuring a Firewall for Operations Manager

    To make the SCOM installation easier, make sure your account is member of the local administrator of all the servers, and that your user has sa permissions on the SQL Server.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, October 16, 2019 8:03 AM
  • Hi Sheeram,

     

    Try to Restart and install again to see if it is working.

     

    However, if it is still not working, please check the solution in Installing SCOM 2019 fails with “Error: :PopulateUserRoles: failed” to see if it is working.

     

    Hope it can help.

     

    Best regards.

    Crystal


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, October 16, 2019 9:04 AM
  • Hi Crystal,

    unfortunately this one didnt help. All the permissions are similar to the working SCOM management server (SCOM 2016 environment)


    Thanks, Shreeram

    Wednesday, October 16, 2019 9:11 AM
  • Do note that there are new security changes in SCOM 2019, compare to earlier versions of SCOM:

    https://kevinholman.com/2019/03/14/security-changes-in-scom-2019-log-on-as-a-service/

    At which step of the SCOM 2019 installation do you receive the error? Could you provide screenshots?


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, October 16, 2019 9:38 AM
  • This is the where it fails and the error logs are the ones provided on the top. Yes, the SCOM SDK, DWR, DWW and SCOM MS action accounts have log on as a service rights in the management server as well


    Thanks, Shreeram

    Wednesday, October 16, 2019 10:00 AM
  • You could try Kevin's TLS script over here to check if everything is OK:

    https://kevinholman.com/2018/05/06/implementing-tls-1-2-enforcement-with-scom/

    The script will:

    1. Ensure the environment is supported for TLS 1.2

    2. Ensure the SCOM Roles are patched with the correct UR level

    3. Ensure that SQL is a supported version for TLS 1.2

    4. Ensure the software prereqs are installed

    5. Install software prereqs if they are missing

    6. Configure the registry for SCHANNEL protocols, .NET hardening, and ACS ODBC driver where required.

    7. Prompt for a reboot and reboot the server.


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by Shreeram S Wednesday, November 27, 2019 8:25 AM
    Wednesday, October 16, 2019 10:28 AM
  • Hi,

    How's everything going? Did you try Leon's suggestion? If there's any update, feel free to let us know.

    Best regards.

    Crystal


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, October 18, 2019 6:29 AM
  • Hi Crystal/ Leon,

    Apologies for the late reply. Yes, i did run the scripts provided by Kevin in the blog and also have the prerequisite software's' as well, however the error is not resolved. I am getting the same error messages still.


    Thanks, Shreeram

    Tuesday, November 12, 2019 6:45 AM
  • Hi Leon,

    This didnt help resolve as well


    Thanks, Shreeram

    Tuesday, November 12, 2019 6:46 AM
  • As Kevin stated in his blog post over here: 
    https://kevinholman.com/2019/03/14/scom-2019-quickstart-deployment-guide

    Under the "Known / Common issues:

    1. Management Server installation fails when TLS 1.0 is disabled, and prerequisites for TLS 1.2 are missing. 

    On the first management server being installed, the UI will return a failure, and in the OpsMgrSetupWizard.log (found at C:\Users\<username>\AppData\Local\SCOM\LOGS), you see the following:
    [09:41:56]:    Info:    :Info:GetLocalizedAdminGroupName: Administrators Group Name is: BUILTIN\Administrators

    [09:42:12]:    Error:    :PopulateUserRoles: failed : Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057

    On the any additional management servers being installed, this will show up by hanging on “Registering Management Server” and never completing.
    This is caused by having TLS 1.0 disabled on the SCOM management server or SQL server. If TLS 1.2 is enforced or TLS 1.0 disabled, you must FIRST install the software prerequisites for TLS 1.2 for SCOM.

    TLS 1.2 Protocol Support Deployment Guide for System Center 2016


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by Shreeram S Wednesday, November 27, 2019 8:25 AM
    Tuesday, November 12, 2019 7:05 AM
  • The issue is fixed. As everyone pointed, it was the pre-req for TLS 1.2 that was missed.

    I had installed ODBC 13 but didnt reboot the server post installation. So the drivers didnt take effect and my SCOM installation kept failing. Post reboot the installation succeeded.

    Many thanks Leon and Crystal for all your support on this



    Thanks, Shreeram

    Wednesday, November 27, 2019 8:22 AM
  • Great to hear that Sheeram!


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, November 27, 2019 8:25 AM