• State Verified Answer
  • Replies replies
    6
  • Answers answers
    2
  • Subscribers subscribers
    6
  • Views views
    1558
  • Users 0 members are here
  • Locked Locked
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DRA Server Throwing Error: Administration server cannot identify your user account

shocko

I'm running DRA 9.1.1.430 as a single primary server and have brought in a separate new DRA 10 instance that's currently undergoing UAT. All of a sudden though our 9.1 instance is not allowing users to logon and throwing this message when they attempt to access via the ARM or DRA console:

  • The vmsysdra Administration server cannot identify your user account. try connecting to a different Administration server. if you continue to experience this issue contact you Administrator to synchronize Administration servers and refresh the accounts cache.

The only thing that resolves this is doing the following:

  1. Stop all DRA services
  2. Delete the DRA cache files
  3. Delete the DRA DOM Files

On restart this triggers and accounts refresh and then I have access for a short period but when the accounts refresh is complete I'm back to the issue!

  • Suggested Answer

    0  

    Hello,

    If / when you apply the Windows Security Updates or Windows DOT Net Updates from 2022 to the Windows OS Hosting the NetIQ DRA Administration Service; the Cache process will fail . This is a known issue with all versions of DRA. This issue is resolved within DRA 10.1.0 Patch 3 . There is a manual data migration path from DRA 9.1.x over to DRA 10.1.x .

    It should be noted that the DRA 9.x versions are no longer within committed support status. Our current, fully supported version of DRA is 10.1 with patch 3.

    For technical support, you can open a new SR via the customer portal. Here is a link to the Main DRA Support Page: https://www.microfocus.com/en-us/support/Directory%20and%20Resource%20Administrator%20(DRA) .

    Thanks!

    --Eric O'Brien

    Global Product Lead NetIQ Identity Management Products

    713-418-5555 Option 3

  • Verified Answer

    +1 in reply to   

    Thanks Eric. Here's my lanscape:

    1. Windows 2021 R2 with DRA 9.1 latest.and Feb 2022 MS updates - affected
    2. Windows 2016 with DRA 9.2 latest and Feb 2022 MS updates - not affected
    3. Windows 2016 with DRA 10.1 and Feb 2022 MS updates - not affected

    I'll see if removing the MS patches helps in scenario 1. 

  • Suggested Answer

    0 in reply to 

    Removing the Feb 2022 MS monthly updates resolved this for me on DRA 9.1.

  • 0 in reply to   

    I'm seeing the same issue on our primary running 10.2.0.1652.  Is there a fix for this version?

  • 0 in reply to 

    What OS? I had this on my primary server when it was fresh installed and I was logging on as any admin account OTHER than the service account for DRA. This was immediately post installation. I simply logged into DRA as the service account and configured it and all working fine since on Widdows 2019 with DRA version 10.2.0.1652

  • 0 in reply to 

    We're running Windows Server 2016.  This MMS has been deployed for several months and connected to two domains.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.