Server 2008 active directory services and more not starting
Hi
Rebooted the DC after removing CA antivirus and the following services now fail to start
1) DHCP could not start as an RPC server. Not enough resources are available
2) Bits failed to start error 2147952506
3) Intersite Messaging. Error messag eis service changed to unexpected state
4) Active Directory Users and Computers has Red Cross. Error message is naming path was not found
5) DNS service fails to start with error 140. Cannot initialize the RPC service
Active Directory Domain services have started and RPC service also says it has started
I have uninstalled DNS and then tried to reinstalled but it failed to reinstall
Any help would be appreciated
Thanks
Rebooted the DC after removing CA antivirus and the following services now fail to start
1) DHCP could not start as an RPC server. Not enough resources are available
2) Bits failed to start error 2147952506
3) Intersite Messaging. Error messag eis service changed to unexpected state
4) Active Directory Users and Computers has Red Cross. Error message is naming path was not found
5) DNS service fails to start with error 140. Cannot initialize the RPC service
Active Directory Domain services have started and RPC service also says it has started
I have uninstalled DNS and then tried to reinstalled but it failed to reinstall
Any help would be appreciated
Thanks
ASKER
Hi iSiek
Under the control panel > Windows Firewall is shows that the firewall is off. Is this the correct place to look for Advanced Firewall profiles
Under the control panel > Windows Firewall is shows that the firewall is off. Is this the correct place to look for Advanced Firewall profiles
I would rather check Administrative Tools -> Windows Advanced Firewall
:)
Krzysztof
:)
Krzysztof
ASKER
OK ;) I checked there and Domain/Private and Public are all off.
OK, so reboot server onec again and check if services started
This is not FW issue for sure :)
Krzysztof
This is not FW issue for sure :)
Krzysztof
ASKER
Rebooted and still same problem. MS have suggested removing AD and doing a dcpromo again. What do you think, is there anything else I could try?
Is that the only one DC? Do you have recent system state backup?
If it's not the only one, then yes, it's better to decommission it and re-promote as DC again.
If you're interested, please visit my blog at http://kpytko.wordpress.com
and look for "Decommissioning broken Domain Controller: and "Metadata cleanup" articles
after that, you may wish to read "Adding additional DC"
Krzysztof
If it's not the only one, then yes, it's better to decommission it and re-promote as DC again.
If you're interested, please visit my blog at http://kpytko.wordpress.com
and look for "Decommissioning broken Domain Controller: and "Metadata cleanup" articles
after that, you may wish to read "Adding additional DC"
Krzysztof
ASKER
Thanks iSiek
I'll read the articles and get back to you with result
I'll read the articles and get back to you with result
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi iSiek
I read and followed the articles. Seemed to go OK but now the computer cannt join the domain.
When I try to join I am asked for the username/password for the domain admin as per normal and then I get the message "The network location cannot be reached"
I've can see that the TCP/IP NetBIOS Help service has started.
Any ideas what I can do next
I read and followed the articles. Seemed to go OK but now the computer cannt join the domain.
When I try to join I am asked for the username/password for the domain admin as per normal and then I get the message "The network location cannot be reached"
I've can see that the TCP/IP NetBIOS Help service has started.
Any ideas what I can do next
ASKER
Hi iSiek
Looks like we might be back in business. Fixed the "The Network location cannot be reached" by reinstalling Client for Microsoft Networks in the NIC Network properties. Not sure whay it was missing.
The pictures in your docs made it easy to follow. One addition , I may have missed it, was that before you do a metadata cleanup you need to ensure that the object in AD is not protected from deletion (ADUAC > View > Advanced to on > Right click on object > properties > Object) See Protect object from accidental deletion otherwise it will fail if object is protected. I think this is a server 2008 thing.
Anyway thanks again and will award points to you
Looks like we might be back in business. Fixed the "The Network location cannot be reached" by reinstalling Client for Microsoft Networks in the NIC Network properties. Not sure whay it was missing.
The pictures in your docs made it easy to follow. One addition , I may have missed it, was that before you do a metadata cleanup you need to ensure that the object in AD is not protected from deletion (ADUAC > View > Advanced to on > Right click on object > properties > Object) See Protect object from accidental deletion otherwise it will fail if object is protected. I think this is a server 2008 thing.
Anyway thanks again and will award points to you
Thank you! :) I will put there information if you do that for 2008 you need to check object protection
Krzysztof
Krzysztof
Reboot server once again.
Regards,
Krzysztof