DCDiag - failed with Error Win32 Error 8420

  • Thread starter Thread starter Alex
  • Start date Start date
A

Alex

Guest
Hi. We were in the process of upgrading our 2003 network to 2003 DCs (we
only had one 2000 DC) and have an error we can't seem to resolve when
running dcdiag. We added a second DC (2003) without problem, unfortunately
there was a terminal hardware failure on the new server a few days later and
the O/S was unbootable. Rather than restore we cleared out all the entries
for the failed DC and re-added it. At this point everything was working
successfully apart from one error listed below during DCDiag test. We
continued with our replacement of the last 2000 DC and replaced it with a
new server running 2003. Again the demotion and addition of the new DC went
without problem. Unfortunately we continue to get the DCDiag errors when
running tests against both DCs.

So far I have tried deleting the Forest and Domain DNS zones using ntdsutil,
allowing the deletion to replicate on both DCs then using the DNS Console
recreating the zones. This all appears to work visually but I then continue
to get the error below. After deleting the zone but before recreating using
the DNS console, if I run DCDiag the Topology and CutOffServer errors no
longer occur, they only reappear when the Forest and DNS Zones are
recreated.

Can anyone suggest what I can do to resolve this and whether it will be
having any impact on the system ?

Thanks,
Alex.


dcdiag /c /v :/dc1 Results, DC2 has the same results

Starting test: Topology
* Configuration Topology Integrity Check
* Analyzing the connection topology for
DC=ForestDNSZones,DC=Domain,DC=NET.
* Performing upstream (of target) analysis.
DsReplicaSyncAllw failed with error Win23 Error 8420.
* Performing downstream (of target) analysis.
DsReplicaSyncAllw failed with error Win23 Error 8420.
* Analyzing the connection topology for
DC=DomainDNSZones,DC=Domain,DC=NET.
* Performing upstream (of target) analysis.
DsReplicaSyncAllw failed with error Win23 Error 8420.
* Performing downstream (of target) analysis.
DsReplicaSyncAllw failed with error Win23 Error 8420.
* Analyzing the connection topology for CN=Schema,CN=Configuration,
DC=Domain,DC=NET.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for
CN=Configuration,DC=Domain,DC=NET.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for DC=Domain,DC=NET.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
........................................DC1 passed test Topology

Starting test: CutoffServers
* Configuration Topology Aliveness Check
* Analyzing the alive system replication topology for
DC=ForesetDNSZones,DC=Domain,DC=NET.
* Performing upstream (of target) analysis.
DsReplicaSyncAllw failed with error Win23 Error 8420.
* Performing downstream (of target) analysis.
DsReplicaSyncAllw failed with error Win23 Error 8420.
* Analyzing the alive system replication topology for
DC=DomainDNSZones,DC=Domain,DC=NET.
* Performing upstream (of target) analysis.
DsReplicaSyncAllw failed with error Win23 Error 8420.
* Performing downstream (of target) analysis.
DsReplicaSyncAllw failed with error Win23 Error 8420. ,
* Analyzing the alive system replication topology for
CN=Schema,CN=ConfigurationDC=Domain,DC=NET.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for
CN=Configuration,DC=Domain,DC=NET.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for DC=Domain,DC=NET.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
.........................................DC1 passed test CutoffServers
 
Re: DCDiag - failed with Error Win32 Error 8420

Read inline please.

In news:uKjgheJmIHA.3512@TK2MSFTNGP03.phx.gbl,
Alex <email@microsoft.newsgroups> typed:
> Hi. We were in the process of upgrading our 2003 network to 2003 DCs
> (we only had one 2000 DC) and have an error we can't seem to resolve
> when running dcdiag. We added a second DC (2003) without problem,
> unfortunately there was a terminal hardware failure on the new server
> a few days later and the O/S was unbootable. Rather than restore we
> cleared out all the entries for the failed DC and re-added it. At
> this point everything was working successfully apart from one error
> listed below during DCDiag test. We continued with our replacement
> of the last 2000 DC and replaced it with a new server running 2003.
> Again the demotion and addition of the new DC went without problem.
> Unfortunately we continue to get the DCDiag errors when running tests
> against both DCs.
>
> So far I have tried deleting the Forest and Domain DNS zones using
> ntdsutil, allowing the deletion to replicate on both DCs then using
> the DNS Console recreating the zones. This all appears to work
> visually but I then continue to get the error below. After deleting
> the zone but before recreating using the DNS console, if I run DCDiag
> the Topology and CutOffServer errors no longer occur, they only
> reappear when the Forest and DNS Zones are recreated.

Was the Win2k DC still in operation and running DNS at this time?
Had you moved the zones to those partitions?

>
> Can anyone suggest what I can do to resolve this and whether it will
> be having any impact on the system ?


> DsReplicaSyncAllw failed with error Win23 Error 8420.
> * Performing downstream (of target) analysis.
> DsReplicaSyncAllw failed with error Win23 Error 8420.
> * Analyzing the connection topology for
> DC=DomainDNSZones,DC=Domain,DC=NET.
> * Performing upstream (of target) analysis.
> DsReplicaSyncAllw failed with error Win23 Error 8420.
> * Performing downstream (of target) analysis.
> DsReplicaSyncAllw failed with error Win23 Error 8420.

Did you copy this from dcdiag?



--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================
 
Re: DCDiag - failed with Error Win32 Error 8420

Read inline please.


"Kevin D. Goodknecht Sr. [MVP]" <admin@nospam.WFTX.US> wrote in message
news:uexUeALmIHA.2396@TK2MSFTNGP02.phx.gbl...
> Read inline please.
>
> In news:uKjgheJmIHA.3512@TK2MSFTNGP03.phx.gbl,
> Alex <email@microsoft.newsgroups> typed:
>> Hi. We were in the process of upgrading our 2003 network to 2003 DCs
>> (we only had one 2000 DC) and have an error we can't seem to resolve
>> when running dcdiag. We added a second DC (2003) without problem,
>> unfortunately there was a terminal hardware failure on the new server
>> a few days later and the O/S was unbootable. Rather than restore we
>> cleared out all the entries for the failed DC and re-added it. At
>> this point everything was working successfully apart from one error
>> listed below during DCDiag test. We continued with our replacement
>> of the last 2000 DC and replaced it with a new server running 2003.
>> Again the demotion and addition of the new DC went without problem.
>> Unfortunately we continue to get the DCDiag errors when running tests
>> against both DCs.
>>
>> So far I have tried deleting the Forest and Domain DNS zones using
>> ntdsutil, allowing the deletion to replicate on both DCs then using
>> the DNS Console recreating the zones. This all appears to work
>> visually but I then continue to get the error below. After deleting
>> the zone but before recreating using the DNS console, if I run DCDiag
>> the Topology and CutOffServer errors no longer occur, they only
>> reappear when the Forest and DNS Zones are recreated.
>
> Was the Win2k DC still in operation and running DNS at this time?
> Had you moved the zones to those partitions?


Yes. The 2k DC held all FSMO roles and was running DNS. I have not moved
the zones to the partitions. The Forest and Domain DNS Zones were created
automatically as part of the second DC deployment but were not used. I was
going to move the zones into the partitions after this issue is resolved.
Replication in DNS is currently configured on both DCs for Win 2000
compatibility i.e. Replicate to all DC in the AD domain. Again I would
change this to DNS Servers in the domain once the issue is resolved.


>> Can anyone suggest what I can do to resolve this and whether it will
>> be having any impact on the system ?
>
>
>> DsReplicaSyncAllw failed with error Win23 Error 8420.
>> * Performing downstream (of target) analysis.
>> DsReplicaSyncAllw failed with error Win23 Error 8420.
>> * Analyzing the connection topology for
>> DC=DomainDNSZones,DC=Domain,DC=NET.
>> * Performing upstream (of target) analysis.
>> DsReplicaSyncAllw failed with error Win23 Error 8420.
>> * Performing downstream (of target) analysis.
>> DsReplicaSyncAllw failed with error Win23 Error 8420.
>
> Did you copy this from dcdiag?


That was the output from dcdiag, although it was retyped by hand as our
domain is not internet connected.

Thanks,
Alex.

>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
>
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> http://message.wftx.us/
 
Re: DCDiag - failed with Error Win32 Error 8420

I'm seeing the same errors in a dcdiag report. Any information you can
provide is appreciated. A quick search of the net doesn't turn up anything
meaningful.

Thanks,
Craig

"Alex" wrote:

> Read inline please.
>
>
> "Kevin D. Goodknecht Sr. [MVP]" <admin@nospam.WFTX.US> wrote in message
> news:uexUeALmIHA.2396@TK2MSFTNGP02.phx.gbl...
> > Read inline please.
> >
> > In news:uKjgheJmIHA.3512@TK2MSFTNGP03.phx.gbl,
> > Alex <email@microsoft.newsgroups> typed:
> >> Hi. We were in the process of upgrading our 2003 network to 2003 DCs
> >> (we only had one 2000 DC) and have an error we can't seem to resolve
> >> when running dcdiag. We added a second DC (2003) without problem,
> >> unfortunately there was a terminal hardware failure on the new server
> >> a few days later and the O/S was unbootable. Rather than restore we
> >> cleared out all the entries for the failed DC and re-added it. At
> >> this point everything was working successfully apart from one error
> >> listed below during DCDiag test. We continued with our replacement
> >> of the last 2000 DC and replaced it with a new server running 2003.
> >> Again the demotion and addition of the new DC went without problem.
> >> Unfortunately we continue to get the DCDiag errors when running tests
> >> against both DCs.
> >>
> >> So far I have tried deleting the Forest and Domain DNS zones using
> >> ntdsutil, allowing the deletion to replicate on both DCs then using
> >> the DNS Console recreating the zones. This all appears to work
> >> visually but I then continue to get the error below. After deleting
> >> the zone but before recreating using the DNS console, if I run DCDiag
> >> the Topology and CutOffServer errors no longer occur, they only
> >> reappear when the Forest and DNS Zones are recreated.
> >
> > Was the Win2k DC still in operation and running DNS at this time?
> > Had you moved the zones to those partitions?
>
>
> Yes. The 2k DC held all FSMO roles and was running DNS. I have not moved
> the zones to the partitions. The Forest and Domain DNS Zones were created
> automatically as part of the second DC deployment but were not used. I was
> going to move the zones into the partitions after this issue is resolved.
> Replication in DNS is currently configured on both DCs for Win 2000
> compatibility i.e. Replicate to all DC in the AD domain. Again I would
> change this to DNS Servers in the domain once the issue is resolved.
>
>
> >> Can anyone suggest what I can do to resolve this and whether it will
> >> be having any impact on the system ?
> >
> >
> >> DsReplicaSyncAllw failed with error Win23 Error 8420.
> >> * Performing downstream (of target) analysis.
> >> DsReplicaSyncAllw failed with error Win23 Error 8420.
> >> * Analyzing the connection topology for
> >> DC=DomainDNSZones,DC=Domain,DC=NET.
> >> * Performing upstream (of target) analysis.
> >> DsReplicaSyncAllw failed with error Win23 Error 8420.
> >> * Performing downstream (of target) analysis.
> >> DsReplicaSyncAllw failed with error Win23 Error 8420.
> >
> > Did you copy this from dcdiag?
>
>
> That was the output from dcdiag, although it was retyped by hand as our
> domain is not internet connected.
>
> Thanks,
> Alex.
>
> >
> >
> > --
> > Best regards,
> > Kevin D. Goodknecht Sr. [MVP]
> > Hope This Helps
> >
> > ===================================
> > When responding to posts, please "Reply to Group"
> > via your newsreader so that others may learn and
> > benefit from your issue, to respond directly to
> > me remove the nospam. from my email address.
> > ===================================
> > http://www.lonestaramerica.com/
> > http://support.wftx.us/
> > http://message.wftx.us/
>
>
 
Re: DCDiag - failed with Error Win32 Error 8420

Hello CraigC,

Please describe your network in detail, how many DC's, operating system etc.
Also give some info about your DNS setup. Additional post the complete output
from dcdiag here.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> I'm seeing the same errors in a dcdiag report. Any information you
> can provide is appreciated. A quick search of the net doesn't turn up
> anything meaningful.
>
> Thanks,
> Craig
> "Alex" wrote:
>
>> Read inline please.
>>
>> "Kevin D. Goodknecht Sr. [MVP]" <admin@nospam.WFTX.US> wrote in
>> message news:uexUeALmIHA.2396@TK2MSFTNGP02.phx.gbl...
>>
>>> Read inline please.
>>>
>>> In news:uKjgheJmIHA.3512@TK2MSFTNGP03.phx.gbl,
>>> Alex <email@microsoft.newsgroups> typed:
>>>> Hi. We were in the process of upgrading our 2003 network to 2003
>>>> DCs (we only had one 2000 DC) and have an error we can't seem to
>>>> resolve when running dcdiag. We added a second DC (2003) without
>>>> problem, unfortunately there was a terminal hardware failure on the
>>>> new server a few days later and the O/S was unbootable. Rather
>>>> than restore we cleared out all the entries for the failed DC and
>>>> re-added it. At this point everything was working successfully
>>>> apart from one error listed below during DCDiag test. We continued
>>>> with our replacement of the last 2000 DC and replaced it with a new
>>>> server running 2003. Again the demotion and addition of the new DC
>>>> went without problem. Unfortunately we continue to get the DCDiag
>>>> errors when running tests against both DCs.
>>>>
>>>> So far I have tried deleting the Forest and Domain DNS zones using
>>>> ntdsutil, allowing the deletion to replicate on both DCs then using
>>>> the DNS Console recreating the zones. This all appears to work
>>>> visually but I then continue to get the error below. After
>>>> deleting the zone but before recreating using the DNS console, if I
>>>> run DCDiag the Topology and CutOffServer errors no longer occur,
>>>> they only reappear when the Forest and DNS Zones are recreated.
>>>>
>>> Was the Win2k DC still in operation and running DNS at this time?
>>> Had you moved the zones to those partitions?
>>>
>> Yes. The 2k DC held all FSMO roles and was running DNS. I have not
>> moved the zones to the partitions. The Forest and Domain DNS Zones
>> were created automatically as part of the second DC deployment but
>> were not used. I was going to move the zones into the partitions
>> after this issue is resolved. Replication in DNS is currently
>> configured on both DCs for Win 2000 compatibility i.e. Replicate to
>> all DC in the AD domain. Again I would change this to DNS Servers in
>> the domain once the issue is resolved.
>>
>>>> Can anyone suggest what I can do to resolve this and whether it
>>>> will be having any impact on the system ?
>>>>
>>>> DsReplicaSyncAllw failed with error Win23 Error 8420.
>>>> * Performing downstream (of target) analysis.
>>>> DsReplicaSyncAllw failed with error Win23 Error 8420.
>>>> * Analyzing the connection topology for
>>>> DC=DomainDNSZones,DC=Domain,DC=NET.
>>>> * Performing upstream (of target) analysis.
>>>> DsReplicaSyncAllw failed with error Win23 Error 8420.
>>>> * Performing downstream (of target) analysis.
>>>> DsReplicaSyncAllw failed with error Win23 Error 8420.
>>> Did you copy this from dcdiag?
>>>
>> That was the output from dcdiag, although it was retyped by hand as
>> our domain is not internet connected.
>>
>> Thanks,
>> Alex.
>>> --
>>> Best regards,
>>> Kevin D. Goodknecht Sr. [MVP]
>>> Hope This Helps
>>> ===================================
>>> When responding to posts, please "Reply to Group"
>>> via your newsreader so that others may learn and
>>> benefit from your issue, to respond directly to
>>> me remove the nospam. from my email address.
>>> ===================================
>>> http://www.lonestaramerica.com/
>>> http://support.wftx.us/
>>> http://message.wftx.us/
 
Re: DCDiag - failed with Error Win32 Error 8420

Meinholf,

Thanks for the response. Maybe I should have been more specific in my
original post. I don't really need help with dcdiag output or with my
network... I'm only looking for a detailed explanation of what "Win32 Error
8420" actually means. I can't find a decent explanation online.

Thanks,
Craig


"Meinolf Weber" wrote:

> Hello CraigC,
>
> Please describe your network in detail, how many DC's, operating system etc.
> Also give some info about your DNS setup. Additional post the complete output
> from dcdiag here.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
> > I'm seeing the same errors in a dcdiag report. Any information you
> > can provide is appreciated. A quick search of the net doesn't turn up
> > anything meaningful.
> >
> > Thanks,
> > Craig
> > "Alex" wrote:
> >
> >> Read inline please.
> >>
> >> "Kevin D. Goodknecht Sr. [MVP]" <admin@nospam.WFTX.US> wrote in
> >> message news:uexUeALmIHA.2396@TK2MSFTNGP02.phx.gbl...
> >>
> >>> Read inline please.
> >>>
> >>> In news:uKjgheJmIHA.3512@TK2MSFTNGP03.phx.gbl,
> >>> Alex <email@microsoft.newsgroups> typed:
> >>>> Hi. We were in the process of upgrading our 2003 network to 2003
> >>>> DCs (we only had one 2000 DC) and have an error we can't seem to
> >>>> resolve when running dcdiag. We added a second DC (2003) without
> >>>> problem, unfortunately there was a terminal hardware failure on the
> >>>> new server a few days later and the O/S was unbootable. Rather
> >>>> than restore we cleared out all the entries for the failed DC and
> >>>> re-added it. At this point everything was working successfully
> >>>> apart from one error listed below during DCDiag test. We continued
> >>>> with our replacement of the last 2000 DC and replaced it with a new
> >>>> server running 2003. Again the demotion and addition of the new DC
> >>>> went without problem. Unfortunately we continue to get the DCDiag
> >>>> errors when running tests against both DCs.
> >>>>
> >>>> So far I have tried deleting the Forest and Domain DNS zones using
> >>>> ntdsutil, allowing the deletion to replicate on both DCs then using
> >>>> the DNS Console recreating the zones. This all appears to work
> >>>> visually but I then continue to get the error below. After
> >>>> deleting the zone but before recreating using the DNS console, if I
> >>>> run DCDiag the Topology and CutOffServer errors no longer occur,
> >>>> they only reappear when the Forest and DNS Zones are recreated.
> >>>>
> >>> Was the Win2k DC still in operation and running DNS at this time?
> >>> Had you moved the zones to those partitions?
> >>>
> >> Yes. The 2k DC held all FSMO roles and was running DNS. I have not
> >> moved the zones to the partitions. The Forest and Domain DNS Zones
> >> were created automatically as part of the second DC deployment but
> >> were not used. I was going to move the zones into the partitions
> >> after this issue is resolved. Replication in DNS is currently
> >> configured on both DCs for Win 2000 compatibility i.e. Replicate to
> >> all DC in the AD domain. Again I would change this to DNS Servers in
> >> the domain once the issue is resolved.
> >>
> >>>> Can anyone suggest what I can do to resolve this and whether it
> >>>> will be having any impact on the system ?
> >>>>
> >>>> DsReplicaSyncAllw failed with error Win23 Error 8420.
> >>>> * Performing downstream (of target) analysis.
> >>>> DsReplicaSyncAllw failed with error Win23 Error 8420.
> >>>> * Analyzing the connection topology for
> >>>> DC=DomainDNSZones,DC=Domain,DC=NET.
> >>>> * Performing upstream (of target) analysis.
> >>>> DsReplicaSyncAllw failed with error Win23 Error 8420.
> >>>> * Performing downstream (of target) analysis.
> >>>> DsReplicaSyncAllw failed with error Win23 Error 8420.
> >>> Did you copy this from dcdiag?
> >>>
> >> That was the output from dcdiag, although it was retyped by hand as
> >> our domain is not internet connected.
> >>
> >> Thanks,
> >> Alex.
> >>> --
> >>> Best regards,
> >>> Kevin D. Goodknecht Sr. [MVP]
> >>> Hope This Helps
> >>> ===================================
> >>> When responding to posts, please "Reply to Group"
> >>> via your newsreader so that others may learn and
> >>> benefit from your issue, to respond directly to
> >>> me remove the nospam. from my email address.
> >>> ===================================
> >>> http://www.lonestaramerica.com/
> >>> http://support.wftx.us/
> >>> http://message.wftx.us/
>
>
>
 
Re: DCDiag - failed with Error Win32 Error 8420

Hello CraigC,

If you have errors in the dcdiag output, there is something not correct.
Normally the dcdiag output doesn't give any error.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Meinholf,
>
> Thanks for the response. Maybe I should have been more specific in my
> original post. I don't really need help with dcdiag output or with my
> network... I'm only looking for a detailed explanation of what "Win32
> Error 8420" actually means. I can't find a decent explanation online.
>
> Thanks,
> Craig
> "Meinolf Weber" wrote:
>
>> Hello CraigC,
>>
>> Please describe your network in detail, how many DC's, operating
>> system etc. Also give some info about your DNS setup. Additional post
>> the complete output from dcdiag here.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> I'm seeing the same errors in a dcdiag report. Any information you
>>> can provide is appreciated. A quick search of the net doesn't turn
>>> up anything meaningful.
>>>
>>> Thanks,
>>> Craig
>>> "Alex" wrote:
>>>> Read inline please.
>>>>
>>>> "Kevin D. Goodknecht Sr. [MVP]" <admin@nospam.WFTX.US> wrote in
>>>> message news:uexUeALmIHA.2396@TK2MSFTNGP02.phx.gbl...
>>>>
>>>>> Read inline please.
>>>>>
>>>>> In news:uKjgheJmIHA.3512@TK2MSFTNGP03.phx.gbl,
>>>>> Alex <email@microsoft.newsgroups> typed:
>>>>>> Hi. We were in the process of upgrading our 2003 network to 2003
>>>>>> DCs (we only had one 2000 DC) and have an error we can't seem to
>>>>>> resolve when running dcdiag. We added a second DC (2003) without
>>>>>> problem, unfortunately there was a terminal hardware failure on
>>>>>> the new server a few days later and the O/S was unbootable.
>>>>>> Rather than restore we cleared out all the entries for the failed
>>>>>> DC and re-added it. At this point everything was working
>>>>>> successfully apart from one error listed below during DCDiag
>>>>>> test. We continued with our replacement of the last 2000 DC and
>>>>>> replaced it with a new server running 2003. Again the demotion
>>>>>> and addition of the new DC went without problem. Unfortunately we
>>>>>> continue to get the DCDiag errors when running tests against both
>>>>>> DCs.
>>>>>>
>>>>>> So far I have tried deleting the Forest and Domain DNS zones
>>>>>> using ntdsutil, allowing the deletion to replicate on both DCs
>>>>>> then using the DNS Console recreating the zones. This all
>>>>>> appears to work visually but I then continue to get the error
>>>>>> below. After deleting the zone but before recreating using the
>>>>>> DNS console, if I run DCDiag the Topology and CutOffServer errors
>>>>>> no longer occur, they only reappear when the Forest and DNS Zones
>>>>>> are recreated.
>>>>>>
>>>>> Was the Win2k DC still in operation and running DNS at this time?
>>>>> Had you moved the zones to those partitions?
>>>>>
>>>> Yes. The 2k DC held all FSMO roles and was running DNS. I have
>>>> not moved the zones to the partitions. The Forest and Domain DNS
>>>> Zones were created automatically as part of the second DC
>>>> deployment but were not used. I was going to move the zones into
>>>> the partitions after this issue is resolved. Replication in DNS is
>>>> currently configured on both DCs for Win 2000 compatibility i.e.
>>>> Replicate to all DC in the AD domain. Again I would change this to
>>>> DNS Servers in the domain once the issue is resolved.
>>>>
>>>>>> Can anyone suggest what I can do to resolve this and whether it
>>>>>> will be having any impact on the system ?
>>>>>>
>>>>>> DsReplicaSyncAllw failed with error Win23 Error 8420.
>>>>>> * Performing downstream (of target) analysis.
>>>>>> DsReplicaSyncAllw failed with error Win23 Error 8420.
>>>>>> * Analyzing the connection topology for
>>>>>> DC=DomainDNSZones,DC=Domain,DC=NET.
>>>>>> * Performing upstream (of target) analysis.
>>>>>> DsReplicaSyncAllw failed with error Win23 Error 8420.
>>>>>> * Performing downstream (of target) analysis.
>>>>>> DsReplicaSyncAllw failed with error Win23 Error 8420.
>>>>> Did you copy this from dcdiag?
>>>>>
>>>> That was the output from dcdiag, although it was retyped by hand as
>>>> our domain is not internet connected.
>>>>
>>>> Thanks,
>>>> Alex.
>>>>> --
>>>>> Best regards,
>>>>> Kevin D. Goodknecht Sr. [MVP]
>>>>> Hope This Helps
>>>>> ===================================
>>>>> When responding to posts, please "Reply to Group"
>>>>> via your newsreader so that others may learn and
>>>>> benefit from your issue, to respond directly to
>>>>> me remove the nospam. from my email address.
>>>>> ===================================
>>>>> http://www.lonestaramerica.com/
>>>>> http://support.wftx.us/
>>>>> http://message.wftx.us/
 
Re: DCDiag - failed with Error Win32 Error 8420

Yes, I agree. However, I'm still looking for a detailed technical
explanation of "Win32 Error 8420". Since Microsoft wrote the code, I know
someone there knows specifically what this error indicates. What say you
Microsofties?


"Meinolf Weber" wrote:

> Hello CraigC,
>
> If you have errors in the dcdiag output, there is something not correct.
> Normally the dcdiag output doesn't give any error.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
> > Meinholf,
> >
> > Thanks for the response. Maybe I should have been more specific in my
> > original post. I don't really need help with dcdiag output or with my
> > network... I'm only looking for a detailed explanation of what "Win32
> > Error 8420" actually means. I can't find a decent explanation online.
> >
> > Thanks,
> > Craig
> > "Meinolf Weber" wrote:
> >
> >> Hello CraigC,
> >>
> >> Please describe your network in detail, how many DC's, operating
> >> system etc. Also give some info about your DNS setup. Additional post
> >> the complete output from dcdiag here.
> >>
> >> Best regards
> >>
> >> Meinolf Weber
> >> Disclaimer: This posting is provided "AS IS" with no warranties, and
> >> confers
> >> no rights.
> >> ** Please do NOT email, only reply to Newsgroups
> >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> >>> I'm seeing the same errors in a dcdiag report. Any information you
> >>> can provide is appreciated. A quick search of the net doesn't turn
> >>> up anything meaningful.
> >>>
> >>> Thanks,
> >>> Craig
> >>> "Alex" wrote:
> >>>> Read inline please.
> >>>>
> >>>> "Kevin D. Goodknecht Sr. [MVP]" <admin@nospam.WFTX.US> wrote in
> >>>> message news:uexUeALmIHA.2396@TK2MSFTNGP02.phx.gbl...
> >>>>
> >>>>> Read inline please.
> >>>>>
> >>>>> In news:uKjgheJmIHA.3512@TK2MSFTNGP03.phx.gbl,
> >>>>> Alex <email@microsoft.newsgroups> typed:
> >>>>>> Hi. We were in the process of upgrading our 2003 network to 2003
> >>>>>> DCs (we only had one 2000 DC) and have an error we can't seem to
> >>>>>> resolve when running dcdiag. We added a second DC (2003) without
> >>>>>> problem, unfortunately there was a terminal hardware failure on
> >>>>>> the new server a few days later and the O/S was unbootable.
> >>>>>> Rather than restore we cleared out all the entries for the failed
> >>>>>> DC and re-added it. At this point everything was working
> >>>>>> successfully apart from one error listed below during DCDiag
> >>>>>> test. We continued with our replacement of the last 2000 DC and
> >>>>>> replaced it with a new server running 2003. Again the demotion
> >>>>>> and addition of the new DC went without problem. Unfortunately we
> >>>>>> continue to get the DCDiag errors when running tests against both
> >>>>>> DCs.
> >>>>>>
> >>>>>> So far I have tried deleting the Forest and Domain DNS zones
> >>>>>> using ntdsutil, allowing the deletion to replicate on both DCs
> >>>>>> then using the DNS Console recreating the zones. This all
> >>>>>> appears to work visually but I then continue to get the error
> >>>>>> below. After deleting the zone but before recreating using the
> >>>>>> DNS console, if I run DCDiag the Topology and CutOffServer errors
> >>>>>> no longer occur, they only reappear when the Forest and DNS Zones
> >>>>>> are recreated.
> >>>>>>
> >>>>> Was the Win2k DC still in operation and running DNS at this time?
> >>>>> Had you moved the zones to those partitions?
> >>>>>
> >>>> Yes. The 2k DC held all FSMO roles and was running DNS. I have
> >>>> not moved the zones to the partitions. The Forest and Domain DNS
> >>>> Zones were created automatically as part of the second DC
> >>>> deployment but were not used. I was going to move the zones into
> >>>> the partitions after this issue is resolved. Replication in DNS is
> >>>> currently configured on both DCs for Win 2000 compatibility i.e.
> >>>> Replicate to all DC in the AD domain. Again I would change this to
> >>>> DNS Servers in the domain once the issue is resolved.
> >>>>
> >>>>>> Can anyone suggest what I can do to resolve this and whether it
> >>>>>> will be having any impact on the system ?
> >>>>>>
> >>>>>> DsReplicaSyncAllw failed with error Win23 Error 8420.
> >>>>>> * Performing downstream (of target) analysis.
> >>>>>> DsReplicaSyncAllw failed with error Win23 Error 8420.
> >>>>>> * Analyzing the connection topology for
> >>>>>> DC=DomainDNSZones,DC=Domain,DC=NET.
> >>>>>> * Performing upstream (of target) analysis.
> >>>>>> DsReplicaSyncAllw failed with error Win23 Error 8420.
> >>>>>> * Performing downstream (of target) analysis.
> >>>>>> DsReplicaSyncAllw failed with error Win23 Error 8420.
> >>>>> Did you copy this from dcdiag?
> >>>>>
> >>>> That was the output from dcdiag, although it was retyped by hand as
> >>>> our domain is not internet connected.
> >>>>
> >>>> Thanks,
> >>>> Alex.
> >>>>> --
> >>>>> Best regards,
> >>>>> Kevin D. Goodknecht Sr. [MVP]
> >>>>> Hope This Helps
> >>>>> ===================================
> >>>>> When responding to posts, please "Reply to Group"
> >>>>> via your newsreader so that others may learn and
> >>>>> benefit from your issue, to respond directly to
> >>>>> me remove the nospam. from my email address.
> >>>>> ===================================
> >>>>> http://www.lonestaramerica.com/
> >>>>> http://support.wftx.us/
> >>>>> http://message.wftx.us/
>
>
>
 
Re: DCDiag - failed with Error Win32 Error 8420

"CraigC" <CraigC@discussions.microsoft.com> wrote in message
news:9E4CB2E5-4CB5-42A5-A9A6-73C134FB1833@microsoft.com...


> Yes, I agree. However, I'm still looking for a detailed technical
> explanation of "Win32 Error 8420". Since Microsoft wrote the code, I know
> someone there knows specifically what this error indicates. What say you
> Microsofties?


> > Thanks for the response. Maybe I should have been more specific in my
> > original post. I don't really need help with dcdiag output or with my
> > network... I'm only looking for a detailed explanation of what "Win32
> > Error 8420" actually means. I can't find a decent explanation online.


So where have your tried looking?

Have you Googled the obvious? Have you Googled MICROSOFT
only?

Have you looked at EventId.net? (They don't seem to have anything,
and possible because this isn't really an Event ID.)

And is that the SPECIFIC error text you have?

Post the specific error text (as "Win32 Error".

Googling this: [ site:microsoft.com ~error 8420 ]
....provides interesting results -- are they specifically insufficient?

There are even references there to exactly "Win32 Error 8420"

This might also be interesting:

[ -site:microsoft.com "win32 error 8420" ]

Everywhere EXCEPT Microsoft...
 
Back
Top