Case of the Domain Join Failure II–Object Already Exists

In our first domain join failure case, we looked at the scenario when the local computer name was corrupted

Now we look at this scenario: Joining a computer to a domain, we are told “Object already exists” Even though it doesn’t!

Searching AD Users & Computers we find:


So I start a Network Monitor trace, configured to use Windows Parsers. Network Monitor is here and the latest parsers are available here

Parsers are selected in Tools –> Options


I then set the network monitor filter to monitor NetLogon traffic. From this could see a specific domain controller was the culprit for saying the object already existed:


Sure enough, when connected Active Directory Users & Computers to the specific domain controller in question computer account was found.


Computer account could not be deleted. Ultimate cause was Domain Controller had run out of free disk space…

This issue could also be caused by delays in replication. When joining to domain, all DCs are checked against…Network Monitor will easily tell you why your domain joins are failing in most cases. And on Windows 7 and later you can just netsh trace start capture=yes report=yes persistent=yes to get the required logging, even if a reboot occurs in-between, just netsh trace stop to finish your trace, then open the .ETL file in Network Monitor.

About chentiangemalc

specializes in end-user computing technologies. disclaimer 1) use at your own risk. test any solution in your environment. if you do not understand the impact/consequences of what you're doing please stop, and ask advice from somebody who does. 2) views are my own at the time of posting and do not necessarily represent my current view or the view of my employer and family members/relatives. 3) over the years Microsoft/Citrix/VMWare have given me a few free shirts, pens, paper notebooks/etc. despite these gifts i will try to remain unbiased.
This entry was posted in Active Directory, Network Monitor and tagged . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s