Forum Discussion

AhmedBahgat's avatar
AhmedBahgat
Copper Contributor
May 28, 2024

SCOM 2022 and SCOM 2019

Hello All

I have just joined this forum after 48 hours of intensive struggling, I am trying to apply for a job that requires SCOM experience, so I tried to install it on my Windows server 2019 domain on my home lab, I found that setting up SCOMJ 2022 or 2019 is a complete nightmare, possibly I tried over 50 times to no avail, I consistently get the error message in the SCOM setup log of:

Error: :PopulateUserRoles: failed : Threw Exception.Type: System.Runtime.InteropServices.COMException, Exception Error Code: 0x80070539, Exception.Message: The security ID structure is invalid. (Exception from HRESULT: 0x80070539)

 

Error: :PopulateUserRoles: failed : Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Value does not fall within the expected range.
Error: :StackTrace: at Microsoft.EnterpriseManagement.Interop.Security.Auth.AzAuthorizationStoreClass.Initialize(Int32 lFlags, String bstrPolicyURL, Object varReserved)

 

The SQL connection during setup is ok as the first DB OperationsDatabase is created but it gets deleted after that error due to a rollback.

Can anyone help me please as I am just about to give up on the SCOM and the job

Cheers

6 Replies

  • Rehamhossam's avatar
    Rehamhossam
    Copper Contributor

    hello Ahmed,
    i have the same issue ,can you help me how to resolve it.

    • AhmedBahgat's avatar
      AhmedBahgat
      Copper Contributor

      Hello mate

      I think it ended up being the right permissions not being set properly, I followed the steps to the letter and it ended up working

      Cheers

  • Rehamhossam's avatar
    Rehamhossam
    Copper Contributor

    Hello Ahmed,

    i have the same issue(The SQL connection during setup is ok as the first DB OperationsDatabase is created but it gets deleted after that error due to a rollback.), if it resolved with you please could you provide me the solution?

    • AhmedBahgat's avatar
      AhmedBahgat
      Copper Contributor

      Hello mate

      It was certainly the proper permissions not being set, including the domain users and nalso the SQL users, if you bfollow any of those guidlines ato the vletter, you should get it at the bend, in fact I also remo9ved it and reinstalled it about 3 times to get pracftised, so it is certainly a permission issue

      Cheers

      • admin2315's avatar
        admin2315
        Copper Contributor

        Sorry, I have exactly the same problem, can you be more specific about what you did that worked, what rights and for which account? Thanks, in advanced!

Resources