Metadata cleanup failed

SAM2009
SAM2009 used Ask the Experts™
on
Hi,


My DC is down so I reinstall Windows 2003.

During the process of metadata cleanup with NTDSUTIL I got err msg at the end when I did: remove selected server

I got this msg:
-------------------------------------------------------------------------------------
LDAP error 0x32(50 (Insufficient Rights).
Ldap extended error message is 00000005: SecErr: DSID-03151D15, problem 4003 (IN
SUFF_ACCESS_RIGHTS), data 0

Win32 error returned is 0x5(Access is denied.)

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

Now my problem I can't delete the DC in ADUC, it keeps telling me:

Access is denied.


If try to run metadata cleanup again it doesn't work because the server is not in site anymore. It seems the first metadata cleanup do the job but did not finish...

What can I do now?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Expert 2012
Commented:
Check the security rights on that  DC from ADUC and assign ur self full permission if its not there

Make sure u have enterprise admin rights
Leon FesterSenior Solutions Architect
Commented:
Typically you only need domain admins, unless somebody has removed permissions from this group.

So agreed that you try the enterprise admin group.

You mention that this is a Win2K3 DC, but what level is your AD?
If you're running Win2K8 DC's then it could be that this object is protected from accidental delete.

Check the properties of the computer object to confirm if it can be deleted.
Sandesh DubeyTechnical Lead
Top Expert 2011
Commented:
Ensuer that you are using domain/enterprise/schema admin user rights user id.If the server is not listed in ntdutil then this indicates that the same is deleted.However also ensure that the faulty DC instances are removed from ADsites and services,DC OU & DNS.

How to remove data in Active Directory after an unsuccessful domain controller demotion
http://support.microsoft.com/kb/216498?wa=wsignin1.0

Delete Failed DCs from Active Directory
http://sandeshdubey.wordpress.com/2011/10/12/metadata-cleanup-of-a-domain-controller/

Once the instances are remove run dcdiag /q and repadmin /replsum to check the health of online DC if error is reported post the same.

Note:If faulty DC is FSMO role holder you need to seize the FSMO on other DC.Also ensure Authorative time server is configured on PDC role holder server.

Seize FSMO role: http://www.petri.co.il/seizing_fsmo_roles.htm

Configuring the time service on the PDC Emulator FSMO role holder
http://msmvps.com/blogs/acefekay/archive/2009/09/18/configuring-the-windows-time-service-for-windows-server.aspx

Hope this helps

Author

Commented:
Thanks everybody! In fact, even if Enterprise admins have full right in the DC OU someone restrict the rights on the DC object itself. After checking full right on the object, it works!

Thanks again for all you suggestions!

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial