server 2012 dc hangs after logon

Posted on 2014-07-31
Medium Priority
Last Modified: 2015-01-21
I have a Server 2012 Domain Controller that has been in production for approx 2 months and has worked fine until the past two weeks. Its a new server, OS, etc but has the same name as an old 2003 DC that was replaced. The old one was demoted, renamed, re-ip'd, etc before this server was added. The problem is that at startup it takes about 2 hours before the ctrl+alt+del menu finally comes up. When I CAN finally login, I never get past the "Please Wait for the user Profile Service". I let it run for 48 hrs and it stays in the same place. This is a production fileserver so rebooting during the day is difficult, but so far I have:

- rebooted a gazillion times
- tried booting to last known good - no luck but says something about undoing updates    
- tried starting in safe mode - no luck same as above
- tried booting off of dvd to repair without deleting everything
- tried booting from directory services repair mode - nothing
- did get the server to login instantly after I pulled network cables out earlier this week (can't get it to work again)

The strange thing is that I can access the registry, shares, services, etc remotely, but eventvwr, printing, and local login won't work.

Our monitoring company was installing their Blink software on it right before this started happening, but I don't know if it's that, a Windows Update, AD, or what. I had been working on a pc on our network that had a machine account password issue and ran across this and have changed our computer password age.


Running dcdiag /v against the server gives me:

 The session setup from computer '%server%' failed because the security database does not contain a trust account '%server%$' referenced by the specified computer.  

            USER ACTION  

            If this is the first occurrence of this event for the specified computer and account, this may be a transient issue that doesn't require any action at this time.  If this is a Read-Only Domain Controller and '%server%$' is a legitimate machine account for the computer '%server%' then '%server%' should be marked cacheable for this location if appropriate or otherwise ensure connectivity to a domain controller  capable of servicing the request (for example a writable domain controller).  Otherwise, the following steps may be taken to resolve this problem:  

            If '%server%$' is a legitimate machine account for the computer '%server%', then '%server%' should be rejoined to the domain.  

            If '%server%$' is a legitimate interdomain trust account, then the trust should be recreated.  

I just found the above and haven't really researched it yet but I've tried everything I can think of at this point. Any help?
Question by:FCB_IT
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3

Expert Comment

ID: 40233151
not sure what that monitoring company installed but I would tale it off quickly. are you able to verify all ip addresses on the nics are correct etc?

I will check those few simple things first like IP addresses, errors in the event log. If I don't see anything serious there, me, I would wipe the whole thing out and  reinstall. Much easier in my opinion been researching and troubleshooting for hours on end. And while I'm at it I would reformat that old DC that's been demoted.

Author Comment

ID: 40233160
Software is beyond trust powerbroker. Problem is that I can't log in to view event log nor i can view the nics.
LVL 37

Expert Comment

ID: 40233928
How many DC servers do you have?
Is this only single server left OR you have multiple DCs?
If this is only DC you have, you will lose AD completely and then you need to start from scratch.

Try below
Restart problematic DC in DSRM mode and demote it forcefully through GUI (select forceremoval option)

Note that dcpromo command is no more supported on 2012 onwards and you have to use GUI

This will bring that server to workgroup, now here if thsi is the last DC, you have to start over again from scratch

If this is just ADC, then use below link to remove its computer account from AD
Then change its hostname if possible and promote it again to ADC
Check below link


Accepted Solution

FCB_IT earned 0 total points
ID: 40553811
We ended up blowing away the server and starting over with a fresh install and everything has been fine since.

Author Closing Comment

ID: 40561587

Featured Post

Get real performance insights from real users

Key features:
- Total Pages Views and Load times
- Top Pages Viewed and Load Times
- Real Time Site Page Build Performance
- Users’ Browser and Platform Performance
- Geographic User Breakdown
- And more

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In my previous 24 VMware Articles (http://www.experts-exchange.com/ARTH_1864316.html?arthOrderBy=3&arthSort=1#arth), most featured Intermediate VMware Topics. My next series of articles concentrated on topics for the VMware Novice;   If you would…
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
In this Micro Tutorial viewers will learn how to use Windows Server Backup to create full image of their system. Tutorial shows how to install Windows Server Backup Feature on Windows 2012R2 and how to configure scheduled Bare Metal Recovery backup.…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
Suggested Courses

777 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question