Question : RepAdmin/Rehost Naming Context Error Message

We have a mixture of Windows 2003 and 2000 domain controllers in our forest and are trying to remove some lingering objects from the Read-Only partitions from the domain controllers using the REPADMIN/REHOST command. The command works well when run against the Windows 2003 GCs, but when running the command against the Windows 2000 GCs, we receive the following error message:
"The naming context cannot be removed because it is replicated to another server". I believe we have been able to run this command successfully in the past, so I'm not sure what has changed.

Can anyone tell me what circumstances could cause this error?

Answer : RepAdmin/Rehost Naming Context Error Message

Hmmm ... I've not seen that myself which is surprising to me.  Since I can't easily repro., I'd hazard a guess that the GC in question has a partial replica that is used as the source for another GC's partial copy of that partition ... that's a leap on my part since I'm determining this possibility based exclusively on the error message.  Try placing this DC in a site of its own and triggering its KCC (ensure the Sites and Services snapin is focused on this DC to eliminate repl. latency).

Aside -- what reasons are preventing you from simply demoting these GCs (and there certainly are plenty of them)?