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

Urgent help NEEDED: Error 0x0000052E


I am trying to discover a workstation, but I got an error, and cannot solve the issue.

The remote registry service is turned on, Firewall is off, and We made sure there were not the same User/PC name either on a old AD and on a new AD.

I have no idea what the error of "the user name" and "the password" is pointing out.

Could somebody please give me an advice on this problem??

-------------------

Warning: Log path \\WIN-TC5MPVO01OL\QuestResourceUpdatingLogs$\ is not accessible. Error 0x0000052E. The user name or password is incorrect. .

Warning: Configuration path \\WIN-TC5MPVO01OL\QuestResourceUpdatingConfigs$\ is not accessible. Error 0x0000052E. The user name or password is incorrect. .

Warning: The Quest Migration Manager RUM Controller Service is not accessible. Error 0x00000005. Access is denied. .

Discovery completed successfully.

  • The error is the username/password is incorrect.   

    Follow the steps in this KB article to resolve the issue.

    https://support.quest.com/migration-manager-for-ad/kb/156393/error-0x0000052e-logon-failure-unknown-user-name-or-bad-password-when-moving-a-computer-

    Update the credentials by adding or reentering the username and password at both the global level and collection level if set at the collection level.

    Global Credentials update:

    1. Open Resource Update Manager console.

    2. Open "Projects | Domain Credentials Manager"

    3. Update the credentials as required.


    Collection Credentials update: 

    Credentials supplied will be used to process only the members of the collection.

    1. Right click collection name.

    2. Select "Domain Credentials Manager"

    3. Update the credentials as required.

    Run a "Cleanup" task and then run a "Move" task again.

    When entering the credentials make sure you use the following formats:
    domain\username
    users@domain.com

  • Hi, Chris!

    Thank you for your prompt reply and help. I really appreciate your kindness.

    Actually, I looked at the same post, and followed the instruction and tried to fix it; however, the error I got was the exactly same. Nothing changed.

    I wonder if there is anywhere else I should confirm.....