none
New SCOM 2019 Deployment - Populate User Roles failed RRS feed

  • Question

  • [15:16:15]:        Always:        :Current Action: PopulateUserRoles

    [15:16:15]:        Info:        :Info:GetLocalizedAdminGroupName: Administrators Group Name is: BUILTIN\Administrators

    [15:16:31]:        Error:        :PopulateUserRoles: failed : Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Value does not fall within the expected range.

    [15:16:31]:        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)

    [15:16:31]:        Error:        :FATAL ACTION: PopulateUserRoles

    [15:16:31]:        Error:        :FATAL ACTION: DatabaseActions

    [15:16:31]:        Error:        :ProcessInstalls: Running the PostProcessDelegate returned false.

    [15:16:31]:        Always:        :SetErrorType: Setting VitalFailure. currentInstallItem: Database Configuration

     

     I have been here:

    https://social.technet.microsoft.com/Forums/en-US/91f801aa-f92f-4916-bef2-491601eec7a0/scom-2016-install-populateuserroles-failed-threw-exceptiontype-systemargumentexception

    And here:

    https://kevinholman.com/2019/03/14/scom-2019-quickstart-deployment-guide/

    I've tried enabling TLS protocols and also forced TLS 1.2 only

    I've tried this:

    https://gallery.technet.microsoft.com/Script-to-automate-TLS-12-091f8fbd#content

    DB's are Windows auth only

    All servers are 2019 LTSB and SQL2017 AO - Installing SCOM 2019 Mar release in a closed environment.

    Wednesday, October 9, 2019 1:26 PM

Answers

  • [15:16:31]:        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)

    The dll names are in the stack trace.

    Reverting Server to use TLS 1.0 was successful in allowing the DB creation to continue

    SCOM_TLS_Config.log contents:

    08/10/19 03:41:16 : *****
    08/10/19 03:41:16 : *****
    08/10/19 03:41:16 : *****
    08/10/19 03:41:16 : Starting SCOM TLS 1.2 Configuration script
    08/10/19 03:41:16 : Checking to see if SCOM is installed and gather the SCOM Role.
    08/10/19 03:41:19 : Checking .NET Framework Version is 4.6 or later
    08/10/19 03:41:21 : PASSED:  .NET version is 4.6 or later
    08/10/19 03:41:21 :   Detected version is: (.NET Framework 4.7.2)
    08/10/19 03:41:23 : Modify Registry to enforce TLS 1.2
    08/10/19 03:41:32 : Modifying Registry Now ....
    08/10/19 03:41:32 : Completed TLS 1.2 prerequsites, configuration, and registry modification.  We must REBOOT the server before this will take effect.
    08/10/19 03:41:40 : Reboot was selected.  Rebooting server NOW.

    I am now troubleshooting OM Server install which gives this error:

    LaunchMSI: MSI D:\Software\System Center Operations Manager 2019\Setup\AMD64\Server\OMServer.msi returned error 1603

    wish me luck


    Friday, October 11, 2019 2:54 PM

All replies

  • The SQL Log:

    Date,Source,Severity,Message
    10/09/2019 10:21:23,spid48s,Unknown,AppDomain 2 (OperationsManager.dbo[runtime].1) unloaded.
    10/09/2019 10:21:23,spid55,Unknown,AppDomain 2 (OperationsManager.dbo[runtime].1) is marked for unload due to common language runtime (CLR) or security data definition language (DDL) operations.
    10/09/2019 10:21:23,spid55,Unknown,Setting database option SINGLE_USER to ON for database 'OperationsManager'.
    10/09/2019 10:21:07,spid79,Unknown,Setting database option AUTO_CLOSE to OFF for database 'OperationsManager'.
    10/09/2019 10:20:23,spid79,Unknown,AppDomain 2 (OperationsManager.dbo[runtime].1) created.
    10/09/2019 10:20:17,spid79,Unknown,Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
    10/09/2019 10:20:17,spid79,Unknown,Configuration option 'transform noise words' changed from 1 to 1. Run the RECONFIGURE statement to install.
    10/09/2019 10:20:17,spid79,Unknown,Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
    10/09/2019 10:20:17,spid79,Unknown,Configuration option 'clr enabled' changed from 1 to 1. Run the RECONFIGURE statement to install.
    10/09/2019 10:20:17,spid79,Unknown,Parallel redo is shutdown for database 'OperationsManager' with worker pool size [2].
    10/09/2019 10:20:17,spid79,Unknown,Parallel redo is started for database 'OperationsManager' with worker pool size [2].
    10/09/2019 10:20:17,spid79,Unknown,Starting up database 'OperationsManager'.
    10/09/2019 10:20:17,spid79,Unknown,Setting database option READ_COMMITTED_SNAPSHOT to ON for database 'OperationsManager'.
    10/09/2019 10:20:17,spid79,Unknown,Setting database option NUMERIC_ROUNDABORT to OFF for database 'OperationsManager'.
    10/09/2019 10:20:17,spid79,Unknown,Setting database option QUOTED_IDENTIFIER to ON for database 'OperationsManager'.
    10/09/2019 10:20:17,spid79,Unknown,Setting database option CONCAT_NULL_YIELDS_NULL to ON for database 'OperationsManager'.
    10/09/2019 10:20:17,spid79,Unknown,Setting database option ARITHABORT to ON for database 'OperationsManager'.
    10/09/2019 10:20:17,spid79,Unknown,Setting database option ANSI_WARNINGS to ON for database 'OperationsManager'.
    10/09/2019 10:20:17,spid79,Unknown,Setting database option ANSI_PADDING to ON for database 'OperationsManager'.
    10/09/2019 10:20:17,spid79,Unknown,Setting database option ANSI_NULLS to ON for database 'OperationsManager'.
    10/09/2019 10:20:17,spid79,Unknown,Setting database option RECOVERY to SIMPLE for database 'OperationsManager'.
    10/09/2019 10:20:16,spid69,Unknown,Parallel redo is shutdown for database 'OperationsManager' with worker pool size [2].
    10/09/2019 10:20:16,spid69,Unknown,Parallel redo is started for database 'OperationsManager' with worker pool size [2].
    10/09/2019 10:20:16,spid69,Unknown,Starting up database 'OperationsManager'.
    10/09/2019 10:18:49,spid89,Unknown,Parallel redo is shutdown for database 'SCOMINSTALLTESTDB_637062131248880081' with worker pool size [2].
    10/09/2019 10:18:49,spid89,Unknown,Parallel redo is started for database 'SCOMINSTALLTESTDB_637062131248880081' with worker pool size [2].
    10/09/2019 10:18:49,spid89,Unknown,Starting up database 'SCOMINSTALLTESTDB_637062131248880081'.
    10/09/2019 10:18:43,spid89,Unknown,Parallel redo is shutdown for database 'SCOMINSTALLTESTDB_637062131186527553' with worker pool size [2].
    10/09/2019 10:18:43,spid89,Unknown,Parallel redo is started for database 'SCOMINSTALLTESTDB_637062131186527553' with worker pool size [2].
    10/09/2019 10:18:43,spid89,Unknown,Starting up database 'SCOMINSTALLTESTDB_637062131186527553'.
    10/09/2019 10:17:46,spid89,Unknown,Parallel redo is shutdown for database 'SCOMINSTALLTESTDB_637062130611572193' with worker pool size [2].
    10/09/2019 10:17:46,spid89,Unknown,Parallel redo is started for database 'SCOMINSTALLTESTDB_637062130611572193' with worker pool size [2].
    10/09/2019 10:17:46,spid89,Unknown,Starting up database 'SCOMINSTALLTESTDB_637062130611572193'.

    Wednesday, October 9, 2019 3:02 PM
  • Hi,

    appreciate that you did an effort and researched for the possible causes. So you ruled out the TLS specifics, but what about this one:

    Installing SCOM 2019 fails with “Error: :PopulateUserRoles: failed”

    Can you please check the permissions on the folder, mentioned in the article?

    Thanks and regards,

    Stoyan


    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov


    Wednesday, October 9, 2019 5:25 PM
    Moderator
  • Hi

     

    Thanks for your detailed description.

     

    Please try Stoyan’s suggestion, restart the server and reinstall the SCOM server to see if it is working. Also, ensure SQLServer\Instance name is entered in the SCOM setup.

     

    If there’s any update, please let us know.

     

    Thanks and have a nice day!

     

    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.

    Thursday, October 10, 2019 2:09 AM
  • Install failed

    Permissions are set to defaults according to this

    https://support.microsoft.com/en-us/help/278381/default-permissions-for-the-machinekeys-folders

    As the SQL log shows, database creation is working on the sql server

    The install log shows "Value does not fall within the expected range" and points in the stack trace to the two .dll's that are failing

    Thursday, October 10, 2019 1:15 PM
  • Hi

     

    Thanks for your reply.

     

    For the two affected  .dll , could you let us now what are they?

     

    Meanwhile, could you check the log “SCOM_TLS_Config.log” under C:\Windows\Temp to see if there’s any error.

     

    In addition, do we have the chance to try to enable TLS 1.0 and install SCOM 2019 again to see if everything will be working.

     

    Thanks and have a nice day!

     

    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 11, 2019 8:46 AM
  • [15:16:31]:        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)

    The dll names are in the stack trace.

    Reverting Server to use TLS 1.0 was successful in allowing the DB creation to continue

    SCOM_TLS_Config.log contents:

    08/10/19 03:41:16 : *****
    08/10/19 03:41:16 : *****
    08/10/19 03:41:16 : *****
    08/10/19 03:41:16 : Starting SCOM TLS 1.2 Configuration script
    08/10/19 03:41:16 : Checking to see if SCOM is installed and gather the SCOM Role.
    08/10/19 03:41:19 : Checking .NET Framework Version is 4.6 or later
    08/10/19 03:41:21 : PASSED:  .NET version is 4.6 or later
    08/10/19 03:41:21 :   Detected version is: (.NET Framework 4.7.2)
    08/10/19 03:41:23 : Modify Registry to enforce TLS 1.2
    08/10/19 03:41:32 : Modifying Registry Now ....
    08/10/19 03:41:32 : Completed TLS 1.2 prerequsites, configuration, and registry modification.  We must REBOOT the server before this will take effect.
    08/10/19 03:41:40 : Reboot was selected.  Rebooting server NOW.

    I am now troubleshooting OM Server install which gives this error:

    LaunchMSI: MSI D:\Software\System Center Operations Manager 2019\Setup\AMD64\Server\OMServer.msi returned error 1603

    wish me luck


    Friday, October 11, 2019 2:54 PM
  • Hi,

     

    Glad to hear that DB is created successfully after using TLS1.0.

     

    And now I find our error has changed to “LaunchMSI: MSI D:\Software\System Center Operations Manager 2019\Setup\AMD64\Server\OMServer.msi returned error 1603”.  If there’s any misunderstanding, please let us know.

     

    Based as I know, this can be caused by some residual information. Please try the following steps to see if it is working:

    Note: please make a backup before we do the following steps:

    1. Deleted the following registry keys

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager

    2. Remove-eventlog -logname "operations manager"

    3. Delete APM and Microsoft Monitoring Agent Audit Forwarding service

    sc delete "System Center Management APM"

    Sc delete AdtAgent

    4. Reboot the machine

     

    Then re-install the Management Server to see if it is working.

     

    If there’s any update, please 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.

    Monday, October 14, 2019 9:27 AM