asked on

Restored 2008 DC no longer replicating with other 2003 DC's

Today I had to restore a WIN 2008 R2 Domain Controller that holds all the FSMO roles in a VMWare environment. I'm getting errors when trying to synch between the restored (2008 R2) and the existing WIN2K3 DC's. I vRanger to restore my vm from an earlier backup. This is the output when I run: repadmin /syncall. Thanks for the help in advance.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\administrator.mydomain>repadmin /syncall
CALLBACK MESSAGE: The following replication is in progress:
From: ebecfdad-8334-43c5-b3a1-3949fcd39a9b._msdcs.mydomain.local
To : a46298ac-395e-4818-b3d4-e301bd88ab04._msdcs.mydomain.local
CALLBACK MESSAGE: Error issuing replication: 8451 (0x2103):
The replication operation encountered a database error.
From: ebecfdad-8334-43c5-b3a1-3949fcd39a9b._msdcs.mydomain.local
To : a46298ac-395e-4818-b3d4-e301bd88ab04._msdcs.mydomain.local
CALLBACK MESSAGE: The following replication is in progress:
From: 73915512-2782-405d-a46a-1ca70333deeb._msdcs.mydomain.local
To : a46298ac-395e-4818-b3d4-e301bd88ab04._msdcs.mydomain.local
CALLBACK MESSAGE: Error issuing replication: 8451 (0x2103):
The replication operation encountered a database error.
From: 73915512-2782-405d-a46a-1ca70333deeb._msdcs.mydomain.local
To : a46298ac-395e-4818-b3d4-e301bd88ab04._msdcs.mydomain.local
CALLBACK MESSAGE: SyncAll Finished.

SyncAll reported the following errors:
Error issuing replication: 8451 (0x2103):
The replication operation encountered a database error.
From: ebecfdad-8334-43c5-b3a1-3949fcd39a9b._msdcs.mydomain.local
To : a46298ac-395e-4818-b3d4-e301bd88ab04._msdcs.mydomain.local
Error issuing replication: 8451 (0x2103):
The replication operation encountered a database error.
From: 73915512-2782-405d-a46a-1ca70333deeb._msdcs.mydomain.local
To : a46298ac-395e-4818-b3d4-e301bd88ab04._msdcs.mydomain.local

SOLUTION

Paka

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER CERTIFIED SOLUTION

Krzysztof Pytko

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

RAFF-

ASKER

Thank you all. After further investigation, I decided to remove the problematic DC and seize the Roles on a functional DC as recommended. The server did go through a USN Roll back and there fore I followed these recommended steps here: http://support.microsoft.com/default.aspx?scid=kb;EN-US;875495

Although I think I was able to remove all instances of the old DC by running the metadata cleanup command, I recreated the new DC with a different name just in case. Didn't want it to come back and haunt me later. I know know that restoring DC's from VM images is not recommended and only should be used in case there are no other DC's in the environment.