Error 1753 Error 6d9 From Hrgetserversforrole Make
Ask Question Answer Questions My Profile ShortcutsDiscussion GroupsFeature RequestsHelp and SupportHow-tosIT Service ProvidersMy QuestionsApp CenterRatings and ReviewsRecent ActivityRecent PostsScript CenterSpiceListsSpiceworks BlogVendor PagesWindows Events Event 2152 (Error) Source: MSExchange ADAccess How important is this event? (1 vote) 1 2 3 4 5 not important very important Description This Windows Event does not have a description yet. Add link Text to display: Where should this link go? Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C C++ C# CSS ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL VB.net Vimscript XML YAML Insert Cancel Save Cancel Associated Messages Process w3wp.exe (PID=5836). An remote procedure call (RPC) request to the Microsoft Exchange Active Directory Topology service failed with error 1753 (Error 6d9 from HrGetTopologyVersion). 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.
Sep 08, 2009 Process w3wp.exe (PID=4916). An 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. Sep 08, 2009 Process mad.exe (PID=2168). 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. Jul 23, 2010 Process w3wp.exe (AutoDisc) (PID=2856). An 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 notcannot start. Eventvwr : MSExchange ADAccess Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1524). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). 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." Use the 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 https://community.spiceworks.com/windows_event/show/2585-msexchange-adaccess-2152 connectivity to 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 http://forums.msexchange.org/m_1800515072/printable.htm through this link: http://andreslozada.blogspot.com/2009/08/msexchange-adaccess-event-id-2114.html 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
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 https://www.experts-exchange.com/questions/23996429/AD-Access-problems.html Full Time Job Ways to Get Help Expand Search Submit Close Search http://jared-woodruff.blogspot.com/2012_10_01_archive.html Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > AD Access problems Want to Advertise Here? Solved AD Access problems Posted on 2008-12-18 Databases Exchange Active Directory MS Applications MS Server Apps 1 Verified Solution 8 Comments 5,276 Views Last Modified: error 1753 2013-12-24 Hi Two or tree times a day I have this event : Event Type: Error Event Source: MSExchange ADAccess Event Category: General Event ID: 2152 Date: 1/7/2008 Time: 1:27:56 AM User: N/A Computer: EXCHANGE64 Description: Process MSExchangeTransportLogSearch.exe (PID=1760). An error 1753 error 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. It returning to normal after 10 or 15 minutes. When I get this error my Exchange is becoming unusable for the Outlook users. Do you have an idea to fix this issu? Thanks Jean-Pierre 0 Question by:jpmoreau Facebook Twitter LinkedIn Google Active 5 days ago Best Solution byjpmoreau Thanks for the help I found the problem. I had my Linux router in the DNS server on the network card. I have removed it and now everything is OK. Jean-Pierre Go to Solution 7 Comments LVL 7 Overall: Level 7 Exchange 2 Active Directory 2 Message Expert Comment by:dphantom2008-12-19 Is your Exchange server pointed to a Windows DNS server or Linux/Unix? 0 Message Active 5 days ago Author Comment by:jpmoreau2008-12-19 Windows DNS Server I have 4 server in my Ntework with one is DNS Server Jean-Pierre 0 LVL 12
Techies and coders, Another Solution to an issue which might help you out. Problem Description: When Upgrading Exchange Server or CAS/HUB Transport server to Server 2008 R2 SP1 you notice the Server cant communicate to other Exchange Systems. Nor can you use Powershell to self manage it anymore. Cause When Upgrading the server to Service Pack 1, the installer disables all of the following service types: IIS Services Remote Registry Services Exchange Services World Wide Web Services It does this to prevent issues when the server resets after a major patch installation, however there is a 1 in 5 chance that it wont reset the service values back to "Automatic" which causes a bunch of errors like some shown below: Process w3wp.exe () (PID=xxx). 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. Error 0x80040115 occurred in module reset. (WEB Access) Sending email server operation timed out. The WinRM client cannot process the request. Solution Well in my case i had another CAS server to compare the services side by sideagainsteach other todeterminewhat was disabled thatshouldn'tbe, however for your basic CAS server these are (See Image) the services that would be automatic and started. If you have Scripts that run to generate reports on your exchange clusters then you need to make sure the following services are started: Remote Registry(Lets your scriptsdeterminethe current update rollup's and exchange versions.), IIS Admin Service &W3SVC. You will need to check your IIS Sites and running and contactable. Also if you