Replication Problems

[tjb]

If your Ntfrs jet database is corrupt or missing then replication will break. This is usually found in c:\Windows\ntfrs\jet. Usually though the File Replication Service will refuse to start if it can't locate the database.

[FN-GM]

If your Ntfrs jet database is corrupt or missing then replication will break. This is usually found in c:\Windows\ntfrs\jet. Usually though the File Replication Service will refuse to start if it can't locate the database.

 

the service seems to be going, im going to try what chris suggested and see what i can do.

 

im hoping that i dont have to rebuild the domain.

 

thanks

 

Z

 

PS: Who ever has the solution will get lots of beer

Edited January 21, 2009 by FN-GM
Ps part

[SYNACK]

You could try this:

 

Copy the contents of the netlogon folder, demote the affected machine (after role transfer) then rejoin, wait for AD to sync up and then copy the files back into netlogon which should go live when AD is properly synced up

[FN-GM]

You could try this:

 

Copy the contents of the netlogon folder, demote the affected machine (after role transfer) then rejoin, wait for AD to sync up and then copy the files back into netlogon which should go live when AD is properly synced up

 

What if i manually copy sysvol to the other DC and then demote the problematic one will that cause sysvol to kick in again on all DC's? What if it doesn't will it all go wrong? I know you should never do this but before i try should i take a snapshot of the DC, it can't make it any worse lol.

 

Thanks for all your help

 

Z

[SYNACK]

If the policies are all still working on the others sysvol should be fine. Have you imaged one of the servers lately. That is what usually causes this error. I am unsure whether the direct copy of it all would work but would probably not try it myself as the revision numbers etc would be different.

 

I would use the VM converter to grab a VM of the one with sysvol and see if it has the same issues in a virtual environment then I would try the steps on that first.

 

I would try taking a system state backup then doing an authorotive restore on the VM to see whether that resets enough of the flags to get it working again. If it did work then I would attempt it on teh propper DC after a backup

[FN-GM]

Hi, on the other servers there are no sysvol shares at all.

 

Not touched the servers, the only thing i did was demote a DC and all this happened.

 

Already in a VM environment will make a copy and try on the internal network.

 

ok so if i make a backup and imediently restore it should fix it?

 

thanks for the tips

 

Z

[webman]

What caused them not to replicate in the first place?

[FN-GM]

No idea, i wish i did know nothing in the event log to indicate why. It happened when i demoted a DC.

 

I had another possible solution, demote the bad DC and rebuild the sysvol like this - Windows Technical Issues Blog: How to rebuild the SYSVOL tree when none exists in Active Directory

 

what will actually need rebuilding? will it be the group policies? I take it users will be fine? Has anyone done this before?

 

Thanks

 

Z

[bossman]

@FN-GM:

I had a similar problem when one of my DCs went down unexpectedly due to a bios chip corruption.

Both running win2ksp4

When eventually got it back up forgot to set the time in the bios (due to oversite and pressure to get back up) and this caused the NTFRS to time out and this is what i think has happened to yours as it cannot connect to the other DCs which it replicates with.

All I can say is that it is fiddley but if you search for NTFRS timeout in google for the type servers you have I am sure you will find what you are looking for.

 

good luck :-)

 

Have just seen your post and this is what i had to do :-)

Edited January 21, 2009 by bossman

[FN-GM]

@FN-GM:

I had a similar problem when one of my DCs went down unexpectedly due to a bios chip corruption.

Both running win2ksp4

When eventually got it back up forgot to set the time in the bios (due to oversite and pressure to get back up) and this caused the NTFRS to time out and this is what i think has happened to yours as it cannot connect to the other DCs which it replicates with.

All I can say is that it is fiddley but if you search for NTFRS timeout in google for the type servers you have I am sure you will find what you are looking for.

 

good luck :-)

 

Thanks bossman, it is a VM so i know it wasn't what you said. I will have a look, how easy was it to fix?

 

I have managed to get AD replicating i just the those errors and sysvol is messed up.

 

thanks

 

z

[FN-GM]

Would i be going the best way about it demoting the problem DC and then rebuilding sysvol on the other?

 

Thanks