Active Directory database defragmentation error -1526

thenewmessiah 41 Reputation points
2022-01-05T19:03:29.26+00:00

Hi All,
I have a corrupted Active Directory DB on a RODC.
Performing the defragmentation, I get this error:

Operation terminated with error -1526 (JET_errLVCorrupted, Corruption encountered in long-value tree)

Do you have any idea on how to fix this error?

Thanks

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,861 questions
0 comments

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Dave Patrick 426.1K Reputation points MVP
    2022-01-05T19:16:36.933+00:00

    Not much to go on but the simplest solution may be to demote, reboot, promo it again or just stand up a new one for replacement.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

  2. Kazuki Masuda 81 Reputation points
    2022-01-06T13:33:59.767+00:00

    Hi,
    According to the KB, this error shows that Active Directory Replication doesn't work well.

    So that, I recommend you to check whether Active Directory replication works well by using "repadmin" command.
    And if something error message shows, please check based on the message.

    I hope this information will be of use to you.

    Best Regards,
    Zaamasu

  3. Limitless Technology 39,356 Reputation points
    2022-01-10T08:58:08.05+00:00

    Hello

    Thank you for your question and reaching out.

    I can understand you are facing the issue with AD Database defragmentation.

    The best solution will be Rebuild the Domain controller
    If you've more than one Domain controller you may try to rebuild the DC that is having problems and then re-promote it again.

    1. Remove active directory from the DC. You can do that formatting the hard drive, replacing the drive with a new one (backup the files that you need before formatting the drive). Normally this is done by using the dcpromo /forceremoval, but in corruption scenarios that shouldn't work. Just MAKE SURE that the DC and related Active Directory configuration IS OUT of the DC and is NEVER AGAIN related or CONNECTED to the same network where the ORIGINAL HEALTHY DCs are. Is very important to guarantee this step or you may end up in a complete forest corruption scenario. Perhaps formatting the drive is the best option here... Just in case :)
    2. The second step relates to seizing process. it's SEIZE ROLES, transfers are only possible when the DCs that have FSMO roles are online, but that’s not the case because we formatted the drive, right?

    If your "formatted" DC held any FSMO roles, you must seize them to another online DC. To identify if your “formatted” DC had any FSMO roles in it go to command prompt and type (first install support tools from your windows cd\Support directory):

    netdom query fsmo

    --If the reply is helpful, please Upvote and Accept as answer--

    0 comments
  4. thenewmessiah 41 Reputation points
    2022-01-12T11:22:53.453+00:00

    I was trying to avoid the demote, but this was the only solution.