This is the last FRS event log, all directories listed are present,
the file system is NTFS with SP4.
The File Replication Service is unable to add this computer to the following
replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
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 "ecpdc.police.lancco.pa.us"
Replica set member name is "ECPDC"
Replica set root path is "c:\winnt\sysvol\domain"
Replica staging directory path is "c:\winnt\sysvol\staging\domain"
Replica working directory path is "c:\winnt\ntfrs\jet"
Windows error status code is ERROR_INVALID_HANDLE
FRS error status code is FrsErrorNotFound
Other event log messages may also help determine the problem. Correct the
problem and the service will attempt to restart replication automatically at
a later time.
this is the last FRS event log on PSDC1, I can resolve
ecpdc.police.lancco.pa.us from PSDC1, the FRS service is running on ecpdc.
The File Replication Service is having trouble enabling replication from
ECPDC to PSDC1 for c:\winnt\sysvol\domain using the DNS name
ecpdc.police.lancco.pa.us. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name ecpdc.police.lancco.pa.us
from this computer.
[2] FRS is not running on ecpdc.police.lancco.pa.us.
[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.
This is a previous entry from the FRS event log on PSDC1, I don't
understand exactly what it means
Following is the summary of warnings and errors encountered by File
Replication Service while polling the Domain Controller
psdc1.police.lancco.pa.us for FRS replica set configuration information.
The nTDSConnection object cn=c6e774a3-afd0-48a9-864c-38a8c99b3ac6,cn=ntds
settings,cn=ecpdc,cn=servers,cn=eastcocalicopd,cn=sites,cn=configuration,dc=
lancco,dc=root is conflicting with cn=psdc1,cn=ntds
settings,cn=ecpdc,cn=servers,cn=eastcocalicopd,cn=sites,cn=configuration,dc=
lancco,dc=root. Using cn=c6e774a3-afd0-48a9-864c-38a8c99b3ac6,cn=ntds
settings,cn=ecpdc,cn=servers,cn=eastcocalicopd,cn=sites,cn=configuration,dc=
lancco,dc=root
-----Original Message-----
From: Siddharth Sawkar [mailto:[EMAIL PROTECTED]
Sent: Friday, August 29, 2003 1:02 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] sysvol not replicating
Don't dcpromo down and back up- you will just waste your time.
What are the last events in the FRS event logs.
If EVERYTHING else is perfect, we can check the registry to see what your
seeding server is. If it doesn't have any problems, we can do a non-auth
restore which will be the quickest way back up (flip a reg key and bounce
the ntfrs service).
/Siddharth
On Fri, 29 Aug 2003, Simon Geary wrote:
> No, that would be the worse possible thing you could do! You should never
> manually copy any FRS replicated data over as that could trigger a full
> replication of Sysvol and bring your network down to a crawl. If FRS isn't
> working, look for the root cause and fix that instead, don't try any
> shortcuts.
>
> The main thing to check is the components that FRS relies on, mainly DNS.
> How does the DNS configuration look, can you resolve names to\from that
> server? DNS misconfiguration should be the first possible cause you focus
on
> as it is the most common.
>
> Other troubleshooting steps:
> Check all event logs for associated errors. Any jrnl_wrap or FRS\DNS
related
> pointers?
> dcdiag /v
> netdiag /v
> repadmin /showreps (should have at least one inbound and outbound partner)
>
> Do any of these point you towards the problem?
>
> If you are unable to track down the source of the problem you can always
> give up and start again, which is actually not so bad as it sounds. If the
> FRS problem can't be resolved, dcpromo back to a member server, double
check
> DNS settings and then attempt the promotion again.
>
> Simon Geary
> MVP
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Rittenhouse,
> Cindy
> Sent: 29 August 2003 16:33
> To: [EMAIL PROTECTED]
> Subject: [ActiveDir] sysvol not replicating
>
>
> Two days ago a consulting firm upgraded a BDC at a remote location to
> Windows 2000. After the upgrade users had all types of trouble connecting.
> It seems the sysvol is not replicating because the
> Do_Not_Remove_NtFrs_PreInstall_Directory, Policies directory, and Scripts
> directory do not exist on the remote server in either the sysvol\domain or
> the sysvol\sysvol directory. The rest of AD seems to be replicating fine.
> Can I simply copy those directories from one of my DCs to the DC in the
> remote location?
> Thanks
>
> Cynthia Rittenhouse MCSE,CCNA
> LAN Administrator
> County of Lancaster
> Lancaster, PA 17602
>
>
> List info : http://www.activedir.org/mail_list.htm
> List FAQ : http://www.activedir.org/list_faq.htm
> List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
>
> List info : http://www.activedir.org/mail_list.htm
> List FAQ : http://www.activedir.org/list_faq.htm
> List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
>
List info : http://www.activedir.org/mail_list.htm
List FAQ : http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
List info : http://www.activedir.org/mail_list.htm
List FAQ : http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
