netlogon timeout when attempt to demote dc

Hi,

I am attempting to demote last DC in a site, it does the final replication,
then when netlogon is shutting down, it times out and failes to demote due to
timeout. In the event log as soon as netlogon starts to shtdown, the DNS
server encounters a critical error from Active Directory. The evens is 4015
and is as follows:

The DNS server has encountered a critical error from the Active Directory.
Check that the Active Directory is functioning properly. The extended error
debug information (which may be empty) is "000020DE: SvcErr: DSID-030F00E4,
problem 5001 (BUSY), data 0". The event data contains the error.

The dcpromo ends by saying that Active Directory was not removed, I then
reboot since AD seems ok after that.

Any ideas how I can get this resolved so I can demote this DC properly using
dcpromo. I'd rather not try a force demotion or using NTDSUTIL

Any idea, thank you, appreciated.

WHere is the DC pointing to for its Preferred DNS?

"mc123" wrote:

> Hi,
>
> I am attempting to demote last DC in a site, it does the final replication,
> then when netlogon is shutting down, it times out and failes to demote due to
> timeout. In the event log as soon as netlogon starts to shtdown, the DNS
> server encounters a critical error from Active Directory. The evens is 4015
> and is as follows:
>
> The DNS server has encountered a critical error from the Active Directory.
> Check that the Active Directory is functioning properly. The extended error
> debug information (which may be empty) is "000020DE: SvcErr: DSID-030F00E4,
> problem 5001 (BUSY), data 0". The event data contains the error.
>
> The dcpromo ends by saying that Active Directory was not removed, I then
> reboot since AD seems ok after that.
>
> Any ideas how I can get this resolved so I can demote this DC properly using
> dcpromo. I'd rather not try a force demotion or using NTDSUTIL
>
> Any idea, thank you, appreciated.

It first points to itself then secondly to the main DC in the root domain.

Thanks.

"Steve B" wrote:

> WHere is the DC pointing to for its Preferred DNS?
>
> "mc123" wrote:
>
> > Hi,
> >
> > I am attempting to demote last DC in a site, it does the final replication,
> > then when netlogon is shutting down, it times out and failes to demote due to
> > timeout. In the event log as soon as netlogon starts to shtdown, the DNS
> > server encounters a critical error from Active Directory. The evens is 4015
> > and is as follows:
> >
> > The DNS server has encountered a critical error from the Active Directory.
> > Check that the Active Directory is functioning properly. The extended error
> > debug information (which may be empty) is "000020DE: SvcErr: DSID-030F00E4,
> > problem 5001 (BUSY), data 0". The event data contains the error.
> >
> > The dcpromo ends by saying that Active Directory was not removed, I then
> > reboot since AD seems ok after that.
> >
> > Any ideas how I can get this resolved so I can demote this DC properly using
> > dcpromo. I'd rather not try a force demotion or using NTDSUTIL
> >
> > Any idea, thank you, appreciated.

Point to the other root DC as its Preferred DNS Server. Ensure that all the
AD related records are there for both the DC being demoted and the other root
DC. Then try running DCPROMO again.

"mc123" wrote:

> It first points to itself then secondly to the main DC in the root domain.
>
> Thanks.
>
> "Steve B" wrote:
>
> > WHere is the DC pointing to for its Preferred DNS?
> >
> > "mc123" wrote:
> >
> > > Hi,
> > >
> > > I am attempting to demote last DC in a site, it does the final replication,
> > > then when netlogon is shutting down, it times out and failes to demote due to
> > > timeout. In the event log as soon as netlogon starts to shtdown, the DNS
> > > server encounters a critical error from Active Directory. The evens is 4015
> > > and is as follows:
> > >
> > > The DNS server has encountered a critical error from the Active Directory.
> > > Check that the Active Directory is functioning properly. The extended error
> > > debug information (which may be empty) is "000020DE: SvcErr: DSID-030F00E4,
> > > problem 5001 (BUSY), data 0". The event data contains the error.
> > >
> > > The dcpromo ends by saying that Active Directory was not removed, I then
> > > reboot since AD seems ok after that.
> > >
> > > Any ideas how I can get this resolved so I can demote this DC properly using
> > > dcpromo. I'd rather not try a force demotion or using NTDSUTIL
> > >
> > > Any idea, thank you, appreciated.

Hi, I tried, but I get the same problem, when netlogon tries to stop, active
directory on the particular server encounters a critical error and does not
complete?

Any ideas, is there some specific tests that can be run to verify AD on this
server is ok?

I think I have tried most of the netdiag, and dcdiag??

Thanks.

"Steve B" wrote:

> Point to the other root DC as its Preferred DNS Server. Ensure that all the
> AD related records are there for both the DC being demoted and the other root
> DC. Then try running DCPROMO again.
>
> "mc123" wrote:
>
> > It first points to itself then secondly to the main DC in the root domain.
> >
> > Thanks.
> >
> > "Steve B" wrote:
> >
> > > WHere is the DC pointing to for its Preferred DNS?
> > >
> > > "mc123" wrote:
> > >
> > > > Hi,
> > > >
> > > > I am attempting to demote last DC in a site, it does the final replication,
> > > > then when netlogon is shutting down, it times out and failes to demote due to
> > > > timeout. In the event log as soon as netlogon starts to shtdown, the DNS
> > > > server encounters a critical error from Active Directory. The evens is 4015
> > > > and is as follows:
> > > >
> > > > The DNS server has encountered a critical error from the Active Directory.
> > > > Check that the Active Directory is functioning properly. The extended error
> > > > debug information (which may be empty) is "000020DE: SvcErr: DSID-030F00E4,
> > > > problem 5001 (BUSY), data 0". The event data contains the error.
> > > >
> > > > The dcpromo ends by saying that Active Directory was not removed, I then
> > > > reboot since AD seems ok after that.
> > > >
> > > > Any ideas how I can get this resolved so I can demote this DC properly using
> > > > dcpromo. I'd rather not try a force demotion or using NTDSUTIL
> > > >
> > > > Any idea, thank you, appreciated.

[WhitePhantom]

I was having the same problem about 30 minutes ago. I corrected it by checking if the Intersite Messaging service was enabled on both domain controllers (we only have two). Sure enough, it had somehow been disabled on the DC that holds all the FSMO roles. As soon as I enabled the service, I was able to demote my non FSMO domain controller without any problems.

Good luck!
WhitePhantom

Hi,
I ended up cleaning up AD meta data, also noticed that when I deleted the
site, in sites and services, it would not automatically delete the
domaindnszone and forestdnszone information, which I believe should be
removed when a site is removed from sites and services.
I checked the intersite messaging service, which seems to be running on DC
that holds all FSMO roles.
I should be demoting some other DC in not too long so will see what happens
to them, for right now I should be clean from the one DC that was not
demoting, I just hope there isn't a problem with AD.

Thanks.

"WhitePhantom" wrote:

>
> I was having the same problem about 30 minutes ago. I corrected it by
> checking if the Intersite Messaging service was enabled on both domain
> controllers (we only have two). Sure enough, it had somehow been
> disabled on the DC that holds all the FSMO roles. As soon as I enabled
> the service, I was able to demote my non FSMO domain controller without
> any problems.
>
> Good luck!
> WhitePhantom
>
>
> --
> WhitePhantom
> ------------------------------------------------------------------------
> WhitePhantom's Profile: http://forums.techarena.in/members/30671.htm
> View this thread: netlogon timeout when attempt to demote dc
>
> http://forums.techarena.in
>
>