S
Stefan 'Birdie' Vogel
Hello,
we have a 2003 domain with several sites and DCs
All DCs are 2003Std with SP1
until now we never had problems seting up a new DC
Last days I tried to setup some DCs for new locations and got the following
error:
DCPROMO runs without problems
Server is rebooted after DCPROMO
AD-replication running without errors
FRS starts to replicate SYSVOL and filles stageing area and the sysvol
itself
afer several 100MB replication suddenly stops but is not finished.
No entries in eventlog
Only a message (after each restart of FRS) telling that FRS has to fill
SYSVOL with data from another computer
Sometimes after a FRS-service-restart, it is replicating a hand full of
files and stops again.
DNS is running, also time sync.
I tried the BurFlags=D2, resulting in a complete new replication of SYSVOL,
also stoping at approximately the same amount of replicated files.
I also demoted and re-promoted the machine: No change
Has anyone any idea?
Bye
Stefan
Here is a FRSDIAG output from that machine.
------------------------------------------------------------
FRSDiag v1.7 on 7/14/2006 3:19:14 AM
..\AH2C004 on 2006-07-14 at 3.19.14 AM
------------------------------------------------------------
Checking for errors/warnings in FRS Event Log ....
NtFrs 7/14/2006 2:37:00 AM Warning 13565 File Replication Service is
initializing the system volume with data from another domain controller.
Computer AH2C004 cannot become a domain controller until this process is
complete. The system volume will then be shared as SYSVOL. To check for the
SYSVOL share, at the command prompt, type: net share When File Replication
Service completes the initialization process, the SYSVOL share will appear.
The initialization of the system volume can take some time. The time is
dependent on the amount of data in the system volume, the availability of
other domain controllers, and the replication interval between domain
controllers.
NtFrs 7/14/2006 2:29:50 AM Warning 13565 File Replication Service is
initializing the system volume with data from another domain controller.
Computer AH2C004 cannot become a domain controller until this process is
complete. The system volume will then be shared as SYSVOL. To check for the
SYSVOL share, at the command prompt, type: net share When File Replication
Service completes the initialization process, the SYSVOL share will appear.
The initialization of the system volume can take some time. The time is
dependent on the amount of data in the system volume, the availability of
other domain controllers, and the replication interval between domain
controllers.
NtFrs 7/13/2006 6:44:36 AM Warning 13565 File Replication Service is
initializing the system volume with data from another domain controller.
Computer AH2C004 cannot become a domain controller until this process is
complete. The system volume will then be shared as SYSVOL. To check for the
SYSVOL share, at the command prompt, type: net share When File Replication
Service completes the initialization process, the SYSVOL share will appear.
The initialization of the system volume can take some time. The time is
dependent on the amount of data in the system volume, the availability of
other domain controllers, and the replication interval between domain
controllers.
.......... failed 3
Checking for errors in Directory Service Event Log .... passed
Checking for minimum FRS version requirement ... passed
Checking for errors/warnings in ntfrsutl ds ... passed
Checking for Replica Set configuration triggers... passed
Checking for suspicious file Backlog size...
ERROR : File Backlog TO server "AUTO\FR2C002$" is : 8794 :: Unless this is
due to your schedule, this is a problem!
ERROR : File Backlog TO server "AUTO\MO2C002$" is : 8794 :: Unless this is
due to your schedule, this is a problem!
failed with 2 error(s) and 0 warning(s)
Checking Overall Disk Space and SYSVOL structure (note: integrity is not
checked)... passed
Checking for suspicious inlog entries ... passed
Checking for suspicious outlog entries ... passed
Checking for appropriate staging area size ... passed
Checking for errors in debug logs ...
ERROR on NtFrs_0002.log : "IBCO_FETCH_RETRY" : 7/13-10:39:16 :T: LocnCmd:
Create State: IBCO_FETCH_RETRY ReplicaName: DOMAIN SYSTEM VOLUME (SYSVOL
SHARE) (1)
ERROR on NtFrs_0004.log : "IBCO_FETCH_RETRY" : 7/14-02:36:44 :T: LocnCmd:
Create State: IBCO_FETCH_RETRY ReplicaName: DOMAIN SYSTEM VOLUME (SYSVOL
SHARE) (1)
Found 2 IBCO_FETCH_RETRY error(s)! Latest ones (up to 3) listed above
.......... failed with 2 error entries
Checking NtFrs Service (and dependent services) state...
ERROR : Cannot access SYSVOL share on AH2C004
ERROR : Cannot access NETLOGON share on AH2C004
.......... failed 2
Checking NtFrs related Registry Keys for possible problems...
SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\SysvolReady = 0 ::
ERROR: SysvolReady is not set to 1 :: SYSVOL is likely not Sharing! This key
should NOT be changed manually but this should be addressed! See article
KB.327781 (How to Troubleshoot Missing SYSVOL and NETLOGON Shares on Windows
Server) for further information!
failed with 1 error(s) and 0 warning(s)
Checking Repadmin Showreps for errors...passed
Final Result = failed with 10 error(s)
we have a 2003 domain with several sites and DCs
All DCs are 2003Std with SP1
until now we never had problems seting up a new DC
Last days I tried to setup some DCs for new locations and got the following
error:
DCPROMO runs without problems
Server is rebooted after DCPROMO
AD-replication running without errors
FRS starts to replicate SYSVOL and filles stageing area and the sysvol
itself
afer several 100MB replication suddenly stops but is not finished.
No entries in eventlog
Only a message (after each restart of FRS) telling that FRS has to fill
SYSVOL with data from another computer
Sometimes after a FRS-service-restart, it is replicating a hand full of
files and stops again.
DNS is running, also time sync.
I tried the BurFlags=D2, resulting in a complete new replication of SYSVOL,
also stoping at approximately the same amount of replicated files.
I also demoted and re-promoted the machine: No change
Has anyone any idea?
Bye
Stefan
Here is a FRSDIAG output from that machine.
------------------------------------------------------------
FRSDiag v1.7 on 7/14/2006 3:19:14 AM
..\AH2C004 on 2006-07-14 at 3.19.14 AM
------------------------------------------------------------
Checking for errors/warnings in FRS Event Log ....
NtFrs 7/14/2006 2:37:00 AM Warning 13565 File Replication Service is
initializing the system volume with data from another domain controller.
Computer AH2C004 cannot become a domain controller until this process is
complete. The system volume will then be shared as SYSVOL. To check for the
SYSVOL share, at the command prompt, type: net share When File Replication
Service completes the initialization process, the SYSVOL share will appear.
The initialization of the system volume can take some time. The time is
dependent on the amount of data in the system volume, the availability of
other domain controllers, and the replication interval between domain
controllers.
NtFrs 7/14/2006 2:29:50 AM Warning 13565 File Replication Service is
initializing the system volume with data from another domain controller.
Computer AH2C004 cannot become a domain controller until this process is
complete. The system volume will then be shared as SYSVOL. To check for the
SYSVOL share, at the command prompt, type: net share When File Replication
Service completes the initialization process, the SYSVOL share will appear.
The initialization of the system volume can take some time. The time is
dependent on the amount of data in the system volume, the availability of
other domain controllers, and the replication interval between domain
controllers.
NtFrs 7/13/2006 6:44:36 AM Warning 13565 File Replication Service is
initializing the system volume with data from another domain controller.
Computer AH2C004 cannot become a domain controller until this process is
complete. The system volume will then be shared as SYSVOL. To check for the
SYSVOL share, at the command prompt, type: net share When File Replication
Service completes the initialization process, the SYSVOL share will appear.
The initialization of the system volume can take some time. The time is
dependent on the amount of data in the system volume, the availability of
other domain controllers, and the replication interval between domain
controllers.
.......... failed 3
Checking for errors in Directory Service Event Log .... passed
Checking for minimum FRS version requirement ... passed
Checking for errors/warnings in ntfrsutl ds ... passed
Checking for Replica Set configuration triggers... passed
Checking for suspicious file Backlog size...
ERROR : File Backlog TO server "AUTO\FR2C002$" is : 8794 :: Unless this is
due to your schedule, this is a problem!
ERROR : File Backlog TO server "AUTO\MO2C002$" is : 8794 :: Unless this is
due to your schedule, this is a problem!
failed with 2 error(s) and 0 warning(s)
Checking Overall Disk Space and SYSVOL structure (note: integrity is not
checked)... passed
Checking for suspicious inlog entries ... passed
Checking for suspicious outlog entries ... passed
Checking for appropriate staging area size ... passed
Checking for errors in debug logs ...
ERROR on NtFrs_0002.log : "IBCO_FETCH_RETRY" : 7/13-10:39:16 :T: LocnCmd:
Create State: IBCO_FETCH_RETRY ReplicaName: DOMAIN SYSTEM VOLUME (SYSVOL
SHARE) (1)
ERROR on NtFrs_0004.log : "IBCO_FETCH_RETRY" : 7/14-02:36:44 :T: LocnCmd:
Create State: IBCO_FETCH_RETRY ReplicaName: DOMAIN SYSTEM VOLUME (SYSVOL
SHARE) (1)
Found 2 IBCO_FETCH_RETRY error(s)! Latest ones (up to 3) listed above
.......... failed with 2 error entries
Checking NtFrs Service (and dependent services) state...
ERROR : Cannot access SYSVOL share on AH2C004
ERROR : Cannot access NETLOGON share on AH2C004
.......... failed 2
Checking NtFrs related Registry Keys for possible problems...
SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\SysvolReady = 0 ::
ERROR: SysvolReady is not set to 1 :: SYSVOL is likely not Sharing! This key
should NOT be changed manually but this should be addressed! See article
KB.327781 (How to Troubleshoot Missing SYSVOL and NETLOGON Shares on Windows
Server) for further information!
failed with 1 error(s) and 0 warning(s)
Checking Repadmin Showreps for errors...passed
Final Result = failed with 10 error(s)