replication error

[Guest]

Error Code 13508

2 win2k DC's

DC 1

dcdiag /v error results:

Starting test: frssysvol
* The File Replication Service Event log test
The SYSVOL has been shared, and the AD is no longer
prevented from starting by the File Replication Service.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
An Warning Event occured. EventID: 0x800034C4
Time Generated: 04/07/2006 13:36:41
Event String: The File Replication Service is having trouble
enabling replication from FILESERVER to
TESTSERVER for c:\winnt\sysvol\domain using the
DNS name fileserver.DAEOFFICE.LOCAL. FRS will
keep retrying.
Following are some of the reasons you would see
this warning.

[1] FRS can not correctly resolve the DNS name
fileserver.DAEOFFICE.LOCAL from this computer.
[2] FRS is not running on
fileserver.DAEOFFICE.LOCAL.
[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.
......................... TESTSERVER passed test frssysvol

netdiag error results:

Starting test: frssysvol
* The File Replication Service Event log test
The SYSVOL has been shared, and the AD is no longer
prevented from starting by the File Replication Service.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
An Warning Event occured. EventID: 0x800034C4
Time Generated: 04/07/2006 13:36:41
Event String: The File Replication Service is having trouble
enabling replication from FILESERVER to
TESTSERVER for c:\winnt\sysvol\domain using the
DNS name fileserver.DAEOFFICE.LOCAL. FRS will
keep retrying.
Following are some of the reasons you would see
this warning.

[1] FRS can not correctly resolve the DNS name
fileserver.DAEOFFICE.LOCAL from this computer.
[2] FRS is not running on
fileserver.DAEOFFICE.LOCAL.
[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.
......................... TESTSERVER passed test frssysvol


DC2

dcdiag \v

Starting test: frssysvol
* The File Replication Service Event log test
The SYSVOL has been shared, and the AD is no longer
prevented from starting by the File Replication Service.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
An Warning Event occured. EventID: 0x800034C4
Time Generated: 04/07/2006 16:57:02
Event String: The File Replication Service is having trouble
enabling replication from TESTSERVER to
FILESERVER for c:\winnt\sysvol\domain using the
DNS name testserver.DAEOFFICE.LOCAL. FRS will
keep retrying.
Following are some of the reasons you would see
this warning.

[1] FRS can not correctly resolve the DNS name
testserver.DAEOFFICE.LOCAL from this computer.
[2] FRS is not running on
testserver.DAEOFFICE.LOCAL.
[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.
......................... FILESERVER passed test frssysvol


Any ideas?

 

[Herb Martin]

dcdiag /v error results:
Starting test: frssysvol

Any ideas?

Yes, the three mentioned are a good starting point:

[1] FRS can not correctly resolve the DNS name
fileserver.DAEOFFICE.LOCAL from this computer.
[2] FRS is not running on
fileserver.DAEOFFICE.LOCAL.
[3] The topology information in the Active
Directory for this replica has not yet replicated
to all the Domain Controllers.

Consider that the vast majority of Replication (and Authentication)
errors are really DNS problems and start there.

[One caveat though about this virtual rule: If AD replicaton IS
working and only FRS is failing then usually this exonerates DNS.]

You didn't include the DNS sections of DCDiag (I usually just run
it without the /v], and perhaps you haven't tried the obvious /f (fix)
to let DCDiag try to repair DNS issues.

You can easily check that the service is running on both DCs.
And you can with a bit more difficulty determine if you have a
full replication topology by inspecting AD Sites and Services or
using the replication tools (ReplMon and RepAdmin).

As to DNS double-check the DNS principles outlined below and
if that doesn't work describe (specifically) your DNS setup, including
which DC is Primary/Secondary (or which ARE AD Integrated) and
confirm that the zone is set for Dynamic updates and that ALL DCs
are using (on NIC->IP Properties) STRICTLY the (internal) DNS
server (set) which can resolve those AD DNS names.


DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)

netdiag /fix

....or maybe:

dcdiag /fix

(Win2003 can do this from Support tools):
nltest /dsregdns /serverC-ServerNameGoesHere
http://support.microsoft.com/kb/q260371/

Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.

Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.

Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

[1] FRS can not correctly resolve the DNS name
fileserver.DAEOFFICE.LOCAL from this computer.
[2] FRS is not running on
fileserver.DAEOFFICE.LOCAL.
[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.
......................... TESTSERVER passed test frssysvol

netdiag error results:

Starting test: frssysvol
* The File Replication Service Event log test
The SYSVOL has been shared, and the AD is no longer
prevented from starting by the File Replication Service.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
An Warning Event occured. EventID: 0x800034C4
Time Generated: 04/07/2006 13:36:41
Event String: The File Replication Service is having trouble
enabling replication from FILESERVER to
TESTSERVER for c:\winnt\sysvol\domain using the
DNS name fileserver.DAEOFFICE.LOCAL. FRS will
keep retrying.
Following are some of the reasons you would see
this warning.

[1] FRS can not correctly resolve the DNS name
fileserver.DAEOFFICE.LOCAL from this computer.
[2] FRS is not running on
fileserver.DAEOFFICE.LOCAL.
[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.
......................... TESTSERVER passed test frssysvol


DC2

dcdiag \v

Starting test: frssysvol
* The File Replication Service Event log test
The SYSVOL has been shared, and the AD is no longer
prevented from starting by the File Replication Service.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
An Warning Event occured. EventID: 0x800034C4
Time Generated: 04/07/2006 16:57:02
Event String: The File Replication Service is having trouble
enabling replication from TESTSERVER to
FILESERVER for c:\winnt\sysvol\domain using the
DNS name testserver.DAEOFFICE.LOCAL. FRS will
keep retrying.
Following are some of the reasons you would see
this warning.

[1] FRS can not correctly resolve the DNS name
testserver.DAEOFFICE.LOCAL from this computer.
[2] FRS is not running on
testserver.DAEOFFICE.LOCAL.
[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.
......................... FILESERVER passed test frssysvol


Any ideas?

 

[Guest]

found & fixed the problem. thanks!

dcdiag /v error results:
Starting test: frssysvol

Any ideas?

Yes, the three mentioned are a good starting point:

[1] FRS can not correctly resolve the DNS name
fileserver.DAEOFFICE.LOCAL from this computer.
[2] FRS is not running on
fileserver.DAEOFFICE.LOCAL.
[3] The topology information in the Active
Directory for this replica has not yet replicated
to all the Domain Controllers.

Consider that the vast majority of Replication (and Authentication)
errors are really DNS problems and start there.

[One caveat though about this virtual rule: If AD replicaton IS
working and only FRS is failing then usually this exonerates DNS.]

You didn't include the DNS sections of DCDiag (I usually just run
it without the /v], and perhaps you haven't tried the obvious /f (fix)
to let DCDiag try to repair DNS issues.

You can easily check that the service is running on both DCs.
And you can with a bit more difficulty determine if you have a
full replication topology by inspecting AD Sites and Services or
using the replication tools (ReplMon and RepAdmin).

As to DNS double-check the DNS principles outlined below and
if that doesn't work describe (specifically) your DNS setup, including
which DC is Primary/Secondary (or which ARE AD Integrated) and
confirm that the zone is set for Dynamic updates and that ALL DCs
are using (on NIC->IP Properties) STRICTLY the (internal) DNS
server (set) which can resolve those AD DNS names.


DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)

netdiag /fix

....or maybe:

dcdiag /fix

(Win2003 can do this from Support tools):
nltest /dsregdns /serverC-ServerNameGoesHere
http://support.microsoft.com/kb/q260371/

Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.

Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.

Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

[1] FRS can not correctly resolve the DNS name
fileserver.DAEOFFICE.LOCAL from this computer.
[2] FRS is not running on
fileserver.DAEOFFICE.LOCAL.
[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.
......................... TESTSERVER passed test frssysvol

netdiag error results:

Starting test: frssysvol
* The File Replication Service Event log test
The SYSVOL has been shared, and the AD is no longer
prevented from starting by the File Replication Service.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
An Warning Event occured. EventID: 0x800034C4
Time Generated: 04/07/2006 13:36:41
Event String: The File Replication Service is having trouble
enabling replication from FILESERVER to
TESTSERVER for c:\winnt\sysvol\domain using the
DNS name fileserver.DAEOFFICE.LOCAL. FRS will
keep retrying.
Following are some of the reasons you would see
this warning.

[1] FRS can not correctly resolve the DNS name
fileserver.DAEOFFICE.LOCAL from this computer.
[2] FRS is not running on
fileserver.DAEOFFICE.LOCAL.
[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.
......................... TESTSERVER passed test frssysvol


DC2

dcdiag \v

Starting test: frssysvol
* The File Replication Service Event log test
The SYSVOL has been shared, and the AD is no longer
prevented from starting by the File Replication Service.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
An Warning Event occured. EventID: 0x800034C4
Time Generated: 04/07/2006 16:57:02
Event String: The File Replication Service is having trouble
enabling replication from TESTSERVER to
FILESERVER for c:\winnt\sysvol\domain using the
DNS name testserver.DAEOFFICE.LOCAL. FRS will
keep retrying.
Following are some of the reasons you would see
this warning.

[1] FRS can not correctly resolve the DNS name
testserver.DAEOFFICE.LOCAL from this computer.
[2] FRS is not running on
testserver.DAEOFFICE.LOCAL.
[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.
......................... FILESERVER passed test frssysvol


Any ideas?

 

[Herb Martin]

found & fixed the problem. thanks!

What was the problem?

It is generally a good idea to explain what you found
and how you fixed it so that others may benefit and that
those who try to help will know if the advice covered
the problem or needs to be expanded/modified.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

found & fixed the problem. thanks!

dcdiag /v error results:
Starting test: frssysvol

Any ideas?

Yes, the three mentioned are a good starting point:

[1] FRS can not correctly resolve the DNS name
fileserver.DAEOFFICE.LOCAL from this computer.
[2] FRS is not running on
fileserver.DAEOFFICE.LOCAL.
[3] The topology information in the Active
Directory for this replica has not yet replicated
to all the Domain Controllers.

Consider that the vast majority of Replication (and Authentication)
errors are really DNS problems and start there.

[One caveat though about this virtual rule: If AD replicaton IS
working and only FRS is failing then usually this exonerates DNS.]

You didn't include the DNS sections of DCDiag (I usually just run
it without the /v], and perhaps you haven't tried the obvious /f (fix)
to let DCDiag try to repair DNS issues.

You can easily check that the service is running on both DCs.
And you can with a bit more difficulty determine if you have a
full replication topology by inspecting AD Sites and Services or
using the replication tools (ReplMon and RepAdmin).

As to DNS double-check the DNS principles outlined below and
if that doesn't work describe (specifically) your DNS setup, including
which DC is Primary/Secondary (or which ARE AD Integrated) and
confirm that the zone is set for Dynamic updates and that ALL DCs
are using (on NIC->IP Properties) STRICTLY the (internal) DNS
server (set) which can resolve those AD DNS names.


DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or
indirectly)

netdiag /fix

....or maybe:

dcdiag /fix

(Win2003 can do this from Support tools):
nltest /dsregdns /serverC-ServerNameGoesHere
http://support.microsoft.com/kb/q260371/

Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.

Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.

Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

[1] FRS can not correctly resolve the DNS name
fileserver.DAEOFFICE.LOCAL from this computer.
[2] FRS is not running on
fileserver.DAEOFFICE.LOCAL.
[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.
......................... TESTSERVER passed test frssysvol

netdiag error results:

Starting test: frssysvol
* The File Replication Service Event log test
The SYSVOL has been shared, and the AD is no longer
prevented from starting by the File Replication Service.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
An Warning Event occured. EventID: 0x800034C4
Time Generated: 04/07/2006 13:36:41
Event String: The File Replication Service is having trouble
enabling replication from FILESERVER to
TESTSERVER for c:\winnt\sysvol\domain using the
DNS name fileserver.DAEOFFICE.LOCAL. FRS will
keep retrying.
Following are some of the reasons you would see
this warning.

[1] FRS can not correctly resolve the DNS name
fileserver.DAEOFFICE.LOCAL from this computer.
[2] FRS is not running on
fileserver.DAEOFFICE.LOCAL.
[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.
......................... TESTSERVER passed test frssysvol


DC2

dcdiag \v

Starting test: frssysvol
* The File Replication Service Event log test
The SYSVOL has been shared, and the AD is no longer
prevented from starting by the File Replication Service.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
An Warning Event occured. EventID: 0x800034C4
Time Generated: 04/07/2006 16:57:02
Event String: The File Replication Service is having trouble
enabling replication from TESTSERVER to
FILESERVER for c:\winnt\sysvol\domain using the
DNS name testserver.DAEOFFICE.LOCAL. FRS will
keep retrying.
Following are some of the reasons you would see
this warning.

[1] FRS can not correctly resolve the DNS name
testserver.DAEOFFICE.LOCAL from this computer.
[2] FRS is not running on
testserver.DAEOFFICE.LOCAL.
[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.
......................... FILESERVER passed test frssysvol


Any ideas?