|
Question : NTFRS 13555 errors, SYSVOL not replicating
|
|
Hi folks
Sceanario:
SERVER1 - Win 2k Server SP4, DC (holding FSMO roles). Exchange 2003 installed. File server. DNS. AD Int
SERVER2 - Win2003 SP1, DC. File Server
SERVER3 - Win2003 SP1, DC. File Server, DNS AD Integrated.
I dont have DFS setup.
My problem is that the SYSVOL share on SERVER1 isnt replicating to either SERVER2 or SERVER3. AD replication is however taking place. Sysvol replication is working between SERVER2 and SERVER3.
Event logs on SERVER1 show error id 13552 and 13555 once a day:
--------------------------------------------------------------------------------------
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13552
Date: 27/08/2007
Time: 11:53:12
User: N/A
Computer: SERVER
Description:
The File Replication Service is unable to add this computer to the following replica set:
"DATA"
This could be caused by a number of problems such as:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0
The information below may help to resolve the problem:
Computer DNS name is "server.domainname.com"
Replica set member name is "{CE58CCDD-B96C-44F4-81DF-62CEA9720A6D}"
Replica set root path is "d:\data"
Replica staging directory path is "c:\frs-staging"
Replica working directory path is "c:\winnt\ntfrs\jet"
Windows error status code is
FRS error status code is FrsErrorSuccess
------------------------------------------------------------------------------------------------------------------
13555 says the FRS is in an error state and suggests possible steps to take
------------------------------------------------------------------------------------------------------------------
On both SERVER2 and SERVER3 I daily get the event id 13508.
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 17/08/2007
Time: 15:52:03
User: N/A
Computer: WEBSERVER
Description:
The File Replication Service is having trouble enabling replication from SERVER 1to SERVER2 for c:\windows\sysvol\domain using the DNS name server.domainname.com. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name server.domainname.com from this computer.
[2] FRS is not running on server.dominname.com.
[3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
Ok, because the SYSVOL is replicating fine between SERVER2 and SERVER3 I suspect that the ntfrs jet database maybe corrupt on SERVER1. Am I right and how would I confirm this to be so?
This post (http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_21732861.html?sfQueryTermInfo=1+13555+event+id) is similar to mine but doesnt explain how one can ascertain if the ntfrs is actually corrupt.
I'd like to know this before deleting the ntfrs in case its causes my Exchange any problems as happened in this case (http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Windows/2000/Q_21110144.html?sfQueryTermInfo=1+13555+event+id).
When I run dcdiag on SERVER1 I get the following:
Starting test: frssysvol
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
......................... SERVER passed test frssysvol
I've checked the security settings on the SYSVOL folder and all is ok there.
Hopefully I've posted enough information. Seemingly this is a long standing issue but was never touched as everything is working fine (not broken dont fix it) but I'd like to clean up the logs if at all possible as going adding a new file and Exchange box in the near future.
Thanks
|
|
|
Answer : NTFRS 13555 errors, SYSVOL not replicating
|
|
The JRNL_WRAP_ERROR is covered in the KB article 290762.
http://support.microsoft.com/kb/290762
That's probably your best bet. Good luck.
|
|
|
|
|
