Process Inetinfo Exe Topology Discovery Failed Error 0x8007077f
Contents |
Active Directory Integration Tool Services Exchange Active Directory SharePoint OCS/Lync Customer Success Blog Support ENow Exchange & Office 365 Solutions Engine Blog (ESE) Exchange Can't Start Due to Misconfigured AD Sites Posted by Michel de exchange 2013 topology discovery failed Rooij on Aug 8, 2012 1:38:00 PM Find me on: Facebook LinkedIn Twitter microsoft exchange active directory topology service wont start Tweet Recently, a customer had issues with their Exchange server which didn’t start properly after rebooting. After
The Microsoft Exchange Active Directory Topology Service On Server Localhost Did Not Return
checking out the Eventlog, I noticed that it was full of messages, generated by all services. The most interesting events were the ones generated by MSExchange ADAccess: MSExchange ADAccess, EventID 2141
Process Msexchangeadtopologyservice.exe Topology Discovery Failed Error 0x80040a02
Process STORE.EXE (PID=2996). Topology discovery failed, error 0x8007077f MSExchange ADAccess, EventID 2142 Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1760). Topology discovery failed, error 0x8007077f Also, the results of the active directory discovery process generated every 15 minutes, which are normally logging in event 2080, “Exchange Active Directory Provider has discovered the following servers with the following characteristics”, was missing. Note that because the system could start msexchangeadtopologyservice.exe all domain controller servers in use are not responding the Microsoft Exchange Active Directory Topology service (until it failed and is restarted by dependent services), Exchange’s other services were also triggered, leading to almost indefinitely restarting services as configured in their corresponding service recovery actions sections. Now, since I had connected to a domain controller using an RDP session from my client, and I was able to connect to port 389 (Global Catalog) from Exchange using LDP, the communications looked fine. Then, I switched to Active Directory Sites and Services: As you can see from the shot, this was a potential cause of the problem. First, there was a site without domain controllers. Second, there were no subnets defined. So, in this situation, it is undetermined in which site Exchange is located. When a system can’t determine in which site a computer belongs, the function DSGetSiteName, used to retrieve the current site, returns an error 1919 0x77f (ERROR_NO_SITENAME). Consequently, the Exchange Active Directory discovery process fails and eventually Exchange fails. You can inspect the current discovered site usingnltest/dsgetsiteor by having a peek in the registry at HKLM\System\CurrentControlSet\Services\Netlogon\Parameters\DynamicSiteName. Now, to solve the si
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked
Microsoft Exchange 2013 Active Directory Topology Service Failed To Start
by: Services are not starting on exchange 2003 after moving exchange 2013 active directory topology service wont start branch office Previous Versions of Exchange > Exchange 2003 and Exchange 2007 - General Discussion microsoft exchange active directory topology service dependencies Question 0 Sign in to vote Dear Friends, i prepared one exchange server in my H.0 ,MY installation sucess moved some users and http://blog.enowsoftware.com/solutions-engine/bid/132664/Exchange-Can-t-Start-Due-to-Misconfigured-AD-Sites tested mail flow all are fine,after this i moved same server to my branch and i changed ip address and logged in the server bunt non of exchange services are started and throughing following event ids........ Application Log:-----2114 and 1005 Event Type: ErrorEvent Source: MSExchangeDSAccessEvent Category: Topology Event ID: 2114Date: 8/12/2007Time: 3:15:46 PMUser: N/AComputer: MINAEXCHDescription:Process https://social.technet.microsoft.com/Forums/exchange/en-US/910c2761-1051-4e76-9cc6-784b7a24154b/services-are-not-starting-on-exchange-2003-after-moving-branch-office?forum=exchangesvrgenerallegacy MAD.EXE (PID=2484). Topology Discovery failed, error 0x8007077f. For more information, click http://www.microsoft.com/contentredirect.asp. Event Type: ErrorEvent Source: MSExchangeSAEvent Category: General Event ID: 1005Date: 8/12/2007Time: 3:15:39 PMUser: N/AComputer: MINAEXCHDescription:Unexpected error No site name is available for this machine. Facility: Win32 ID no: c007077f Microsoft Exchange System Attendant occurred. For more information, click http://www.microsoft.com/contentredirect.asp. in system log:--- 7001 and 7026 Event Type: ErrorEvent Source: Service Control ManagerEvent Category: NoneEvent ID: 7001Date: 8/12/2007Time: 3:16:52 PMUser: N/AComputer: MINAEXCHDescription:The Microsoft Exchange Information Store service depends on the Microsoft Exchange System Attendant service which failed to start because of the following error: The operation completed successfully. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: ErrorEvent Source: Service Control ManagerEvent Category: NoneEvent ID: 7026Date: 8/12/2007Time: 3:16:52 PMUser: N/AComputer: MINAEXCHDescription:The following boot-start or system-start driver(s) failed to load: SCSIChanger For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. i checked all my ports opened in my router between my H.O & Branch.and i gone through all microsoft articles but i did`t ge
| My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out Topology Discovery Failed. Users viewing this topic: none Logged in as: Guest Tree Style Printable Version All Forums >> [Microsoft Exchange http://forums.msexchange.org/Topology_Discovery_Failed%25/m_1800421790/tm.htm 2003] >> General >> Topology Discovery Failed. Page: [1] Login Message << Older Topic Newer http://www.eventid.net/display-eventid-2114-source-MSExchangeDSAccess-eventno-2458-phase-1.htm Topic >> Topology Discovery Failed. - 7.Nov.2006 6:49:41 PM rakem Posts: 35 Joined: 31.Jan.2006 Status: offline I have just installed Exchange 2003 and SP1 onto a new 2003 R2 server. forestprep and domain prep ran without any problems, however the following services will not star: MS Exchange Information Store MTA Stacks System Attendant Im getting event ID 2114 logged active directory in event viewer saying that: "Process INETINFO.EXE (PID=1592). Topology Discovery failed, error 0x80040a02. " Our domain set up is one domain name with multiple sites, each site has its own DC which is also a GC and also every DC is a DNS server. The site that the exchange server is in has two DCs, both are GCs and DNS servers. The exchange server uses them as its primary and seccondary DNS servers. I have full connectivity between active directory topology all sites, I access active directory from the exchange server. Can anyone provide some trouble shooting tips please! thanks. Post #: 1 Featured Links* RE: Topology Discovery Failed. - 7.Nov.2006 11:10:54 PM jchong Posts: 2516 Joined: 1.Dec.2005 From: Centreville, Virginia Status: offline Please run Exchange Best Practice analyzer first, let's start with the basics such as DNS issues, network issues etc. EBPA will perform these tests, please post results. _____________________________James Chong MCSE | M+, S+, MCTS, Security+ msexchangetips.blogspot.com (in reply to rakem) Post #: 2 RE: Topology Discovery Failed. - 8.Nov.2006 12:23:02 AM rakem Posts: 35 Joined: 31.Jan.2006 Status: offline actually there is no need i managed to fix it!! the problem was that the Exchange Enterprise Servers group was not in the manage auditing and security log policy on the default domain policy. Once i placed it in there all the services started up and its all go! (in reply to jchong) Post #: 3 RE: Topology Discovery Failed. - 8.Nov.2006 2:00:59 AM BeTaCam Posts: 420 Joined: 24.Feb.2003 From: India Status: offline Check permisisons on the Logs. HTH BC (in reply to rakem) Post #: 4 Page: [1] << Older Topic Newer Topic >> All Forums >> [Microsoft Exchange 2003] >> General >> Topology Discovery Failed. Page: [1] Jump to: Select a ForumAll Forums---------------------- [Microsoft Office 365] - - Exchange Online [Microsof
Monitor an unlimited number of servers with $49/year With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common to see an entire company using just one server, these days that's no longer the case. New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers. read more... Event ID: 2114 Source: MSExchangeDSAccess Source: MSExchangeDSAccess Type: Error Description:Process INETINFO.EXE (PID=241).Topology Discovery failed, error 0x80040a02. English: This information is only available to subscribers. An example of English, please! Concepts to understand: What is the role of the Microsoft Exchange Directory service? Comments: Ajay Kulshreshtha In our case, the only DC in the site where Exchange 2003 was located had gone down. We had to remove the IP of this DC from DNS settings and also move that subnet (in AD Sites and Services) to the remote site whose DCs were available. x 319 CPonton924 Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this use ME218185 (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 connectivity to local domain controllers. x 339 EventID.Net Different processes and different errors can be reported with this event and one should carefully consider the troubleshooting as they may apply to different instances of this problem. The PID (process ID) is irrelevant as it is specific to that running session of Exchange. Process: MSEXCHANGEADTOPOLOGYSERVICE.EXE, error: 0x80040a02 (DSC_E_NO_SUITABLE_CDC).- Error translates to 'The wait operation timed out.' It is possible that the Exchange component was unable to reach the Active Directory or the computer running Exchange is not powerfull enough to meet the demands of Exchange (see the "Guide to Monitoring the Performance of your Exchange Server" blog for suggestions on monitoring the Exchange performance. An interesting discussion about this can be found on Technet - see the "MSExchangeADTopology failed to start" link. Process: EXMGMT.EXE, Error code 0x8007077f. From a support forum: - Corrected OWA and IIS configuration based on