Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, September 30, 2015 1:43 PM
Windows Server 2012 R2
Forest & Domain Functional Level: Windows Server 2012 R2
DNS running on Domain Controller
When I open the Active Directory Administrative Center, I get that it can't connect to the domain. The error is "Cannot find an available server that is running the Active Directory Web Service (ADWS)."
Note that I'm opening it on the domain controller.
I've never gotten the administrative center to work - always had this problem. The ADWS are installed and running, DNS works fine. Two Domain Controllers in the domain, they synchronize without errors, but the administrative center doesn't run on either one.
This domain was promoted up from 2003 functional level, but the original 2003 domain controller was retired.
Any ideas welcome.
Philo Janus, MCP Bridging business & Technology: http://www.saintchad.org/ Telecommuter? http://www.homeofficesurvival.com/ Author: Pro InfoPath 2007 & Pro InfoPath 2010 Pro PerformancePoint 2007 Pro SQL Server Analysis Services 2008 Building Integrated Business Intelligence Solutions
All replies (3)
Monday, October 5, 2015 9:36 AM ✅Answered | 1 vote
Hi Philo,
Maybe obvious, but please make a simple restart of ADWS service and see if it works:
PS> Restart-Service –name ADWS
Also, ADWS service requires TCP port 9389 to be open on the domain controller where ADWS service is running. If you've customized your firewall, you must update it to make sure that this port is open for ADWS service.
Hope this helps.
Regards,
Ethan Hua
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Wednesday, September 30, 2015 4:10 PM
If you have another DC in your environment, I would simply flatten the one giving you the problem and rebuild it from scratch. That takes about 30 minutes. If you don't have another DC, you should get one, even as a VM.
If the problematic DC holds the FSMO roles, make sure you move them to the other DC before flattening and rebuilding the problematic DC.
Recommended practice is to rebuild DCs instead of upgrading in place. Due to its multi-master replication feature, it is by far the easiest way to keep your DCs as clean as possible. Upgrades always create a higher possibility of problems.
. : | : . : | : . tim
Wednesday, September 30, 2015 5:48 PM
Actually I have the exact same problem on both DCs - one is physical, one is virtual. The virtual one I built from scratch on Server 2012R2. Trying the Admin Center on either DC gives the same reply.
FWIW, I am exceptionally tired of the "just format and reinstall" attitude in the software industry. I highly recommend that *anyone* who has ever advocated that watch a season of "Air Crash Investigations" to see what real engineering and problem resolution looks like.
People who just format and reinstall will keep saying it's the way to go because they keep having the same problems without ever understanding what happened. If you do root cause analysis and figure out WHY it happened, then you can avoid it happening again.
Philo Janus, MCP Bridging business & Technology: http://www.saintchad.org/ Telecommuter? http://www.homeofficesurvival.com/ Author: Pro InfoPath 2007 & Pro InfoPath 2010 Pro PerformancePoint 2007 Pro SQL Server Analysis Services 2008 Building Integrated Business Intelligence Solutions