search for: 81a27497

...showrepl Default-First-Site-Name\DC2 DSA Options: 0x00000001 DSA object GUID: 5e93a102-2963-496a-af16-0c51eebb2e31 DSA invocationId: 82b24c02-16cb-4ed1-b68b-a047c26886a9 ==== INBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=samba,DC=domain,DC=com Default-First-Site-Name\DC1 via RPC DSA object GUID: 81a27497-bdfb-4977-9874-675bbfba490f Last attempt @ Tue Jul 1 20:58:53 2014 CEST failed, result 8442 (WERR_DS_DRA_INTERNAL_ERROR) 825 consecutive failure(s). Last success @ Tue Jul 1 16:34:57 2014 CEST CN=Configuration,DC=samba,DC=domain,DC=com Default-First-Site-Name\DC1 via RPC DSA object GUI...

...s perspective, everything is running as it should, there appear to be no issues. However: something in my replication has gone wrong... on dc2: ==== INBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=samba,DC=company,DC=com Default-First-Site-Name\DC1 via RPC DSA object GUID: 81a27497-bdfb-4977-9874-675bbfba490f Last attempt @ Tue Jul 8 17:12:09 2014 CEST failed, result 8442 (WERR_DS_DRA_INTERNAL_ERROR) 3252 consecutive failure(s). Last success @ Tue Jul 1 16:34:57 2014 CEST CN=Configuration,DC=samba,DC=company,DC=com...

...arming was that we should: Oh sure! I posted that info already, I think, but this is the error: > ERROR: no target object found for GUID component for msDS-NC-Replica-Locations in object CN=84bea0a7-82dd-4237-9296-030573700698,CN=Partitions,CN=Configuration,DC=samba,DC=company,DC=com - <GUID=81a27497-bdfb-4977-9874-675bbfba490f>;<RMD_ADDTIME=130405075610000000>;<RMD_CHANGETIME=130405075610000000>;<RMD_FLAGS=0>;<RMD_INVOCID=556b2cb4-e576-48e2-bb7c-7f62caee84fc>;<RMD_LOCAL_USN=4605>;<RMD_ORIGINATING_USN=3630>;<RMD_VERSION=0>;CN=NTDS Settings,CN=DC1,CN=...

...following exception: There appear still some references to an old (many YEARS ago removed) DC: > ERROR: no target object found for GUID component for msDS-NC-Replica-Locations in object CN=84bea0a7-82dd-4237-9296-030573700698,CN=Partitions,CN=Configuration,DC=samba,DC=company,DC=com - <GUID=81a27497-bdfb-4977-9874-675bbfba490f>;<RMD_ADDTIME=130405075610000000>;<RMD_CHANGETIME=130405075610000000>;<RMD_FLAGS=0>;<RMD_INVOCID=556b2cb4-e576-48e2-bb7c-7f62caee84fc>;<RMD_LOCAL_USN=187541>;<RMD_ORIGINATING_USN=3630>;<RMD_VERSION=0>;CN=NTDS Settings,CN=DC1,C...

...gt; no longer needed. There is no DC1 mentioned anywhere there. And the two errors remain: > ERROR: no target object found for GUID component for msDS-NC-Replica-Locations in object CN=84bea0a7-82dd-4237-9296-030573700698,CN=Partitions,CN=Configuration,DC=samba,DC=merit,DC=unu,DC=edu - <GUID=81a27497-bdfb-4977-9874-675bbfba490f>;<RMD_ADDTIME=130405075610000000>;<RMD_CHANGETIME=130405075610000000>;<RMD_FLAGS=0>;<RMD_INVOCID=556b2cb4-e576-48e2-bb7c-7f62caee84fc>;<RMD_LOCAL_USN=4605>;<RMD_ORIGINATING_USN=3630>;<RMD_VERSION=0>;CN=NTDS Settings,CN=DC1,CN=...

...anywhere there. And the two errors remain: > >> ERROR: no target object found for GUID component for >> msDS-NC-Replica-Locations in object >> CN=84bea0a7-82dd-4237-9296-030573700698,CN=Partitions,CN=Configuration,DC=samba,DC=merit,DC=unu,DC=edu >> - >> <GUID=81a27497-bdfb-4977-9874-675bbfba490f>;<RMD_ADDTIME=130405075610000000>;<RMD_CHANGETIME=130405075610000000>;<RMD_FLAGS=0>;<RMD_INVOCID=556b2cb4-e576-48e2-bb7c-7f62caee84fc>;<RMD_LOCAL_USN=4605>;<RMD_ORIGINATING_USN=3630>;<RMD_VERSION=0>;CN=NTDS >> Settings,...

...erences to an old (many YEARS > ago removed) DC: >> ERROR: no target object found for GUID component for >> msDS-NC-Replica-Locations in object >> CN=84bea0a7-82dd-4237-9296-030573700698,CN=Partitions,CN=Configuration,DC=samba,DC=company,DC=com >> - >> <GUID=81a27497-bdfb-4977-9874-675bbfba490f>;<RMD_ADDTIME=130405075610000000>;<RMD_CHANGETIME=130405075610000000>;<RMD_FLAGS=0>;<RMD_INVOCID=556b2cb4-e576-48e2-bb7c-7f62caee84fc>;<RMD_LOCAL_USN=187541>;<RMD_ORIGINATING_USN=3630>;<RMD_VERSION=0>;CN=NTDS >> Setting...

On 10/16/2017 11:13 AM, Rowland Penny via samba wrote: > On Mon, 16 Oct 2017 16:53:17 +0200 > mj via samba <samba at lists.samba.org> wrote: > >> Hi, >> >> dbcheck tells us we have two "dangling forward links" that I am >> trying to get rid of. On my test domain, I have simply done >> >> ldbedit -e nano -H

...ould: > > Oh sure! I posted that info already, I think, but this is the error: > > > ERROR: no target object found for GUID component for msDS-NC-Replica-Locations in object CN=84bea0a7-82dd-4237-9296-030573700698,CN=Partitions,CN=Configuration,DC=samba,DC=company,DC=com - <GUID=81a27497-bdfb-4977-9874-675bbfba490f>;<RMD_ADDTIME=130405075610000000>;<RMD_CHANGETIME=130405075610000000>;<RMD_FLAGS=0>;<RMD_INVOCID=556b2cb4-e576-48e2-bb7c-7f62caee84fc>;<RMD_LOCAL_USN=4605>;<RMD_ORIGINATING_USN=3630>;<RMD_VERSION=0>;CN=NTDS Settings,CN=DC1,CN=...

On 10/16/2017 08:56 PM, Andrew Bartlett wrote: > Are they breaking anything? Not sure. But in another thread I reported some issues on replication, highwatermark notifications, high COU load, etc. My idea was do try several things to fix this. SO I created a virtualised isolated environment, in which I can try out all kinds of things: - upgrading the DCs to 4.7 (as suggested by you) or -