{"id":358,"date":"2018-10-26T19:38:35","date_gmt":"2018-10-26T19:38:35","guid":{"rendered":"http:\/\/www.torontohelpdesk.ca\/blog\/?p=358"},"modified":"2018-10-26T19:43:13","modified_gmt":"2018-10-26T19:43:13","slug":"exchange-2010-sbs-2011-not-functioning-service-stuck-in-starting","status":"publish","type":"post","link":"https:\/\/www.torontohelpdesk.ca\/blog\/exchange-2010-sbs-2011-not-functioning-service-stuck-in-starting\/","title":{"rendered":"Exchange 2010 (SBS 2011) not functioning (some services stuck in starting mode)"},"content":{"rendered":"<p><strong>Problem:<\/strong><\/p>\n<p>After some sort of update, Exchange services stuck in starting and won&#8217;t start. Error messages include &#8220;Unexpected error Logon failure: unknown user name or bad password. Facility: LDAP Provider ID no: 8007052e Microsoft Exchange System Attendant occurred.&#8221;<\/p>\n<p><strong>Solution:<\/strong><\/p>\n<p>(h\/t <a href=\"https:\/\/support.microsoft.com\/en-ca\/help\/2751452\/dns-zones-do-not-load-event-4000-4007\">Microsoft)<\/a><\/p>\n<p>What I realized is that the issue was more rooted than just Exchange. When you try running DNS it comes back with a pop up that states &#8220;Access Denied&#8221;. If you check the FSMO roles, they all come back positive. DCDiag also has an error message.<\/p>\n<p>The solution ended up being quite simple (after hours of research). First off, we suggested bloody switching to Office 365 and then the following:<\/p>\n<ol>\n<li><span class=\"\" style=\"font-family: Tahoma; font-size: small;\">In case you have other Domain Controller\/ DNS server present in the environment then configure the server experiencing the issue to point to other active DNS server in TCP\/IP properties.<\/span><\/li>\n<li><span class=\"\" style=\"font-family: Tahoma; font-size: small;\">Stop the KDC service on the DC experiencing the issue.<\/span><\/li>\n<li><span class=\"\" style=\"font-family: Tahoma; font-size: small;\">Run the following command with elevated rights: netdom resetpwd \/server:&lt;PDC.domain.com&gt; \/userd:&lt;Domain\\domain_admin&gt; \/passwordd:*<\/span><\/li>\n<li><span class=\"\" style=\"font-family: Tahoma; font-size: small;\">It will prompt for the password of the Domain Admin account that you used, enter that.<\/span><\/li>\n<li><span class=\"\" style=\"font-family: Tahoma; font-size: small;\">Once the command executes, reboot the server.<\/span><\/li>\n<li><span class=\"\" style=\"font-family: Tahoma; font-size: small;\">DNS zones should load now.<\/span><\/li>\n<\/ol>\n<p class=\"\"><span style=\"font-family: Tahoma; font-size: small;\">If this is the only DC in the environment and there are no other DNS Servers available then perform the same steps but replate the &#8220;PDC.Domain.com&#8221; with the server&#8217;s own IP address (since it itself is the PDC)<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Problem: After some sort of update, Exchange services stuck in starting and won&#8217;t start. Error messages include &#8220;Unexpected error Logon failure: unknown user name or bad password. Facility: LDAP Provider ID no: 8007052e Microsoft Exchange System Attendant occurred.&#8221; Solution: (h\/t <a class=\"more-link\" href=\"https:\/\/www.torontohelpdesk.ca\/blog\/exchange-2010-sbs-2011-not-functioning-service-stuck-in-starting\/\">Continue reading <span class=\"screen-reader-text\">  Exchange 2010 (SBS 2011) not functioning (some services stuck in starting mode)<\/span><span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-358","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/posts\/358","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/comments?post=358"}],"version-history":[{"count":2,"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/posts\/358\/revisions"}],"predecessor-version":[{"id":360,"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/posts\/358\/revisions\/360"}],"wp:attachment":[{"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/media?parent=358"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/categories?post=358"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.torontohelpdesk.ca\/blog\/wp-json\/wp\/v2\/tags?post=358"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}