| Author | Messages | |
bartvdw
Posts:20
 | | 07/14/2010 11:08 AM |
| Hi guys,
I'm taking a look at replication and health of our AD. When I run repadmin /replsummary it shows on 1 DC 1 error. Using repadmin /showrepl * it shows me the details: Last error: 8333 (0x208d): Directory object not found.
It also reports on this DC that it is not advertising as GC... Although it is a GC...
The replication part that is throwing this error the partition of a child domain.
When I look at it's neighbor in the same site, it doesn't report any errors regarding that partition, neither does it report the warning regarding GC.
How can I trace what preciesly is wrong so I can fix it?
Thanks -Bart
| | | |
| bartvdw
Posts:20
 | | 07/14/2010 11:25 AM |
| Could it be that this error is thrown because it tries to replicate this partition from it's neighbor i.o. source DC? The neighbor syncs correctly this partition from the source DC. But when I look at Sites and Services, I notice that the DC throwing the error syncs only from it's neighbor in the same site...
Thanks -Bart
On Wed, Jul 14, 2010 at 12:08 PM, Bart Van den Wyngaert < bartvdw.lists@gmail.com> wrote:
> Hi guys, > > I'm taking a look at replication and health of our AD. > When I run repadmin /replsummary it shows on 1 DC 1 error. > Using repadmin /showrepl * it shows me the details: > Last error: 8333 (0x208d): Directory object not found. > > It also reports on this DC that it is not advertising as GC... Although it > is a GC... > > The replication part that is throwing this error the partition of a child > domain. > > When I look at it's neighbor in the same site, it doesn't report any errors > regarding that partition, neither does it report the warning regarding GC. > > How can I trace what preciesly is wrong so I can fix it? > > Thanks > -Bart >
| | | |
| bartvdw
Posts:20
 | | 07/14/2010 7:14 PM |
| Thanks.
In meantime found the cause of this error and took the necessary actions.
Cheers -Bart
On Wed, Jul 14, 2010 at 3:33 PM, Mohan Ravindran < mohan.activedirectorysupport@gmail.com> wrote:
> May be you can try this. > > > Repadmin /showutdvec <DC1Name> <NamingContextDN> > > Repadmin /showutdvec dc1 dc=contoso, dc=com > > > On Wed, Jul 14, 2010 at 5:23 AM, Bart Van den Wyngaert < > bartvdw.lists@gmail.com> wrote: > >> Could it be that this error is thrown because it tries to replicate this >> partition from it's neighbor i.o. source DC? >> The neighbor syncs correctly this partition from the source DC. But when I >> look at Sites and Services, I notice that the DC throwing the error syncs >> only from it's neighbor in the same site... >> >> Thanks >> -Bart >> >> >> On Wed, Jul 14, 2010 at 12:08 PM, Bart Van den Wyngaert < >> bartvdw.lists@gmail.com> wrote: >> >>> Hi guys, >>> >>> I'm taking a look at replication and health of our AD. >>> When I run repadmin /replsummary it shows on 1 DC 1 error. >>> Using repadmin /showrepl * it shows me the details: >>> Last error: 8333 (0x208d): Directory object not found. >>> >>> It also reports on this DC that it is not advertising as GC... Although >>> it is a GC... >>> >>> The replication part that is throwing this error the partition of a child >>> domain. >>> >>> When I look at it's neighbor in the same site, it doesn't report any >>> errors regarding that partition, neither does it report the warning >>> regarding GC. >>> >>> How can I trace what preciesly is wrong so I can fix it? >>> >>> Thanks >>> -Bart >>> >> >> > > > -- > Regards, > Mohan R > Level2-Server support Engineer. > > >
| | | |
| mohanrav
Posts:82
 | | 07/15/2010 7:24 AM |
| Hi Bart,
Could you please share that as well? we 'll b prepared to resolve these issues. 
On Wed, Jul 14, 2010 at 1:13 PM, Bart Van den Wyngaert < bartvdw.lists@gmail.com> wrote:
> Thanks. > > In meantime found the cause of this error and took the necessary actions. > > Cheers > -Bart > > > On Wed, Jul 14, 2010 at 3:33 PM, Mohan Ravindran < > mohan.activedirectorysupport@gmail.com> wrote: > >> May be you can try this. >> >> >> Repadmin /showutdvec <DC1Name> <NamingContextDN> >> >> Repadmin /showutdvec dc1 dc=contoso, dc=com >> >> >> On Wed, Jul 14, 2010 at 5:23 AM, Bart Van den Wyngaert < >> bartvdw.lists@gmail.com> wrote: >> >>> Could it be that this error is thrown because it tries to replicate this >>> partition from it's neighbor i.o. source DC? >>> The neighbor syncs correctly this partition from the source DC. But when >>> I look at Sites and Services, I notice that the DC throwing the error syncs >>> only from it's neighbor in the same site... >>> >>> Thanks >>> -Bart >>> >>> >>> On Wed, Jul 14, 2010 at 12:08 PM, Bart Van den Wyngaert < >>> bartvdw.lists@gmail.com> wrote: >>> >>>> Hi guys, >>>> >>>> I'm taking a look at replication and health of our AD. >>>> When I run repadmin /replsummary it shows on 1 DC 1 error. >>>> Using repadmin /showrepl * it shows me the details: >>>> Last error: 8333 (0x208d): Directory object not found. >>>> >>>> It also reports on this DC that it is not advertising as GC... Although >>>> it is a GC... >>>> >>>> The replication part that is throwing this error the partition of a >>>> child domain. >>>> >>>> When I look at it's neighbor in the same site, it doesn't report any >>>> errors regarding that partition, neither does it report the warning >>>> regarding GC. >>>> >>>> How can I trace what preciesly is wrong so I can fix it? >>>> >>>> Thanks >>>> -Bart >>>> >>> >>> >> >> >> -- >> Regards, >> Mohan R >> Level2-Server support Engineer. >> >> >> >
-- Regards, Mohan R Level2-Server support Engineer.
| | | |
| bartvdw
Posts:20
 | | 07/15/2010 8:55 AM |
| Well actually I made that DC GC, but due problems with a DC of a subdomain generated this errors all the way. Decided to remove GC at that DC and errors went away.
-Bart
On Thu, Jul 15, 2010 at 8:23 AM, Mohan Ravindran < mohan.activedirectorysupport@gmail.com> wrote:
> Hi Bart, > > Could you please share that as well? we 'll b prepared to resolve these > issues.  > > On Wed, Jul 14, 2010 at 1:13 PM, Bart Van den Wyngaert < > bartvdw.lists@gmail.com> wrote: > >> Thanks. >> >> In meantime found the cause of this error and took the necessary actions. >> >> Cheers >> -Bart >> >> >> On Wed, Jul 14, 2010 at 3:33 PM, Mohan Ravindran < >> mohan.activedirectorysupport@gmail.com> wrote: >> >>> May be you can try this. >>> >>> >>> Repadmin /showutdvec <DC1Name> <NamingContextDN> >>> >>> Repadmin /showutdvec dc1 dc=contoso, dc=com >>> >>> >>> On Wed, Jul 14, 2010 at 5:23 AM, Bart Van den Wyngaert < >>> bartvdw.lists@gmail.com> wrote: >>> >>>> Could it be that this error is thrown because it tries to replicate this >>>> partition from it's neighbor i.o. source DC? >>>> The neighbor syncs correctly this partition from the source DC. But when >>>> I look at Sites and Services, I notice that the DC throwing the error syncs >>>> only from it's neighbor in the same site... >>>> >>>> Thanks >>>> -Bart >>>> >>>> >>>> On Wed, Jul 14, 2010 at 12:08 PM, Bart Van den Wyngaert < >>>> bartvdw.lists@gmail.com> wrote: >>>> >>>>> Hi guys, >>>>> >>>>> I'm taking a look at replication and health of our AD. >>>>> When I run repadmin /replsummary it shows on 1 DC 1 error. >>>>> Using repadmin /showrepl * it shows me the details: >>>>> Last error: 8333 (0x208d): Directory object not found. >>>>> >>>>> It also reports on this DC that it is not advertising as GC... Although >>>>> it is a GC... >>>>> >>>>> The replication part that is throwing this error the partition of a >>>>> child domain. >>>>> >>>>> When I look at it's neighbor in the same site, it doesn't report any >>>>> errors regarding that partition, neither does it report the warning >>>>> regarding GC. >>>>> >>>>> How can I trace what preciesly is wrong so I can fix it? >>>>> >>>>> Thanks >>>>> -Bart >>>>> >>>> >>>> >>> >>> >>> -- >>> Regards, >>> Mohan R >>> Level2-Server support Engineer. >>> >>> >>> >> > > > -- > Regards, > Mohan R > Level2-Server support Engineer. > > >
| | | |
|
|