Error 1753 Error 6d9 From Hrgetserversforrole
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 Topolfor 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,892 Views Last Modified: 2012-05-06 We have a https://community.spiceworks.com/windows_event/show/2585-msexchange-adaccess-2152 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 after a reboot : yes all of them in a row. https://www.experts-exchange.com/questions/24147439/Exchange-2007-Server-Information-Store-not-mounting-on-reboot.html 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). Make sure that the Remote Procedure Call (RPC) service is running. In addition, make sure that the network ports that are
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 https://www.experts-exchange.com/questions/23996429/AD-Access-problems.html 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 http://microsoft.programming4.us/forums/t/172643.aspx 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 error 1753 Verified Solution 8 Comments 5,276 Views Last Modified: 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: error 1753 error N/A Computer: EXCHANGE64 Description: Process MSExchangeTransportLogSearch.exe (PID=1760). 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. 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
Hardware, Server, Internet Protocols, Database, Exchange . » OS » Server » SBS Small Business Server » Emergency! Exchange not starting after SBS 2008 reboot Emergency! Exchange not starting after SBS 2008 reboot 05-10-2010 11:58 PM Emergency! Exchange not starting after SBS 2008 reboot Rebooted SBS 2088 server , the server installed a few windows updates then shutdown and restarted . After the box was up exchange will not start. lots of errors in the logs:event id 2600:Process MSEXCHANGEADTOPOLOGY (PID=5812). DSAccess could not initiate a remote procedure call (RPC) - Call=RegisterRPCProtseqsAndAuth Error code=80070057.event id 1015:Exchange ActiveSync experienced a transient error when it tried to access Active Directory information for user "". Exchange ActiveSync will try this operation again. If this event occurs infrequently, no user action is required. If this event occurs frequently, check network connectivity using PING or PingPath. You can also use the Test-ActiveSyncConnectivity cmdlet. More information: Microsoft.Exchange.Data.Directory.ADTransientException: Exchange Active Directory Topology Service on server localhost cannot be contacted via RPC interface. Error 0x6D9. ---> Microsoft.Exchange.Rpc.RpcException: Error 6d9 from HrGetServersForRole at Microsoft.Exchange.Rpc.ADTopology.ADTopoRpcClient.HrGetServersForRole(String[ currentlyUsedServers, ServerRole role, Int32 serversRequested, ServerInfo[& suitableServers, Int32[& mapping) at Microsoft.Exchange.Data.Directory.DSAccessTopologyProvider.GetServersForRole(String[ currentlyUsedServers, ADServerRole role, Int32 serversRequested, Int32[& mapping) --- End of inner exception stack trace --- at Microsoft.Exchange.Data.Directory.DSAccessTopologyProvider.GetServersForRole(String[ currentlyUsedServers, ADServerRole role, Int32 serversRequested, Int32[& mapping) at Microsoft.Exchange.Data.Directory.DSAccessTopologyProvider.GetConfigDCInfo(Boolean throwOnFailure) at Microsoft.Exchange.Data.Directory.TopologyProvider.PopulateConfigNamingContexts() at Microsoft.Exchange.Data.Directory.TopologyProvider.GetConfigurationNamingContext() at Microsoft.Exchange.Data.Directory.ADSession.GetConnection(String preferredServer, Boolean isWriteOperation, Boolean isNotifyOperation, ADObjectId& rootId) at Microsoft.Exchange.Data.Directory.ADSession.GetReadConnection(String preferredServer, ADObjectId& rootId) at Microsoft.Exchange.Data.Directory.ADSession.Find(ADObjectId rootId, String optionalBaseDN, ADObjectId readId, QueryScope scope, QueryFilter filter, SortBy sortBy,