Active directory not replicating

Server 2008r2. After power failure we noticed that dns zone won't load on the server holding FSMO role. DNS error logs indicated Event IDs 4521, 4004 and 4015 which all pointed to error replicating AD. The AD errors on the other hand have Event ID errors 2108, 448, 447, 1084. This causes ad objects not replicate changes across all other DCs, etc. How do we fix this? Thanks.
nfinorthitAsked:
Who is Participating?
 
AmitIT ArchitectCommented:
It was suggested to move FSMO role to another DC, then demote and re-promote this server. Will this work?

If you have another DC, then yes it will work. Also, I don't feel, this will cause issue on files stored on another partition. However, backup is key. So backup your data and then take necessary action.
0
 
Neadom TuckerCommented:
So this is typically due to a corrupt or dirty shutdown.  Your DFRS event logs should tell you something about this and have you run a command in an elevated command to start the replication again.  What domain functional level are you running at?

If your at 2008R2 take a look at this:
http://blogs.technet.com/b/thbouche/archive/2013/08/28/dfsr-sysvol-authoritative-non-authoritative-restore-powershell-functions.aspx

Also look in your DFSR event logs as well.  They should give you a clue or post them here.
0
 
nfinorthitAuthor Commented:
I believe functional level is 2003, although all our servers are 2008. We are not looking to raise level as it obviously wasn't the cause of this mess. We need to know what exactly do we need to do to remedy this. DFSR logs don't have any entries past the power failure; messages before the failure are strictly information, - no warnings et.al. It was recommended that we move FSMO role to another functioning DC, demote problem DC and then promote it back to DC. Is this something that can be done?
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
AmitIT ArchitectCommented:
Call MS, before you try any other step. Error indicates AD corruption issue. Rebuilding could be the last option. Check this:
http://eniackb.blogspot.in/2009/06/active-directory-database.html
0
 
nfinorthitAuthor Commented:
It was suggested to move FSMO role to another DC, then demote and re-promote this server. Will this work? While demoting/promoting the server, will users have access to files that are stored on the server in a separate partition? (except reboot time, of course)
0
 
nfinorthitAuthor Commented:
Yes, we do have a backup. What I meant is this. If I demote server, then it becomes just a standalone server. Will shares on it remain share/ntfs permissions and allow users to access the files during the process, except when I am rebooting the server?
0
 
AmitIT ArchitectCommented:
Such changes should be done during non-production hours. So, there are no user impact.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.