Hi guys, I'm installing the Hub Transport, CAS and Mailbox role but I have encountered this error in the EventLog: The Microsoft Exchange Active Directory Topology service terminated with service-specific error 2147942658 (0x80070102). Anyidea??

That error translates to 'The wait operation timed out.' Do you know if your system meets the minimum requirements for installing and running Exchange 2007?

Scott Schnoll - MSFT wrote:That error translates to 'The wait operation timed out.' Do you know if your system meets the minimum requirements for installing and running Exchange 2007? Hi Scott, I'm installing the Beta 2 on HP BL25 (AMD x64), with Windows Server 2003 Ent. Edition, x64.My lab forest (1 root, 2 child) is in a VMWare enviroment

Did you actually have a setup failure or are you just monitoring the eventlog? If the service still fails to start after replication you can restart it manually by doing: start-service *topology* Thanks, ~vivek

Hi Vivek, yes, this is a setup failure. In fact, I have other issues....so I think that the best thing is post the application log error: Event Type:InformationEvent Source:MSExchangeADAccessEvent Category:Topology Event ID:2080Date:8/4/2006Time:9:17:52 AMUser:N/AComputer:MILEX2007ADescription:Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=208). Exchange Active Directory Provider has discovered the following servers with the following characteristics: (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version) In-site:labdc0.esselunga.labCDG 1 7 7 1 0 0 1 7 1millabdc0.mil.esselunga.labCDG 1 7 7 1 0 0 1 7 1neglabdc0.neg.esselunga.labCDG 1 7 7 1 0 0 1 7 1Out-of-site: Event Type:ErrorEvent Source:MSExchangeADAccessEvent Category:Topology Event ID:2114Date:8/4/2006Time:9:17:52 AMUser:N/AComputer:MILEX2007ADescription:Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=208). Topology Discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Event Type:ErrorEvent Source:MSExchange TransportEvent Category:Configuration Event ID:16023Date:8/3/2006Time:5:19:20 PMUser:N/AComputer:MILEX2007ADescription:Failed to start transport agents. The transport service will be stopped. Exception details: Failed to create type 'Microsoft.Exchange.MessagingPolicies.TransportRuleAgent.TransportRuleAgentFactory' from assembly 'C:\Program Files\Microsoft\Exchange Server\TransportRoles\agents\Rule\Microsoft.Exchange.MessagingPolicies.TransportRuleAgent.dll' due to error 'Agent Transport Rule failed to register for configuration change notifications.'. : Microsoft.Exchange.Data.ExchangeConfigurationException: Failed to create type 'Microsoft.Exchange.MessagingPolicies.TransportRuleAgent.TransportRuleAgentFactory' from assembly 'C:\Program Files\Microsoft\Exchange Server\TransportRoles\agents\Rule\Microsoft.Exchange.MessagingPolicies.TransportRuleAgent.dll' due to error 'Agent Transport Rule failed to register for configuration change notifications.'. ---> Microsoft.Exchange.Data.ExchangeConfigurationException: Agent Transport Rule failed to register for configuration change notifications. ---> Microsoft.Exchange.Data.Directory.NoSuitableServerFoundException: The Exchange Topology service did not return a suitable Domain Controller. 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, Int32& maxRetries) at Microsoft.Exchange.Data.Directory.ADSession.GetReadConnection(String preferredServer, ADObjectId& rootId, Int32& maxRetries) at Microsoft.Exchange.Data.Directory.ADSession.Find(ADObjectId rootId, String optionalBaseDN, ADObjectId readId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCtor, CreateObjectsDelegate arrayCtor) at Microsoft.Exchange.Data.Directory.ADSession.Find(ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCtor, CreateObjectsDelegate arrayCtor) at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.Microsoft.Exchange.Data.IConfigDataProvider.Find[T](QueryFilter filter, ObjectId rootId, Boolean deepSearch, SortBy sortBy) at Microsoft.Exchange.MessagingPolicies.Rules.ADRuleStorageManager..ctor(String ruleCollectionName, IConfigDataProvider session) at Microsoft.Exchange.MessagingPolicies.TransportRuleAgent.TransportRuleAgentFactory.RegisterConfigurationChangeHandlers() at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount) at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount) --- End of inner exception stack trace --- at Microsoft.Exchange.MessagingPolicies.TransportRuleAgent.TransportRuleAgentFactory..ctor() --- End of inner exception stack trace --- at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable.CreateAgentFactory(AgentInfo agentInfo) at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable..ctor(IEnumerable agents) at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.RuntimeSettings..ctor(MExConfiguration config, String agentGroup) at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExRuntime.Initialize(String configFile, String agentGroup) at Microsoft.Exchange.Transport.Categorizer.MExEvents.Initialize(String configFilePath) at Microsoft.Exchange.Transport.Components.CategorizerMExRuntimeLoader.Load() Event Type:InformationEvent Source:MSExchange TransportEvent Category:Components Event ID:7001Date:8/3/2006Time:5:19:20 PMUser:N/AComputer:MILEX2007ADescription:The service will be stopped. Reason: Failed to create type 'Microsoft.Exchange.MessagingPolicies.TransportRuleAgent.TransportRuleAgentFactory' from assembly 'C:\Program Files\Microsoft\Exchange Server\TransportRoles\agents\Rule\Microsoft.Exchange.MessagingPolicies.TransportRuleAgent.dll' due to error 'Agent Transport Rule failed to register for configuration change notifications.'. How can you see, there are some problems with the AD Topology service and the Transport service too.

The long stack trace is a red herring, the key is the error before where topologydiscovery failed. Is your server properly configured as part of an AD site (maybe replication issues here)? We usually see this error if the AD config cannot be read properly at service startup---adTopologyService is used by basically every Exchange Service to discover the current site, the servers within that site etc. Thanks, ~vivek

Vivek Sharma - MSFT wrote: The long stack trace is a red herring, the key is the error before where topologydiscovery failed. Is your server properly configured as part of an AD site (maybe replication issues here)? We usually see this error if the AD config cannot be read properly at service startup---adTopologyService is used by basically every Exchange Service to discover the current site, the servers within that site etc. Thanks, ~vivek I have the AD infrastructure on subnet 10.254.20.x/24 and the EX2007 server on subnet 10.254.136.x/23, both on the same site. Note that in this AD enviroment I've arleady deployed the E12 Beta1, DF3 and DF4 bits whith their relatives schema update.

I think you sort of sidestepped the question :-) Do you have proper AD Sites and Subnets set up within AD Sites and Services? If you don't have a subnet assigned toa Site, then the servers won't automatically discover which site they are part of (I believe that's how it works).

Ben Winzenz wrote:I think you sort of sidestepped the question :-) Do you have proper AD Sites and Subnets set up within AD Sites and Services? If you don't have a subnet assigned toa Site, then the servers won't automatically discover which site they are part of (I believe that's how it works). Yes, both subnets are included on the Default-First-Side-Name

Did you install and remove Exchange Server DF9 or earliar version before you install again on removed all Exchange Server role? I get a same problem. Toresolve this problem, get following task : 1. When remove Exchange Server, do not use exsetup.exe util. You can use Add or Remove Programs(uncheck server role). 2. Rename "Exchange Server" Folder in c:\program files\microsoft\ to "Exchange Server_Old" 3. Remove "Microsoft Exchange Security Groups" OUand "Microsoft Exchange System Objects" CN ifserverthat last Exchange server of your Exchange Org. 4. Try to install your new Exchange Org.

I am also having this problem. It appears to only be an issue with the client access role. During the install I watched themsExchangeADTopology service stay at a starting status. As soon as it failed and I ended setup I was able to go in and start the service no problem. Once the service was started I used add/remove to add the Client Access role. This time with the service running it was successful but the system tools were not working properly. I the Hub server I have installed it shows the Client Access Server but has a "!" on it. I have now uninstalled all and will try again. Any suggestions appreciated.

Pwsong wrote: Did you install and remove Exchange Server DF9 or earliar version before you install again on removed all Exchange Server role? [cut] No, I'm using a new, scratched Blade for the Beta 2..........

Joel Engstrom wrote: I am also having this problem. It appears to only be an issue with the client access role. During the install I watched themsExchangeADTopology service stay at a starting status. As soon as it failed and I ended setup I was able to go in and start the service no problem. Once the service was started I used add/remove to add the Client Access role. This time with the service running it was successful but the system tools were not working properly. I the Hub server I have installed it shows the Client Access Server but has a "!" on it. I have now uninstalled all and will try again. Any suggestions appreciated. Well, I have uninstall all the roles, re-boot the server, delete the Microsoft/Exchange Server directory (why is it not deleted by the uninstall procedure?) and re-install the CAS role: as a result, the msExchangeADTopology failed to start with this Application Log warning(!!): Event Type:WarningEvent Source:MSExchangeADAccessEvent Category:General Event ID:2602Date:8/21/2006Time:5:10:21 PMUser:N/AComputer:MILEX2007ADescription:Process MSEXCHANGEADTOPOLOGY (PID=196). Failed to flush Kerberos ticket for local system account - Error code=80070102. Microsoft Exchange AD Topology service will continue starting but the service may be using a token with an out-of date group membership. As a result access to Active Directory may fail with access denied. This failure might be critical during setup. If it happens during normal operation, it can be ignored.

Hi, Little late reply for this discussion ... buti recently ran into the same errors. I found outthat the 'SACL right' value for all Exchange Active Directory Providers' is zero (EventID 2080). See Q316300 for explaination. Apparently the Exchange Server server's computeraccount has insufficient rights to read Active Directory to perform the operations(?). Making the server's computeraccount member of the Domain Admins group results in a 1 for the 'SACL right' value. After this, Topology Discovery was succesful, my Exhange Transport Agent succeeded to start and finally Exchange 2007 b2 (re-re-re)installed succesfully. Paul de Lange

I had the same. Re-installation was not necessary. Just added the Exchange Server's account to the Domain Admin group and rebooted. Worked fine for me.

Do u means the "Exchange Servers" universal group? which not allow to add because this is universal group. Do you mind stay more specific? Because I have same problem when installing my first e2k7 server. thanks in advance! here is the error in eventlog: Event Type:ErrorEvent Source:MSExchange ADAccessEvent Category:Topology Event ID:2114Date:2/15/2007Time:9:01:01 AMUser:N/AComputer:<computer name> Description:Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=864). 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 connectivity to local domain controllers. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Having read the trace and - I do have IP Subnet registered under DefaultFirstSite. I got this error after unsuccessfully installing ForeFront for Exchange (and then removing it). It appears that the ForeFront installation leaves some sort of remnant after uninstall: Event Type:ErrorEvent Source:MSExchangeTransportEvent Category:Configuration Event ID:16023Date:20/04/2007Time:2:57:25 PMUser:N/AComputer:HOSTDescription:Microsoft Exchange couldn't start transport agents. The Microsoft Exchange Transport service will be stopped. Exception details: Failed to create type 'Antigen.AntigenRoutingAgentFactory' from assembly 'C:\Program Files\Microsoft\Exchange Server\TransportRoles\agents\FSEAgent\Bin\FSEAgent_8.0.685.dll' due to error 'Invalid agent assembly path.'. : Microsoft.Exchange.Data.ExchangeConfigurationException: Failed to create type 'Antigen.AntigenRoutingAgentFactory' from assembly 'C:\Program Files\Microsoft\Exchange Server\TransportRoles\agents\FSEAgent\Bin\FSEAgent_8.0.685.dll' due to error 'Invalid agent assembly path.'. ---> System.ArgumentException: Invalid agent assembly path. --- End of inner exception stack trace --- at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable.CreateAgentFactory(AgentInfo agentInfo) at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable..ctor(IEnumerable agents) at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.RuntimeSettings..ctor(MExConfiguration config, String agentGroup) at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExRuntime.Initialize(String configFile, String agentGroup) at Microsoft.Exchange.Transport.Categorizer.MExEvents.Initialize(String configFilePath) at Microsoft.Exchange.Transport.Components.CategorizerMExRuntimeLoader.Load()

I've just had the same problem.. Make sure you have your DNS set correctly and that you have replicated your DC's before running the Exchange setup.. I'm setting up a new site with two new Servers and I think I rushed it a little.. Andrew.

I also am having this issue...adding the machine account to domain admins works, but do you really want to have a machine in the domain admins group?

Same Here, I just added the Exchange Server to Domain Admin group and all worked.

Ok guys maybe it's too late maybe not for resolving the Problems Event ID: 2152 Event 2080 even when you erased the user profile from de server, even when you logon with another admin account. Finally the solution was in my case: removing the exchange groups from the admin exchange account, wait for the replication (5 minutes) with all domain controllers, add again the exchange enterprise groups for the account tha you wanna install exchange server, in my case the 2nd installation for a DRP (disaster resource planning) and bingo no more 2152 problems. After all recommendation from miscrosoft experts, dell server care, everything that was the solution for me! Thanks everyone!

Ya, adding the Exchange server to the domain admins group worked for me. This was in a fresh 2003 forest with one 2008 DC in a lab situation. Never got this error before.

Adding your Exchange server to the domain admins is not verry sain.Instead check if your computer account is part of the Exchange Server Group.

I had disabled IPv6 as well. Re-enabling it fix the install.Thanks for posting.

Same problem here but now in Exchange 2010, got it resolved by disabling IEv6.Could some please explain how is exchange hub role installtiondependent on enabling or disabling of IEv6.Thanks in advance

Same here on the IPv6. Thanks Marc

Hi guys, I'm installing the Hub Transport, CAS and Mailbox role but I have encountered this error in the EventLog: The Microsoft Exchange Active Directory Topology service terminated with service-specific error 2147942658 (0x80070102). Anyidea?? We received this error on our new Exchange 2007 CAS server as well. It was a fresh install into a pre-existing exchange 2003 environment. What I have found is that we restrict access to the security logs on all machines (pc's and servers) to the enterprise admin group via group policy. For testing I put the computer account in the enterprise admin group, rebooted and it resolved the error message.Our group policy is configured this way to meet strict compliance measures, so obviously I cannot leave the machine account in this over-privledged group. We'll have to customize the policy or create a new OU without the policy for the new exchange 2k7 servers.

I had the same problem. Had IPv6 enabled, set up Exchange and then disabled it. After re-enabling IPv6 everything was fine.Travis Wright Senior Program Manager Lead Microsoft

Apologies, above did not resolved my issue, but what did was to re-enable the IPv6 protocol's on the NiCs. Once these were used, the installion flew through successfully !

I had the same issue while peforming Exchange 2007 Disaster recovery on my lab which was failing. As per your resolution i added my Server to the menber of "Exchange Install Domain Servers" which resolved my issue. And my mistake was that instead of resetting the computer account (Exchange Server Name) from AD. I deleted that computer account which was my mistake.

Check your DNS server and check whether _pdc record is exists or not in _msdcs.yourdomain.com zone?

Check and see the NIC card binding order to see the NIC that you use to communicate to the Domain Controller is on top. You can also run a dcdiag test pointing to the DC from Exchange Server and check for errors or warnings.Ashwin Raj

Yep I have been there too. I did it al. Reactivating the computer account on the newerk, checked the computer rights..etc etc etc. but nothing seems to help. Ok..after a couple of hours i found the problem. I was doing a Windows 2003 to windows 2008 domain migration. I stil had an 2003 server active as AD GC. The problem was after i reset the net 2008 AD GC server, The exchange server was pointing to the old 2003 AD. When i shutdown the old 2003 server, the exchange 2010 server was up and running again. i starten teh 2003 server up again and removed it as AD from the domian. I hope this can help. cheers all Peter Jonkers Netherlands

Same: for me I had forgotten, but must have turned off IPv6 in the nic properties ages ago when i first installed the server OS. Turned it back on and re-ran the setup.

I had an unsuccessful installation of Exchange 2010 and, upon some advice from one with more experience than I, rebuilt my Exchange server VM and removed the Exchange server from AD. After performing a new installation, the hub transport role wouldn't start. This was the error in the installation log that got me started. Hub Transport Server Role ......................... FAILED The following error was generated when "$error.Clear(); if ($exsSid -eq $null -or $exsSid -eq "") { $exsSid = get-ExchangeServerGroupSID -DomainController$RoleDomainController } start-setupservice -ServiceName MSExchangeADTopology -ServiceParameters $exsSid,$RoleDomainController" was run: "Service 'MSExchangeADTopology' failed to reach status 'Running' on this server.". Subsequent errors in the event log were: Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=2940). 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 connectivity to local domain controllers. Process MSEXCHANGEADTOPOLOGY (PID=2940). The site monitor API was unable to verify the site name for this Exchange computer - Call=HrSearch Error code=80040a01. Make sure that Exchange server is correctly registered on the DNS server. These errors led me to this thread. In Active Directory Users and Computers, I went to the Microsoft Exchange Security Groups folder and found the Exchange Servers group. I added my exchange server computer name to the group and rebooted. The Microsoft Exchange Transport service started and the errors were no longer being logged to the event log. Russ

Glyn2 - You're a total star mate, have been trying to fix this since Sunday! Adding the new server name into the groups you've suggested has done the trick and recovery now running through OK. member of the following additional groups: "Exchange Servers", "Exchange Domain Servers", Exchange Install Domain Servers" , and "Exchange Trusted Subsystem"

thanks to all repliers to solve this problem, enable ipV6 on your NICs and also in AD site and services console, create subnets and set your default first site in that subnet