locked
Microsoft Exchange Transport service terminated unexpectedly RRS feed

  • Question

  • Hello,

    We had an issue on Exchange Server 2013.

    Apparently, the Microsoft Exchange Transport service terminated and restarted by itself, causing a disservice.
    This is what appeared in Event Viewer:

    13:31:53 "The Microsoft Exchange Transport service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service."

    13:31:58 "The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Microsoft Exchange Transport service, but this action failed with the following error:
    An instance of the service is already running."

    13:32:00 The Microsoft Exchange Transport service entered the running state.

    Can you help us to understand why happened this?

    Thanks

    Thursday, July 14, 2016 1:45 PM

Answers

  • Hi,

    If this issue occur once may this is a temporary problem;

    If this service continue to crush, this may due to some of the corrupt message in the queue. If like that try as following:

    • Pause the transport service and let all the messaged go out.
    • when queue is empty, stop the transport service and go to the mail.que database in transport-->queue folder. And cut paste all the files from queue folder to some other folder as backup.
    • Now start the transport service, it will create a fresh mail.que database and observe if the service us crashing again.

    We can also check whether any transport agent is causing the crash.

    Get-TransportAgent | Disable-TransportAgent

    PS: Disabling transport agents may stop some functions of your transport component. Something like transport rules, etc

    And please check the Exchange Application log to see if any other useful information related to this crush. This will be very helpful.

    It’s also to recommended to increase the diagnostic logging on the transport services with the following command:

    Set-EventLogLevel -Identity MSExchangeTransport\TransportService -Level 5

    Best regards,


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    • Edited by Jason.Chao Friday, July 15, 2016 10:32 AM
    • Proposed as answer by Niko.Cheng Monday, July 25, 2016 1:15 AM
    • Marked as answer by Niko.Cheng Wednesday, August 3, 2016 1:44 AM
    Friday, July 15, 2016 10:32 AM
  • Hi,

    Given current situation, it's recommended to update to the latest version Exchange server 2013 CU 13 .

    The latest version could fix many problems.

    Best regards,


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    • Edited by Jason.Chao Wednesday, July 20, 2016 2:06 AM
    • Proposed as answer by Jason.Chao Saturday, July 23, 2016 3:07 PM
    • Marked as answer by Niko.Cheng Wednesday, August 3, 2016 1:45 AM
    Wednesday, July 20, 2016 2:05 AM

All replies

  • What cumulative update (CU) are you running?

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Thursday, July 14, 2016 5:46 PM
  • A service can crash for multiple reasons, sometimes it's accompanied by an event in the Application/System log at the time it happens - any other relevant events?  Also, was it just a one-time crash?  Or does it continue to crash?
    Thursday, July 14, 2016 8:48 PM
  • We are currently running Microsoft Exchange Server 2013 CU 6
    Friday, July 15, 2016 9:15 AM
  • Hi,

    If this issue occur once may this is a temporary problem;

    If this service continue to crush, this may due to some of the corrupt message in the queue. If like that try as following:

    • Pause the transport service and let all the messaged go out.
    • when queue is empty, stop the transport service and go to the mail.que database in transport-->queue folder. And cut paste all the files from queue folder to some other folder as backup.
    • Now start the transport service, it will create a fresh mail.que database and observe if the service us crashing again.

    We can also check whether any transport agent is causing the crash.

    Get-TransportAgent | Disable-TransportAgent

    PS: Disabling transport agents may stop some functions of your transport component. Something like transport rules, etc

    And please check the Exchange Application log to see if any other useful information related to this crush. This will be very helpful.

    It’s also to recommended to increase the diagnostic logging on the transport services with the following command:

    Set-EventLogLevel -Identity MSExchangeTransport\TransportService -Level 5

    Best regards,


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    • Edited by Jason.Chao Friday, July 15, 2016 10:32 AM
    • Proposed as answer by Niko.Cheng Monday, July 25, 2016 1:15 AM
    • Marked as answer by Niko.Cheng Wednesday, August 3, 2016 1:44 AM
    Friday, July 15, 2016 10:32 AM
  • You're real old.  Update to CU12.  Maybe it'll fix your issues.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Friday, July 15, 2016 6:49 PM
  • There are no other relevant events and It happens occasionally.
    Tuesday, July 19, 2016 1:17 PM
  • Hi,

    Given current situation, it's recommended to update to the latest version Exchange server 2013 CU 13 .

    The latest version could fix many problems.

    Best regards,


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    • Edited by Jason.Chao Wednesday, July 20, 2016 2:06 AM
    • Proposed as answer by Jason.Chao Saturday, July 23, 2016 3:07 PM
    • Marked as answer by Niko.Cheng Wednesday, August 3, 2016 1:45 AM
    Wednesday, July 20, 2016 2:05 AM
  • Hi,

    I haven't heard back from you yet and I'm just writing to see if you have had an opportunity to feedback to us.

    Best regards, 


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    • Edited by Jason.Chao Friday, July 22, 2016 1:48 AM
    Friday, July 22, 2016 1:48 AM
  • Hi,

    Lots of people seem to be batteling this one, but for me the following registry fix worked:

    Give "Network Service" full access to this one.

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\WorkerTaskFramework\IdStore

    Br.

    Peter

    Wednesday, February 6, 2019 5:20 PM