Re: The source server is currently rejecting replication requests.
- From: stephen <stephen@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 11 Jun 2007 09:14:04 -0700
Hi Jorge,
Thank you for your help. I did fixed the Secondary DCs. I didn't performed
the metadta cleanup since that error. However, I did all other cleanup. I
removed the records in the PDC and joined the domain again. Then, I ran
dcpromo command. It works fine after I checked all event log, as well as
replication correct. Therefore, both DCs work propably.
Thanks,
Stephen
"Jorge Silva" wrote:
Hi stephen anything new....
;)
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
"stephen" <stephen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8C0C61BD-A413-454D-8DFC-B99EF3AAF3EA@xxxxxxxxxxxxxxxx
Hi Jorge,
I got problem when I performed the metadata cleanup. The error message is
as
follows:
C:\Documents and Settings\Administrator>ntdsutil
ntdsutil: metadata cleanup
metadata cleanup: connections
server connections: connect to server server2.gov.local
Binding to server2.gov.local ...
DsBindW error 0x6d9(There are no more endpoints available from the
endpoint
mapp
er.)
server connections: connect to server server2
Binding to tsprott ...
DsBindW error 0x6d9(There are no more endpoints available from the
endpoint
mapp
er.)
server connections: quit
metadata cleanup: quit
ntdsutil: quit
C:\Documents and Settings\Administrator>
I have read the article:
http://support.microsoft.com/default.aspx/kb/839880
and verfied each steps. However, I still got the error. What should I do?
Please help me out.
Thanks,
Stephen
"Jorge Silva" wrote:
You can use Windows NTBackup or any Active Directory-aware backup and
restoration utility supported method, check that with your vendor backup
software.
- Disconnect the Failed Dc from network.
- Force Demotion on that Server (dcpromo /forceremoval)
- Then remove all references to that Dc on AD database (Metadata
cleanup).
- Remove any Dns references to the Dc.
- If necessary seize any left Op Master roles that were hosted by that
Dc.
- If the domain controller that you are demoting is a DNS server or
global
catalog server, you must create a new GC or DNS server to satisfy load
balancing, fault tolerance, and configuration settings in the forest.
- When you use the remove selected server command in NTDSUTIL, the
NTDSDSA
object, the parent object for incoming connections to the domain
controller
that you forcibly demoted is removed. The command does not remove the
parent
server objects that appear in the Sites and Services snap-in. Use the
Active
Directory Sites and Services MMC snap-in to remove the server object if
the
domain controller will not be promoted into the forest with the same
computer name
Using Ntdsutil.exe to transfer or seize FSMO roles to a domain controller
http://support.microsoft.com/kb/255504/
Wizard to force demotion in Windows Server 2003 and in Windows 2000
Server
http://support.microsoft.com/kb/332199
How to remove data in Active Directory after an unsuccessful domain
controller demotion
http://support.microsoft.com/?kbid=216498
Clean up server metadata
http://technet2.microsoft.com/WindowsServer/en/Library/012793ee-5e8c-4a5c-9f66-4a486a7114fd1033.mspx?mfr=true
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
"stephen" <stephen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9EDCBAF7-7C26-4857-A463-4F2282C483E2@xxxxxxxxxxxxxxxx
Hi Jorge,
I have another question, if the image backup is a not good backup
software
for AD, what software is the best for AD? Can I use backup software
form
Windows Accessaries?
Thanks,
Stephen
"Jorge Silva" wrote:
Hi
Restoring DCs from imaging ISN'T a supported method of AD
restoration....
http://support.microsoft.com/kb/885875
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
"stephen" <stephen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6C8825A6-7D95-4CA7-B2F3-CDF29A7651E6@xxxxxxxxxxxxxxxx
Hi all,
I aslo get the folllowing error inforamtion:
C:\Program Files\Support Tools>repadmin /showvector /latency DNname
Caching GUIDs.
..
DsReplicaGetInfo() failed with status 8453 (0x2105):
Replication access was denied.
"stephen" wrote:
Hi all,
"The source server is currently rejecting replication requests."
I have secondary DC crash, after I restore data from image backup,
and
the I
tried to replicate dirctory. I got the following error:
Source: Default-First-Site-Name\PrimaryServer
******* 35 CONSECUTIVE FAILURES since 2007-05-31 15:47:35
Last error: 8456 (0x2108):
The source server is currently rejecting replication
requests.
Does anyone know how to fix the problem?
Thanks,
Stephen
- Follow-Ups:
- Re: The source server is currently rejecting replication requests.
- From: Jorge Silva
- Re: The source server is currently rejecting replication requests.
- References:
- Re: The source server is currently rejecting replication requests.
- From: Jorge Silva
- Re: The source server is currently rejecting replication requests.
- From: stephen
- Re: The source server is currently rejecting replication requests.
- From: Jorge Silva
- Re: The source server is currently rejecting replication requests.
- From: stephen
- Re: The source server is currently rejecting replication requests.
- From: Jorge Silva
- Re: The source server is currently rejecting replication requests.
- Prev by Date: Re: dcpromo failed
- Next by Date: Re: Domain account iwth restricted rights
- Previous by thread: Re: The source server is currently rejecting replication requests.
- Next by thread: Re: The source server is currently rejecting replication requests.
- Index(es):
Relevant Pages
|