Problem : Microsoft Exchange Transport Service will not start – error 1053 timeout in a timely fashion
Following some DNS problems, users cannot recieve or send mail using Exchange 2007.
DNS issues have been resolved and dcdiag & netdiag run happily on all DCs.
We have 6 DC controllers one of which is Exchsrv, which is the server with issues.
After several restarts,
Exchange 2007 will only start the following services by itself:
– Microsoft Exchange Active Directory Topology Service
– Microsoft Exchange Infomation Store
– Microsoft Exchange System Attendant
– Microsoft Search (Exchange)
These service startup on boot.
I cannot get the Microsoft Exchange Transport service to start at all.
When I run it manually it fails after 30secs with an error 1053 did not start in a timely fashion.
It is running under the Local System,
but I have tried network service and domain administrator to no avail.
The Event viewer doesn’t have any error messages that are relevant.
HELP!!!
I’ve got of teaching staff who need their e-mail and my phone is red hot!!
Thanks..
———————–
I get the odd Event viewer message from the Topology category, but nothing from the transport service:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=5288). 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:
hades.school.local CDG 1 7 7 1 0 1 1 7 1
traphost.school.local CDG 1 7 7 1 0 1 1 7 1
elyweb.school.local CDG 1 7 7 1 0 1 1 7 1
dataserver.school.local CDG 1 7 7 1 0 1 1
7 1
printsrv.school.local CD- 1 6 6 0 0 1 1 6 1
exchsrv.school.local CDG 1 7 7 1 0 1 1 7 1
Out-of-site:
For more information, see Help and Support Center at //go.microsoft.com/fwlink/events.asp.
Solution : Microsoft Exchange Transport Service will not start – error 1053 timeout in a timely fashion
The problem was that Exch Rollup 3 took too long to start before it timed out.
We uninstalled rollup 2 and 3, then uninstalled the hub transport agent. Rebooted server.
The HT agent was then reinstalled and then rebooted server.
The rollup3 was then installed and the timeout was amended in the registry. Server rebooted and all came up fine.
Front-end Microsoft Exchange Transport service stops and doesn't start in Exchange Describes an issue that occurs when an Exchange server has both back-end and front-end roles. simonxjx v-six dcscontentpm ITPro troubleshooting Normal
Exchange Server CSSTroubleshoot
Exchange Server 2013 Enterprise Exchange Server 2016 Enterprise Edition MET150 3/31/2022 Original KB number: 2958036 Consider the following scenario: In this scenario, the service stops and doesn't restart. Additionally, the following events are logged in the Application log: Log Name: Application
Source: MSExchangeTransport
Event ID: 1019
Task Category: SmtpReceive
Level: Error
Computer: 2013 Server
Description: Failed to start listening (Error: 10048). Binding: 0.0.0.0:25.
Log Name: Application
Source: MSExchangeTransport
Event ID: 1018
Task Category: SmtpReceive
Level: Error
Computer: 2013 Server
Description: The address is already in use. Binding: 0.0.0.0:25.
Log Name: Application
Source: MSExchangeTransport
Event ID: 1036
Task Category: SmtpReceive
Level: Error
Computer: 2013 Server
Description: Inbound direct trust authentication failed for certificate %1. The source IP address of the server that tried to authenticate to Microsoft Exchange is [%2]. Make sure EdgeSync is running properly.
Log Name: Application
Source: MSExchange Common
Event ID: 4999
Task Category: General
Level: Error
Computer: 2013 Server
Description: Watson report about to be sent for process id: 19848, with parameters: E12IIS, c-RTL-AMD64, 15.00.0847.032, MSExchangeTransport, M.Exchange.Net, M.E.P.WorkerProcessManager.HandleWorkerExited, M.E.ProcessManager.WorkerProcessRequestedAbnormalTerminationException, 5e2b, 15.00.0847.030. ErrorReportingEnabled: False
Log Name: Application
Source: MSExchange TransportService
Event ID: 1046
Task Category: ProcessManager
Level: Warning
Computer: 2013 Server
Description: Worker process with process ID 18420 requested the service to terminate with an unhandled exception. [!NOTE] If you stop the Microsoft Exchange Transport service, you can start the front-end Microsoft Exchange Transport service. Then, when you try to start the Microsoft Exchange Transport service, that service doesn't start, and the
events that are mentioned earlier in this section are logged. This issue occurs if there's a receive connector having a Transport type of HubTransport that has the binding set to port 25 on the affected Exchange server. Only the FrontendTransport server-type receive connector should have the binding set to port 25. Run the following command to change the connector
type from HubTransport to FrontendTransport: Set-ReceiveConnector -Identity "Receive connector name" -TransportRole FrontendTransport Delete and re-create the receive connector, and then set its role to FrontendTransport.titledescriptionauthorms.authormanageraudiencems.topiclocalization_priorityms.customms.reviewerappliestosearch.appveridms.date
The front-end Microsoft Exchange Transport service stops and doesn't restart in Exchange Server 2013 SP1 or Exchange Server 2016
Symptoms
Cause
Resolution
Method 1
Method 2