Home | Recovery | Cisco How To Net How To | Blog | Search | Forums | Services | Setup Guide | Chicagotech MVP | IT Exam Practice  |  About Us | Contact Us|

 

 

Active Directory issues after migrating domain from Windows 2003 to 2008

Can't open Active Directory Users and Computers, Active Directory Domains and Trusts, Active Directory Sites and Services with an error

Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355

A Global Catalog Server could not be located - All GC's are down.

Event ID 13508: The File Replication Service is having trouble enabling replication from DC2 to DC4 for c:\windows\sysvol\domain using the DNS name

Event ID 13560: Service is deleting this computer from the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" as an attempt to recover from the error state,

Event ID 13561: The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

Situation: Our client had two DCs running on windows 2003. One of them died. They bought a new server running as Windows 2008 DC. Here are what they did:

1. They followed this article to transfer the FSMO to another 2003 DC.

Move the FSMO roles from failed DC to a new DC



2. Run this commands and before install DC on windows 2008
- ADPREP /FORESTPREP
- ADPREP /DOMAINPREP
Also refer to this link:

Prepare for upgrading to windows 2008 domain



3. Transfer FSMO from 2003 dc to 2008 dc by following this page:

How to transfer FSMO in Windows 2008 DC



4. Tested fine. They can create a new user and logon domain without any issue.

Problem: Now, they have these problem:

1. A new user can't logon domain computer with no domain available message.

2. Can't open Active Directory Users and Computers, Active Directory Domains and Trusts, Active Directory Sites and Services with an error as shown.



3. The Windows Event Viewer logs these errors:
Log Name: File Replication Service
Source: NtFrs
Event ID: 13508
Description:
The File Replication Service is having trouble enabling replication from DC2 to DC4 for c:\windows\sysvol\domain using the DNS name DC2.DC.DCgrp.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 DC2.DC.DCgrp.com from this computer.
[2] FRS is not running on DC2.DC.DCgrp.com.
[3] The topology information in the Active Directory Domain Services 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.

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13560
Description:
The File Replication Service is deleting this computer from the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" as an attempt to recover from the error state,
Error status = FrsErrorSuccess
At the next poll, which will occur in 5 minutes, this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13520
Date: 11/10/2011
Time: 9:26:39 AM
User: N/A
Computer: DC2
Description:
The File Replication Service moved the preexisting files in d:\sysvol\domain to d:\sysvol\domain\NtFrs_PreExisting___See_EventLog.

The File Replication Service may delete the files in d:\sysvol\domain\NtFrs_PreExisting___See_EventLog at any time. Files can be saved from deletion by copying them out of d:\sysvol\domain\NtFrs_PreExisting___See_EventLog. Copying the files into d:\sysvol\domain may lead to name conflicts if the files already exist on some other replicating partner.

In some cases, the File Replication Service may copy a file from d:\sysvol\domain\NtFrs_PreExisting___See_EventLog into d:\sysvol\domain instead of replicating the file from some other replicating partner.

Space can be recovered at any time by deleting the files in d:\sysvol\domain\NtFrs_PreExisting___See_EventLog.

Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13561
Date: 11/10/2011
Time: 9:21:39 AM
User: N/A
Computer: DC2
Description:
The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "d:\sysvol\domain"
Replica root volume is : "\\.\D:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.

[1] Volume "\\.\D:" has been formatted.
[2] The NTFS USN journal on volume "\\.\D:" has been deleted.
[3] The NTFS USN journal on volume "\\.\D:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long time.
[5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\D:".

Following recovery steps will be taken to automatically recover from this error state.
[1] At the first poll which will occur in 5 minutes this computer will be deleted from the replica set.
[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13520
Date: 11/10/2011
Time: 9:26:39 AM
User: N/A
Computer: DC2
Description:
The File Replication Service moved the preexisting files in d:\sysvol\domain to d:\sysvol\domain\NtFrs_PreExisting___See_EventLog.

The File Replication Service may delete the files in d:\sysvol\domain\NtFrs_PreExisting___See_EventLog at any time. Files can be saved from deletion by copying them out of d:\sysvol\domain\NtFrs_PreExisting___See_EventLog. Copying the files into d:\sysvol\domain may lead to name conflicts if the files already exist on some other replicating partner.

In some cases, the File Replication Service may copy a file from d:\sysvol\domain\NtFrs_PreExisting___See_EventLog into d:\sysvol\domain instead of replicating the file from some other replicating partner.

Space can be recovered at any time by deleting the files in d:\sysvol\domain\NtFrs_PreExisting___See_EventLog.

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13560
Date: 11/10/2011
Time: 9:21:39 AM
User: N/A
Computer: DC2
Description:
The File Replication Service is deleting this computer from the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" as an attempt to recover from the error state,
Error status = FrsErrorSuccess
At the next poll, which will occur in 5 minutes, this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.

4. dcdiag shows these errors:

Starting test: FsmoCheck
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
A Global Catalog Server could not be located - All GC's are down.
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355
A Good Time Server could not be located.
Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
A KDC could not be located - All the KDCs are down.
......................... DC.DCgrp.com failed test FsmoChec


An error event occurred. EventID: 0x00000406
Time Generated: 11/10/2011 15:18:08
Event String:
The processing of Group Policy failed. Windows attempted to retrieve
new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful.
An error event occurred. EventID: 0x00000422
Time Generated: 11/10/2011 15:31:05
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\DC.DCgrp.com\sysvol\DC.DCgrp.com\Policies\{31B2F
340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following


Troubleshooting: 1. Net share on both DCs doesn't list netlogon and Sysvol share.

2. Active Directory Site and Services doesn't show the Pre-windows 2000 host or NetBIOS name.

Resolution: Re-create Sysvol and Netlogon by following this article:  How to rebuild SYSVOL share and NETLOGON share

Note: As you forcibly removed the old DC, you will need to remove its metadata using NTDSUTIL, removing any DNS entries left behind and then the relevant server object in Sites and Services.

Also please refer to these links for more troubleshooting steps:

AD wizard cannot gain access to list of domains in forest: This problem can occur if a domain controller in the domain has not registered an "A" record for itself in DNS

Active Directory issues after migrating domain from Windows 2003 to 2008: A new user can't logon domain computer with no domain available message.

Active Directory Installation Failed: system can't find file: Error: Active Directory Installation Failed: The operation failed with the following error: The system cannot find the file specified.

Global Catalog Server could not be located: All GC's down: " windows cannot verify that the user name is unique because the following error occurred while trying to contact the global catalog server: The server is not operational ..."

Clients cant join domain: Network location can not be reached: Fatal Error:DsGetDcName (SETE) call failed, error 1722

Post your questions, comments, feedbacks and suggestions

Contact a consultant

Related Topics

 

 

 

Bob Lin Photography services

Real Estate Photography services 

 

  This web is provided "AS IS" with no warranties.
Copyright © 2002-2018 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.