DCPROMO Target account name incorrect

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We have a windows 2003 primary domain controller and a windows 2000 secondary
domain controller. The windows 2000 secondary domain has been offline for a
few weeks. When brought back online we attempted to run dcpromo to demote
server to a member server. We are using a domain admin account but receive
the following error message: Logon Failure: The target account name is
incorrect". The following is from the dcpromo.log file.
08/01 08:57:29 [INFO] Request for demotion of domain controller
08/01 08:57:29 [INFO] DnsDomainName (NULL)
08/01 08:57:29 [INFO] ServerRole 1
08/01 08:57:29 [INFO] Account (NULL) Options 128
08/01 08:57:29 [INFO] LastDcInDomain FALSE
08/01 08:57:29 [INFO] Start the worker task
08/01 08:57:29 [INFO] Request for demotion returning 0
08/01 08:57:29 [INFO] Reading domain policy from the local machine
08/01 08:57:29 [INFO] Searching for a domain controller for the domain
genmetal.com
08/01 08:57:29 [INFO] Searching for a domain controller for the domain
genmetal.com that contains the account GMFSAG$
08/01 08:57:29 [INFO] Located domain controller GMF-DC1.genmetal.com for
domain genmetal.com
08/01 08:57:29 [INFO] Support Dc in genmetal.com is GMF-DC1.genmetal.com
08/01 08:57:29 [INFO] Located domain controller GMF-DC1.genmetal.com for
domain genmetal.com
08/01 08:57:29 [INFO] Error - Managing the network session with
GMF-DC1.genmetal.com failed
(1396)
08/01 08:57:29 [ERROR] Failed to establish the session with
GMF-DC1.genmetal.com: 0x574
08/01 08:57:29 [INFO] The attempted domain controller operation has completed
08/01 08:57:29 [INFO] DsRolepSetOperationDone returned 0

Do we have to manually remove the DC because it hasn't replicated in over 4
weeks? If so how do we do that?

Thank You.
Ray.
 
Actually I had tried that as well previously and was still getting the same
message. I went and reinstalled sp4, and re-ran dcpromo /forceremoval and it
worked.

Thanks.

Marco Aurélio said:
try dcpromo /forceremoval

rbaker said:
We have a windows 2003 primary domain controller and a windows 2000
secondary
domain controller. The windows 2000 secondary domain has been offline for
a
few weeks. When brought back online we attempted to run dcpromo to demote
server to a member server. We are using a domain admin account but
receive
the following error message: Logon Failure: The target account name is
incorrect". The following is from the dcpromo.log file.
08/01 08:57:29 [INFO] Request for demotion of domain controller
08/01 08:57:29 [INFO] DnsDomainName (NULL)
08/01 08:57:29 [INFO] ServerRole 1
08/01 08:57:29 [INFO] Account (NULL) Options 128
08/01 08:57:29 [INFO] LastDcInDomain FALSE
08/01 08:57:29 [INFO] Start the worker task
08/01 08:57:29 [INFO] Request for demotion returning 0
08/01 08:57:29 [INFO] Reading domain policy from the local machine
08/01 08:57:29 [INFO] Searching for a domain controller for the domain
genmetal.com
08/01 08:57:29 [INFO] Searching for a domain controller for the domain
genmetal.com that contains the account GMFSAG$
08/01 08:57:29 [INFO] Located domain controller GMF-DC1.genmetal.com for
domain genmetal.com
08/01 08:57:29 [INFO] Support Dc in genmetal.com is GMF-DC1.genmetal.com
08/01 08:57:29 [INFO] Located domain controller GMF-DC1.genmetal.com for
domain genmetal.com
08/01 08:57:29 [INFO] Error - Managing the network session with
GMF-DC1.genmetal.com failed
(1396)
08/01 08:57:29 [ERROR] Failed to establish the session with
GMF-DC1.genmetal.com: 0x574
08/01 08:57:29 [INFO] The attempted domain controller operation has
completed
08/01 08:57:29 [INFO] DsRolepSetOperationDone returned 0

Do we have to manually remove the DC because it hasn't replicated in over
4
weeks? If so how do we do that?

Thank You.
Ray.
Click to expand...
Click to expand...
 
You will have to go back now and clean up your metadata.

http://support.microsoft.com/default.aspx?scid=kb;en-us;216498


--

Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.


rbaker said:
Actually I had tried that as well previously and was still getting the same
message. I went and reinstalled sp4, and re-ran dcpromo /forceremoval and it
worked.

Thanks.

Marco Aurélio said:
try dcpromo /forceremoval

rbaker said:
We have a windows 2003 primary domain controller and a windows 2000
secondary
domain controller. The windows 2000 secondary domain has been offline for
a
few weeks. When brought back online we attempted to run dcpromo to demote
server to a member server. We are using a domain admin account but
receive
the following error message: Logon Failure: The target account name is
incorrect". The following is from the dcpromo.log file.
08/01 08:57:29 [INFO] Request for demotion of domain controller
08/01 08:57:29 [INFO] DnsDomainName (NULL)
08/01 08:57:29 [INFO] ServerRole 1
08/01 08:57:29 [INFO] Account (NULL) Options 128
08/01 08:57:29 [INFO] LastDcInDomain FALSE
08/01 08:57:29 [INFO] Start the worker task
08/01 08:57:29 [INFO] Request for demotion returning 0
08/01 08:57:29 [INFO] Reading domain policy from the local machine
08/01 08:57:29 [INFO] Searching for a domain controller for the domain
genmetal.com
08/01 08:57:29 [INFO] Searching for a domain controller for the domain
genmetal.com that contains the account GMFSAG$
08/01 08:57:29 [INFO] Located domain controller GMF-DC1.genmetal.com for
domain genmetal.com
08/01 08:57:29 [INFO] Support Dc in genmetal.com is GMF-DC1.genmetal.com
08/01 08:57:29 [INFO] Located domain controller GMF-DC1.genmetal.com for
domain genmetal.com
08/01 08:57:29 [INFO] Error - Managing the network session with
GMF-DC1.genmetal.com failed
(1396)
08/01 08:57:29 [ERROR] Failed to establish the session with
GMF-DC1.genmetal.com: 0x574
08/01 08:57:29 [INFO] The attempted domain controller operation has
completed
08/01 08:57:29 [INFO] DsRolepSetOperationDone returned 0

Do we have to manually remove the DC because it hasn't replicated in over
4
weeks? If so how do we do that?

Thank You.
Ray.
Click to expand...
Click to expand...
Click to expand...
 
The other solution I found that corrects these types of problems is this:

On the Non-Problem Server run the following command
NETDOM RESETPWD /Server:ProblemServer /UserD:Domain\AdministrativeID
/PasswordD:*

This is the OPPOSITE of the solution that is suggested in article 826902 but
it does work. I've used it a few times.

JHK
 
Back
Top