Dcdiag error "There are errors after SYSVOL has been shared"

[Anthony Litterio]

I keep getting this error. I did the preperations last night for
introducing Windows server 2003 into the existing Windows 2000 server AD,
and ran dcdiag and all tests passed afterward.

I ran dcdiag /e /test:frssysvol and all of the other DC's are Okay. How do
I fix this?

Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... RPMFCHI2 passed test frssysvol

 

[ptwilliams]

Have a look for warnings and errors located in the File Replication System
event log on the troublesome DC. If you can't work out what's happening
with them, post them here.


--

Paul Williams

http://www.msresource.net
http://forums.msresource.net


I keep getting this error. I did the preperations last night for
introducing Windows server 2003 into the existing Windows 2000 server AD,
and ran dcdiag and all tests passed afterward.

I ran dcdiag /e /test:frssysvol and all of the other DC's are Okay. How do
I fix this?

Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... RPMFCHI2 passed test frssysvol

 

[Anthony Litterio]

I am getting these two errors, but they were last night; there is nothing
today.

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 11/10/2004
Time: 7:53:13 PM
User: N/A
Computer: RPMFCHI2
Description:
The File Replication Service is having trouble enabling replication from
RLCHI02 to RPMFCHI2 for c:\winnt\sysvol\domain using the DNS name
rlchi02.rusinpatton.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 rlchi02.rusinpatton.com from
this computer.
[2] FRS is not running on rlchi02.rusinpatton.com.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the
connection has been established.
Data:
0000: ba 06 00 00 º...
---------------------------------------------------------------------------

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13509
Date: 11/10/2004
Time: 8:00:17 PM
User: N/A
Computer: RPMFCHI2
Description:
The File Replication Service has enabled replication from RLCHI02 to
RPMFCHI2 for c:\winnt\sysvol\domain after repeated retries.

 

[ptwilliams]

13509 is saying, 13508 is now fixed. But it took a while, thus I'm letting
you know : )

What's the problem???


--

Paul Williams

http://www.msresource.net
http://forums.msresource.net


I am getting these two errors, but they were last night; there is nothing
today.

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 11/10/2004
Time: 7:53:13 PM
User: N/A
Computer: RPMFCHI2
Description:
The File Replication Service is having trouble enabling replication from
RLCHI02 to RPMFCHI2 for c:\winnt\sysvol\domain using the DNS name
rlchi02.rusinpatton.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 rlchi02.rusinpatton.com from
this computer.
[2] FRS is not running on rlchi02.rusinpatton.com.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the
connection has been established.
Data:
0000: ba 06 00 00 º...
---------------------------------------------------------------------------

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13509
Date: 11/10/2004
Time: 8:00:17 PM
User: N/A
Computer: RPMFCHI2
Description:
The File Replication Service has enabled replication from RLCHI02 to
RPMFCHI2 for c:\winnt\sysvol\domain after repeated retries.