Exchange 2007 Front End server configuration help!
Im having a nightmare of a time upgrading this network to Exchange 2007. To give you some background the network used to be novel, then it was NT4, then 2000 Native, then 2003/200 mixed. Exchange 5.5 then Exchange 2000, then Exchange 2003. Ive finally gotten a new Exchange 2007 box up and running. Obviously had to bring the network to Server 2003 native mode, doing that actually broke several things and several ADSI Edits were required for single object permissions. This network is large enough where they have a front end exchange server that everyone connects to for OWA and for Outlook over HTTPS remotely. The second Exchange server Houses the mailbox databases. We are going to replace both of these with Exchange 2007 counterparts. The Hub/Transport/Mailbox installation of Exchange 2007 on the first server went fairly smoothly (aside from the individual AD object edits I mentioned before). However, when trying to set up a second server to have the Client Access and Hub Transport roles the installation fails at the Hub Transport Role with the Error Service MSExchangeTransport failed to reach status Running on this server. Below is an example of errors: Source: MSExcahnge ADAccess Category: Topology Event ID: 2114 Description: Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=2372). 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. Event ID: 2601 Description: Process MSEXCHANGEADTOPOLOGY (PID=2372). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account <WKGUID=DC1301662F547445B9C490A52961F8FC,CN=Microsoft Exchange,CN=Services,CN=Configuration,...> - Error code=80040a01. The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions. Ive looked online and found some Server 2008 information having to do with IPv6, but were using Server 2003. Do any of you have any thoughts, or can you point me in the right direction???Robert Farmer
August 18th, 2009 1:22am

Can you post event id 2080 coming up in Exchange server Application log to here? There must beSACL right showing 0 instead of 1. And also add Exchange server computer object into "Exchange Servers" Group and reboot the Exchange server so it willdefinitelyfind the domain controller available into AD Site...Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com
Free Windows Admin Tool Kit Click here and download it now
August 18th, 2009 8:52am

Added the server to the Exchange Servers group as well as the other groups the other exchange servers are members of and re-ran setup. Still errored out at the same step. But now i'm getting a new Error message in the Event log. First things first. You asked for Event 2080, it looks the same every time we run setup: Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1332). 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: gc.gem.local CDG 1 7 7 1 0 1 1 7 1 gemsrv.gem.local CDG 1 7 7 1 0 1 1 7 1 GEMDC.gem.local CDG 1 7 7 1 0 1 1 7 1 Out-of-site: For more information, see Help and Support Center at I will post the other error message in another reply since it is VERY long. Robert Farmer
August 18th, 2009 6:26pm

Two event Errors. First one is Event ID: 5003 Source: MSExchangeTransport Category: RoutingDescription: Microsoft Exchange couldn't load configuration information for routing. The process will block and retry the operation in 10 seconds.Second Error: Event ID: 5023 Source MSExchangeTransport Category: RoutingDescription:A transient configuration error was detected while the routing configuration was loading. Exception details: Unable to determine the local Active Directory site : Microsoft.Exchange.Transport.Categorizer.TransientRoutingException: Unable to determine the local Active Directory site at Microsoft.Exchange.Transport.Categorizer.AdSiteRelayMap.ValidateConfig(ExchangeTopology topology, ExEventLog eventLogger, DateTime timestamp) at Microsoft.Exchange.Transport.Categorizer.RoutingTables.ValidateConfig(RawRoutingConfigData rawConfigData) at Microsoft.Exchange.Transport.Categorizer.RoutingTables.PopulateTables(RawRoutingConfigData rawConfigData)All of my servers are running server 2003. This server has been registered in AD and can be seen on the network and has full network access and connectivity. Thoughts? Robert Farmer
Free Windows Admin Tool Kit Click here and download it now
August 18th, 2009 6:29pm

Looks likemsExchHomeRoutingGroup is not set or not have proper value, refer below article and see if it helps to start transport service... You cannot start the Microsoft Exchange Transport service on an Exchange Server 2007 Hub server http://support.microsoft.com/kb/948000Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com
August 18th, 2009 7:12pm

thanks for the help. I followed the article. Not really sure what got messed up but doing that fixed it and i was able to complete the installation! Much thanks!Robert Farmer
Free Windows Admin Tool Kit Click here and download it now
August 18th, 2009 8:36pm

You are welcome! :)Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com
August 18th, 2009 8:43pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics