Eric
Tue Mar 22 12:01:45 CST 2005
You read my mind....I was going to ask for repadmin data (later in this
post, I have an aside on how i personally use repadmin to start, if you're
interested).
When I see an 8606 (which btw is ERROR_DS_INSUFFICIENT_ATTR_TO_CREATE_OBJECT
in winerror.h) I typically think: lingering object. You were totally on the
right track with that repadmin command.
Given that this NC is just an app partition, I'm _tempted_ to say, let's
just unhost then rehost it. You can do this with ntdsutil. Using ntdsutil,
if you went down this path, you'd want to remove yourself (yourself==the DC
in question) from the app partition, then add yourself again some time
later. Thoughts?
I would add, if you do have lingering objects, that tells me you perhaps
exceeded tombstone lifetime on this DC or some other in the past. Is that
the case? Have you exceeded tsl before on this DC or some other that is now
spreading lingering objects? It's worth spending a little time on how you
got in to this state, so we can try and avoid it again in the future. :)
<aside>
I'm often asked how I approach replication problems. I will say, my first
command I run is almost always the same....: repadmin /showrepl * /csv
Why? This command goes forest wide to every DSA, and gives you the goodness
of replication status per CO on those DCs.
From there, I usually crack open the csv file in Excel....and I filter for
any row with a status column !=0. Then I try and fix/explain that row. :)
</aside>
~Eric
--
Eric Fleischman [MSFT]
These postings are provided "AS IS" with no warranties, and confers no
rights.
"Christopher" <c_w_bradshaw@hotmail.com> wrote in message
news:%23tE6VwaLFHA.4092@tk2msftngp13.phx.gbl...
> MORE INFO---
>
> This is the result from repadmin /showrepl /v FSMOserver (the restored
> server gets all successful for this command...)
>
> Default-First-Site-Name\FHEXCHANGE
> DC Options: IS_GC
> Site Options: (none)
> DC object GUID: facd2c7d-8465-4e08-bd74-a15da3714393
> DC invocationID: facd2c7d-8465-4e08-bd74-a15da3714393
>
> ==== INBOUND NEIGHBORS ======================================
> DC=flowerhart,DC=local
> Default-First-Site-Name\FHDATA via RPC
> DC object GUID: 9350d8a8-6258-492e-aa77-2fe2f736e542
> Address:
> 9350d8a8-6258-492e-aa77-2fe2f736e542._msdcs.flowerhart.local
> DC invocationID: eddbfb1b-8197-496d-8840-b639fa74defd
> SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
> USNs: 2975323/OU, 2975323/PU
> Last attempt @ 2005-03-21 10:12:50 was successful.
> CN=Configuration,DC=flowerhart,DC=local
> Default-First-Site-Name\FHDATA via RPC
> DC object GUID: 9350d8a8-6258-492e-aa77-2fe2f736e542
> Address:
> 9350d8a8-6258-492e-aa77-2fe2f736e542._msdcs.flowerhart.local
> DC invocationID: eddbfb1b-8197-496d-8840-b639fa74defd
> SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
> USNs: 2975292/OU, 2975292/PU
> Last attempt @ 2005-03-21 10:12:46 was successful.
>
> CN=Schema,CN=Configuration,DC=flowerhart,DC=local
> Default-First-Site-Name\FHDATA via RPC
> DC object GUID: 9350d8a8-6258-492e-aa77-2fe2f736e542
> Address:
> 9350d8a8-6258-492e-aa77-2fe2f736e542._msdcs.flowerhart.local
> DC invocationID: eddbfb1b-8197-496d-8840-b639fa74defd
> SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
> USNs: 2975292/OU, 2975292/PU
> Last attempt @ 2005-03-21 10:12:46 was successful.
> DC=DomainDnsZones,DC=flowerhart,DC=local
> Default-First-Site-Name\FHDATA via RPC
> DC object GUID: 9350d8a8-6258-492e-aa77-2fe2f736e542
> Address:
> 9350d8a8-6258-492e-aa77-2fe2f736e542._msdcs.flowerhart.local
> DC invocationID: eddbfb1b-8197-496d-8840-b639fa74defd
> SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
> USNs: 2942915/OU, 2942915/PU
> Last attempt @ 2005-03-21 10:12:46 failed, result 8606 (0x219e):
> Can't retrieve message string 8606 (0x219e), error 1815.
> 451 consecutive failure(s).
> Last success @ 2005-03-16 09:57:49.
> DC=ForestDnsZones,DC=flowerhart,DC=local
> Default-First-Site-Name\FHDATA via RPC
> DC object GUID: 9350d8a8-6258-492e-aa77-2fe2f736e542
> Address:
> 9350d8a8-6258-492e-aa77-2fe2f736e542._msdcs.flowerhart.local
> DC invocationID: eddbfb1b-8197-496d-8840-b639fa74defd
> SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
> USNs: 2942915/OU, 2942915/PU
> Last attempt @ 2005-03-21 10:11:28 failed, result 8606 (0x219e):
> Can't retrieve message string 8606 (0x219e), error 1815.
> 468 consecutive failure(s).
> Last success @ 2005-03-16 09:57:49.
> Source: Default-First-Site-Name\FHDATA
> ******* 467 CONSECUTIVE FAILURES since 2005-03-16 09:57:49
> Last error: 8606 (0x219e):
> Can't retrieve message string 8606 (0x219e), error 1815.
>
> "Christopher" <c_w_bradshaw@hotmail.com> wrote in message
> news:OSh%232jaLFHA.2604@TK2MSFTNGP10.phx.gbl...
>> Hi,
>> I have a DC server that was restored using V2I and since then it has not
>> replicated with the DC with all FSMO roles. I added the file to the
>> SYSVOL
>> area, NTFRS_CMD_FILE_MOVE_ROOT , as per the KB article. But since then it
> is
>> only replicating one way, it can't replicate to the restored server. it
>> comes
>> up with the error message "The following error occurred during the
> attempt
>> to synchronize naming context DomainDNSZones.domainname.local from domain
>> controller "restored_server" to domain controller "FSMORoles_DCserver":
>>
>> insufficient attributes were given to create an object. this object may
> not
>> exist because it may have been deleted and already garbaged.
>> This operation will not continue.
>>
>> I also ran the command repadmin /removelingeringobjects which completed
>> successfully. but still no luck. I am hoping someone can help, or would
>> it
>> be best to demote the restored server, then manually remove it from
>> active
>> directory on the FSMO server. (since it is not allowing me to dcpromo as
> it
>> can't find the other server when I run it...)
>>
>> The FSMO DC server is Windows 2003 with Exchange 2003
>> the restored DC server is windows 2003
>>
>>
>> Christopher
>> --
>> <Insert Signature Here>
>>
>>
>
>