NtFrs error 13568 JRNL_WRAP_ERROR


one of networks came in , has 1 2008r2 dc , 2003 dc fsmo roles.   2003 1 above error.   planning retire 2003 dc , promote new 2008r2 server dc.   rather not go thru steps fix above error if not neccesary.   would error prevent moving fsmo roles , demoting member server or need metadata cleanup with ntdsutil  ?   

regards

craig

 


craig

the above error due problem in disk or abrupt shutdown of dc or corruption in sysvol. if want know more why journal wrap error occurs or how troubleshoot or fix it, refer below link.

http://blogs.technet.com/b/instan/archive/2009/07/14/what-happens-in-a-journal-wrap.aspx

this error should not prevent in transferring fsmo role dc. demoting dc can graceful, if doesn't can use dcpromo /forceremoval followed metadata cleanup. metadata cleanup doesn't remove references of removed dc, might require verify other places  esp in dns, take @ below site, might you.

http://awinish.wordpress.com/2011/05/08/metadata-cleanup-of-a-domain-controller/

also, make sure new dc dns & gc server too. point client has been using windows 2003 dc dns new dc.

don't forget make new dc holding pdcemulator role time server too.

how configure authoritative time server in windows server

http://support.microsoft.com/kb/816042

 

regards


awinish vishwakarma| check blog

disclaimer: posting provided as-is no warranties or guarantees , confers no rights.



Windows Server  >  Directory Services



Comments

Popular posts from this blog

server manager error: ADAM.events.xml could not be enumerated.

Cannot access Anywhere Access using domain name?

WMI Failure: Unable to update Local Resource Group