26 C
Dubai
Tuesday, April 16, 2024

Exchange 2013 Transport Service not starting :Unable to determine the local Active Directory site

On a New Exchange 2013 Installation – Transport Service was not starting and setup was keep failing.

 

Event viewer details  –

Log Name: Application
Source:   MSExchangeTransport
Event ID: 5023
Task Category: Routing
Level:    Error
Computer: SCHOEXCH01.careexchange.in
Description:

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.RoutingTopology.Validate()
at Microsoft.Exchange.Transport.Categorizer.RoutingTablesLoader.<>c__DisplayClass3.<TryLoadRoutingTablesAndNotify>b__2()
at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount)
at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount)

 

Resolution:

Open Adsiedit.msc – Browse to below location in the configuration partition

Configuration – Services – Microsoft Exchange – First Organization –  Exchange administrative group – Servers

image

Fill in the attribute – msExchServerSite

To get the Right value – Open Configuration partition – Sites – Browse the the site where the server is location – Properties – distinguishedName

image

Start the Exchange Transport Service.

Re run the setup. It worked fine.

 

 

Seeing the Exchange Setup logs :

[08/01/2015 12:20:01.0441] [2] Will wait ‘25000’ milliseconds for the service ‘MSExchangeTransport’ to reach status ‘Running’.

[08/01/2015 12:20:26.0674] [2] Service ‘MSExchangeTransport’ failed to reach status ‘Running’ on this server after waiting for ‘25000’ milliseconds.

[08/01/2015 12:20:26.0674] [2] Service Control Manager reports no process ID for service MSExchangeTransport.

[08/01/2015 12:20:26.0689] [2] Unable to get the process ID for service MSExchangeTransport because another similar process 0 was found

[08/01/2015 12:20:26.0689] [2] [ERROR] Service ‘MSExchangeTransport’ failed to reach status ‘Running’ on this server.

[08/01/2015 12:20:26.0705] [2] [ERROR] Service ‘MSExchangeTransport’ failed to reach status ‘Running’ on this server.

[08/01/2015 12:20:26.0705] [2] Ending processing start-SetupService

[08/01/2015 12:20:26.0705] [1] The following 1 error(s) occurred during task execution:

[08/01/2015 12:20:26.0705] [1] 0.  ErrorRecord: Service ‘MSExchangeTransport’ failed to reach status ‘Running’ on this server.

[08/01/2015 12:20:26.0705] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: Service ‘MSExchangeTransport’ failed to reach status ‘Running’ on this server.

at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)

at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)

at Microsoft.Exchange.Management.Tasks.ManageSetupService.WaitForServiceStatus(ServiceController serviceController, ServiceControllerStatus status, Unlimited`1 maximumWaitTime, Boolean ignoreFailures, Boolean sendWatsonReportForHungService)

at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(ServiceController serviceController, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)

at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(String serviceName, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)

at Microsoft.Exchange.Management.Tasks.StartSetupService.InternalProcessRecord()

at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()

[08/01/2015 12:20:26.0705] [1] [ERROR] The following error was generated when “$error.Clear();

if ($RoleStartTransportService)

{

start-SetupService -ServiceName MSExchangeTransport -MaxWaitTimeForRunningState 0:0:40

}

” was run: “Service ‘MSExchangeTransport’ failed to reach status ‘Running’ on this server.”.

[08/01/2015 12:20:26.0705] [1] [ERROR] Service ‘MSExchangeTransport’ failed to reach status ‘Running’ on this server.

[08/01/2015 12:20:26.0705] [1] [ERROR-REFERENCE] Id=BridgeheadServiceControl___fe1e918090cf487999f06438464a7f11 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup

[08/01/2015 12:20:26.0705] [1] Setup is stopping now because of one or more critical errors.

[08/01/2015 12:20:26.0705] [1] Finished executing component tasks.

[08/01/2015 12:20:26.0720] [1] Ending processing Install-BridgeheadRole

[08/01/2015 12:24:06.0818] [0] CurrentResult setupbase.maincore:396: 0

[08/01/2015 12:24:06.0833] [0] End of Setup

[08/01/2015 12:24:06.0833] [0] **********************************************

Satheshwaran Manoharan
Satheshwaran Manoharanhttps://www.azure365pro.com
Award-winning Technology Leader with a wealth of experience running large teams and diversified industry exposure in cloud computing. From shipping lines to rolling stocks.In-depth expertise in driving cloud adoption strategies and modernizing systems to cloud native. Specialized in Microsoft Cloud, DevOps, and Microsoft 365 Stack and conducted numerous successful projects worldwide. Also, Acting as a Technical Advisor for various start-ups.

Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

× How can I help you?