Not so Ative Directory

  • Thread starter Thread starter Chas
  • Start date Start date
C

Chas

Keep getting these errors after bringing a second
Windows2k dc online. Any ideas???
Event Source: NtFrs
Event Category: None
Event ID: 13565
Date: 1/22/2004
Time: 2:48:19 PM
User: N/A
Computer: AIL2
Description:
File Replication Service is initializing the system volume
with data from another domain controller. Computer AIL2
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:

Event Type: Information
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1557
Date: 1/22/2004
Time: 3:18:06 PM
User: Everyone
Computer: AIL2
Description:
This DRA has never completed a full synchronization of
partition DC=AIL1. It will not be advertised as an
available directory until this condition is met.

This server was recently installed from a source server.
Please verify that that source server is still available
to finish providing data to this system.

The synchronization will be retried.


Event Type: Error
Event Source: SAM
Event Category: None
Event ID: 16650
Date: 1/22/2004
Time: 3:47:07 PM
User: N/A
Computer: AIL2
Description:
The account-identifier allocator failed to initialize
properly. The record data contains the NT error code that
caused the failure. Windows 2000 will retry the
initialization until it succeeds; until that time, account
creation will be denied on this Domain Controller. Please
look for other SAM event logs that may indicate the exact
reason for the failure.
Data:
0000: a7 02 00 c0 §..À

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.


Any help would be greatly appreciated...
Chas
 
See
http://www.microsoft.com/windowsserver2003/technologies/fileandprint/file/dfs/tshootfrs.mspx
for help on triaging FRS. Although the page specifies Windows Server 2003,
many of the tools and concepts apply to Windows 2000. The Ntfrsutl link has
a pointer to a troubleshooting section but I think the FRS Monitoring Help
File may be newer.

I'd first focus on getting your Active Directory replication working (the
1557 error below). I'd use repadmin /showreps to obtain information as to
why the Active Directory replication hasn't finished. Check both the
Configuration naming context and the Domain naming context (ex:
cn=Configuration,dc=microsoft,dc=com and dc=microsoft,dc=com for the
microsoft.com forest). If replication is failing take the error code
returned and resolve that problem. dcdiag may also give you a clue as to
why you aren't replicating. If repadmin doesn't give you any results also
check the eventlog for KCC or DNS errors. Do this on both the server
reporting the error and its replication partner. After you resolve the AD
replication issue restart NTFRS and see if that fixes the FRS issue.

The most common issue blocking AD replication I've seen is misconfigured
DNS. To start have the DNS client settings for both DCs point to the same
DNS server. From the Services MMC snap-in restart the Netlogon service.
That will normally resolve it.

Jason
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


Keep getting these errors after bringing a second
Windows2k dc online. Any ideas???
Event Source: NtFrs
Event Category: None
Event ID: 13565
Date: 1/22/2004
Time: 2:48:19 PM
User: N/A
Computer: AIL2
Description:
File Replication Service is initializing the system volume
with data from another domain controller. Computer AIL2
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:

Event Type: Information
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1557
Date: 1/22/2004
Time: 3:18:06 PM
User: Everyone
Computer: AIL2
Description:
This DRA has never completed a full synchronization of
partition DC=AIL1. It will not be advertised as an
available directory until this condition is met.

This server was recently installed from a source server.
Please verify that that source server is still available
to finish providing data to this system.

The synchronization will be retried.


Event Type: Error
Event Source: SAM
Event Category: None
Event ID: 16650
Date: 1/22/2004
Time: 3:47:07 PM
User: N/A
Computer: AIL2
Description:
The account-identifier allocator failed to initialize
properly. The record data contains the NT error code that
caused the failure. Windows 2000 will retry the
initialization until it succeeds; until that time, account
creation will be denied on this Domain Controller. Please
look for other SAM event logs that may indicate the exact
reason for the failure.
Data:
0000: a7 02 00 c0 §..À

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.


Any help would be greatly appreciated...
Chas
 
Back
Top