Two SYSVOL share or SYSVOL error

Sometimes you may get in a situation where you have two-two SYSVOL shares and you don't know which one is working and replicating information to other domain controllers.

No problem - sometimes SYSVOL may not be working properly and you get JOURNAL_Wrap error messages on domain controller. When FRS activates itself to replicate contents of SYSVOL to other domain controller it searches registry to find the correct path of SYSVOL. Registry contains the information such as SYSVOL folder location, SYSVOL share name etc. These information are supplied back to FRS to replicate its contents to other domain controller - Well! here is the problem - FRS says: "I don't know what is what : This SYSVOL folder is not the one I'm looking for". Folder have missing information. Now you're stuck up here! Can't go any more, can't do anything with the system. FRSs second step to check DNS for SRV records registered by domain controller - that's the other problem if it can't find other DCs using DNS - that's not the matter here.
�
Microsoft has written an article on Troubleshooting SYSVOL:
�
Check out here:
�
http://support.microsoft.com/kb/316790
�
D4 registry entry in above article makes this domain controller authoritativ for whole SYSVOL share.
�
Also check: Troubleshooting Missing SYSVOL and Netlogon shares:
�
http://support.microsoft.com/kb/257338

Microsoft corporation and/or its respective suppliers make no representations about the suitability, reliability, or accuracy of the information and related graphics contained herein. All such information and related graphics are provided "as is" without warranty of any kind. Microsoft and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information and related graphics, including all implied warranties and conditions of merchantability, fitness for a particular purpose, workmanlike effort, title and non-infringement. You specifically agree that in no event shall Microsoft and/or its suppliers be liable for any direct, indirect, punitive, incidental, special, consequential damages or any damages whatsoever including, without limitation, damages for loss of use, data or profits, arising out of or in any way connected with the use of or inability to use the information and related graphics contained herein, whether based on contract, tort, negligence, strict liability or otherwise, even if Microsoft or any of its suppliers has been advised of the possibility of damages.