Failed With Error 1753 Error 6d9 From Hrgetserversforrole Make
DSAccess Errors ★★★★★★★★★★★★★★★ Vibha DeshpandeAugust 12, 20112 0 0 0 Heres another interesting Exchange case that I came across recently. After several Service Packs, updates (both MS and Non-MS), were applied on the server, we came across this issue of not being able to start the several Exchange Services. Events Logged were as follows: Process MAD.EXE (PID=4036). Topology discovery failed, error 0x80040952 (LDAP_LOCAL_ERROR (Client-side internal error or bad LDAP message)). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Process w3wp.exe () (PID=3160). An remote procedure call (RPC) request to the Microsoft Exchange Active Directory Topology service failed with error 1753 (Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from HrGetServersForRole). Make sure that the Remote Procedure Call (RPC) service is running. In addition, make sure that the network ports that are used by RPC are not blocked by a firewall. Process MSEXCHANGEADTOPOLOGY (PID=9608). When updating security for a remote procedure call (RPC) access for the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the security descriptor for Exchange server object DIAMONDSBS - Error code=80040a01. The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions. After several hours of troubleshooting when we tried to reinstall Exchange, it failed with : Error: The following error was generated when "$error.Clear(); initialize-ServerPermissions -DomainController $RoleDomainController " was run: "Could not find a directory entry for the local host.". Incidently it turned out to be an issue with the host file; It had the followi
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Exchange 2007 Server Information Store not mounting on reboot Want to Advertise Here? Solved Exchange 2007 Server Information Store not mounting on reboot Posted on 2009-02-16 Exchange Windows Server 2003 Windows Networking 1 Verified Solution 7 Comments 3,899 https://blogs.technet.microsoft.com/vibhade/2011/08/12/unable-to-start-exchange-services-with-dsaccess-errors/ Views Last Modified: 2012-05-06 We have a new Exchange 2007 server setup that we just migrated from SBS 2003. I'm getting some weird errors after just rebooting the server though : looks like it won't let the Information Store mount upon bootup, I have to manually start this service as well as MS System Attendant. Here are the following error messages I get in the event log https://www.experts-exchange.com/questions/24147439/Exchange-2007-Server-Information-Store-not-mounting-on-reboot.html after a reboot : yes all of them in a row. A manually start of the services MSSA and the Information Store gets everything working fine, this only happens after a reboot. Windows cannot determine the user or computer name. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted. Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1460). None of the domain controllers in the domain are responding. This event can occur if the domain controllers in local or all domains become unreachable because of network problems. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers. Run the Dcdiag command line tool to test domain controller health. Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1460). Exchange Active Directory Provider found SRV records for domain controllers in domain lle.local. The query was for the SRV record for _ldap._tcp.dc._msdcs.lle.local The following domain controllers were identified by the query: llesrv00.lle.local llesrv01.lle.local Unexpected error No authority could be contacted for authentication. ID no: 80090311 Microsoft Exchange System Attendant occurred. Microsoft Exchange System Attendant failed to start. Process utilCmdletWrapper.exe (EMS) (PID=2896). An remote procedure call (RPC) request to the Microsoft Exchange Active Directory Topology service failed with error 1753 (Error 6d9 from HrGetServersForRole).
cannot start. Eventvwr : MSExchange ADAccess Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1524). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the http://forums.msexchange.org/m_1800515072/printable.htm Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the http://knicksmith.blogspot.com/2007/03/managing-exchange-2007-recipients-with.html information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to failed with local domain controllers. MSExchangeIS Unable to initialize the Microsoft Exchange Information Store service. - Error 0x96f. We can ping or pathping to DC 10.3.3.10. I am out of ideas, please help. Thanks and Regards ismail.mohammed -> RE: The information store service cannot start (11.Aug.2009 4:49:49 AM) hi mate, have you gone through this link: http://andreslozada.blogspot.com/2009/08/msexchange-adaccess-event-id-2114.html failed with error ctvu -> RE: The information store service cannot start (11.Aug.2009 5:18:06 AM) Thank you for your help. But we did not install IPv6. To me there is something wrong with AD and Exchange Thanks and Regards ismail.mohammed -> RE: The information store service cannot start (11.Aug.2009 5:30:54 AM) What is the current OS version on which you have installed Exchange 2007. Run the Exbpa as well ctvu -> RE: The information store service cannot start (11.Aug.2009 5:39:06 AM) It is wins 2003 R2 SP1. Exchage 07 RTM. Thanks ismail.mohammed -> RE: The information store service cannot start (11.Aug.2009 6:52:54 AM) hi mate, See this link: http://forums.msexchange.org/m_1800430290/printable.htm http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploy/thread/1534ef63-ae09-4dee-8fbe-f19e5c21279d ctvu -> RE: The information store service cannot start (11.Aug.2009 9:00:21 AM) Thanks again for your help. Actually I have read them too. In regards to GPO we did not define this. with thesecond link I will rerun setup /prepareAD and I will let you know how I go Much appreciated your help Regards ism
of integrating Exchange 2007 recipient management with our in-house identity management systems. Our active directory provisioning code was already written in .Net and implemented CDOEXM for recipient management. One of the things that concerned me the most about migrating to Exchange 2007 was the ability to manage recipients from within the existing code. CDOEXM is not supported for managing Exchange 2007 recipients and the idea of invoking the Exchange management shell from .Net code was a foreign concept to me. Information on how to do so was sparse. Many many thanks to Vivek Sharma for posting sample code before anything else was available. My early code was based directly off his examples. Since then I have created a few applications using these methods and I have learned quite a few lessons while doing so. Below are some of my experiences and customizations that made the process much simpler.Web ReferencesFirst, here are some helpful links to get started with invoking the management shell from C# code:Creating Applications that Use the Default Hosthttp://msdn2.microsoft.com/en-us/library/ms714671.aspxMstehle's Introduction to Exchange Powershell AutomationPart 1: http://blogs.msdn.com/mstehle/archive/2007/01/25/fyi-introduction-to-exchange-powershell-automation-part-1.aspxPart 2: http://blogs.msdn.com/mstehle/archive/2007/01/25/outbox-introduction-to-exchange-powershell-automation-part-2.aspxSample Code: Calling Exchange cmdlets from .Net codehttp://www.viveksharma.com/techlog/2006/07/27/sample-code-calling-exchange-cmdlets-from-net-codeCaveatsCreating the necessary Runspace and RunspaceInvoke instances will take 2-3 seconds to get setup in a compiled application. It can take 6-9 seconds to execute the first Exchange command on a computer with only the Exchange 2007 management tools installed. You may also receive the following errors in the event log:Event Type: ErrorEvent Source: MSExchange ADAccessEvent Category: GeneralEvent ID: 2152Date: 3/26/2007Time: 7:38:52 PMUser: N/AComputer: HASTYDescription:Process eIDAD.exe (PID=2984). A remote procedure call (RPC) request to the Microsoft Exchange Active Directory Topology service failed with error 1753 (Error 6d9 from HrGetServersForRole). Make sure that the Remote Procedure Call (RPC) service is running. In addition, make sure that the network ports that are used by RPC are not blocked by a firewall.Event Type: ErrorEvent Source: MSExchange CommonEvent Category: DevicesEvent ID: 106Date