SBS 2003 to Server 2012 migration issues

We have a customer who will soon be moving from an SBS 2003 domain to a 2012 R2 domain with Exchange 2013. I am testing this in a virtual scenario first. I have taken a copy of their SBS2003 server and am now running it in Hyper-V. I have created a second Hyper-V guest with Server 2012 R2

So far, I have joined the 2012 server to the domain as a member server, then I installed Active Directory Domain Services on that server so that the schema would update. DHCP is now running properly from the 2012 Server.

I am stuck at the moment however, because DNS doesn't appear to be replicating.

In the DNS Server event log on the 2012 server, every couple of minutes Event ID 4013 is logged:-

The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.

If I run dcdiag /test:DNS then I get the results as shown in the attached text file.

I can ping both servers by name from each other, and I can see that my 2012 server is registered in DNS on the SBS2003 server.

The IP (v4) configuration on both servers has the Primary DNS address set to that of the SBS server, and the Secondary DNS address set to that of the 2012 Server.

I have left both servers on overnight, and still no replication. I am at a loss.
testdns.txt
LVL 17
Chris MillardAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Joseph NyaemaIT ConsultantCommented:
The initial synchronization has not completed.
Can disable the firewall on both and the restart the netlogon and the file replication services.  Then watch the file replication log.
0
Chris MillardAuthor Commented:
I have disabled the firewall on the 2012 Server (the Firewall isn't active on SBS 2003 anyway).

I am still getting the same event log warnings, and when I run repadmin /showrepl I get the following:-

Repadmin: running command /showrepl against full DC localhost

Default-First-Site-Name\EXCH2010

DSA Options: IS_GC 

Site Options: (none)

DSA object GUID: d2d7f80d-019d-4e68-a36c-3a3fe7dca3a9

DSA invocationID: 389984e7-e918-492f-be8a-b98fd0984627



==== INBOUND NEIGHBORS ======================================



DC=tuc,DC=local

    Default-First-Site-Name\TUCSRV via RPC

        DSA object GUID: b7997278-ce7f-4e93-b728-0025fe0eaaec

        Last attempt @ 2014-07-14 09:09:27 failed, result 8451 (0x2103):

            The replication operation encountered a database error.

        3940 consecutive failure(s).

        Last success @ (never).



CN=Configuration,DC=tuc,DC=local

    Default-First-Site-Name\TUCSRV via RPC

        DSA object GUID: b7997278-ce7f-4e93-b728-0025fe0eaaec

        Last attempt @ 2014-07-14 08:49:57 was successful.



CN=Schema,CN=Configuration,DC=tuc,DC=local

    Default-First-Site-Name\TUCSRV via RPC

        DSA object GUID: b7997278-ce7f-4e93-b728-0025fe0eaaec

        Last attempt @ 2014-07-14 08:49:57 was successful.



DC=DomainDnsZones,DC=tuc,DC=local

    Default-First-Site-Name\TUCSRV via RPC

        DSA object GUID: b7997278-ce7f-4e93-b728-0025fe0eaaec

        Last attempt @ 2014-07-14 08:49:57 was successful.



DC=ForestDnsZones,DC=tuc,DC=local

    Default-First-Site-Name\TUCSRV via RPC

        DSA object GUID: b7997278-ce7f-4e93-b728-0025fe0eaaec

        Last attempt @ 2014-07-14 08:49:57 was successful.



Source: Default-First-Site-Name\TUCSRV

******* 3939 CONSECUTIVE FAILURES since (never)

Last error: 8451 (0x2103):

            The replication operation encountered a database error.

Open in new window

0
Joseph NyaemaIT ConsultantCommented:
The database on the 2012 is corrupt.
Demote the Domain Controller and Promote it again.  Unless there is a physical issue... should sort it out.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Chris MillardAuthor Commented:
Right, I have demoted and promoted the Server 2012 DC again, but I still have the same issue - same event log warnings, and same result when running repadmin /showrepl

Furthermore. If, on SBS2003, I run:-

repadmin /replicate exch2010 tucsrv /force

I get the following:-

DsReplicaSync() failed with status 8451 (0x2103):
    Can't retrieve message string 8451 (0x2103), error 1815.

See also the screenshot from the Active Directory Replication Monitor on SBS2003
replmon.JPG
0
Joseph NyaemaIT ConsultantCommented:
Following directions from Replication error 8451 The replication operation encountered a database error plus what I think you should additionally do.

Validate the vertical jet database stack from the bottom up (proceeding up to the next layer only when the underlying layer checks out "good")

From the elevated command prompt first check the state of the file system

chkdsk c:

If any errors then
chkdsk c: /f
then reboot server
reboot -r -f -t 0

Again from the elevated command prompt

Stop the Active Directory Service before you do an Physical Consistency Check
net stop ntds
ESEntutl /k C:\Windows\NTDS\ntds.dit

To perform ESE Logical Consistency Check, again with the AD Service Stopped
NTDSUtil
Activate Instance NTDS
Files
Integrity
quit
quit

If above OK proceed below otherwise post errors
To perform an application logical consistency check, again with the AD service stopped

NTDSUtil
Activate Instance NTDS
Semantic Database Analysis
Go
quit

To perform an offline defrag
ESENTUtl /d c:\windows\ntds\ntds.dit

To start the AD service and related services
Net Start NTDS



Can then check the replication with
repadmin /syncall

If still issues, repeat above on SBS side.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Chris MillardAuthor Commented:
There was indeed a problem with the Active Directory database on the SBS server. I had to put into Directory Services Restore Mode in order to run the checks and repairs.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SBS

From novice to tech pro — start learning today.