MSExchangeTransport service failed to start services

Hi,

Exchange 2013 mailbox server transport service failed to start and posting error event id 17007

Any help?

February 11th, 2015 2:42am

After rename mail.que transport service able to start successfully.

But, what causing mail.que suddenly became bigger in size? how to avoid this issue

Free Windows Admin Tool Kit Click here and download it now
February 11th, 2015 8:07am

Hi,

This Error event indicates there is a version mismatch between an Extensible Storage Engine (ESE) database and its corresponding transaction logs on the Hub Transport server or Edge Transport server. When you rename the mail.que file, the transaction logs will be recreated automatically during the startup of the Microsoft Exchange Transport service. So thats why transport service was able to start successfully.

Whats more, the mail.que file temporarily stores all emails before it is delivered to the target. It is an ESE database which means it is similar in architecture like an Exchange mailbox database, the edb file.

Queue database:

https://technet.microsoft.com/en-us/library/bb125177(v=exchg.150).aspx

Here is the suggested way to get rid of the old mail.que file and get a new one without any downtime.

  1. Go to mailbox server.
  2. Locate to the location of mail.que file. (By default, the path is: C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\queue)
  3. Open exchange management shell and run Get-TransportServer | fl PipelineTracingEnabled, the value should be False. If not, run Set-TransportServer -PipelineTracingEnabled $False
  4. Now run Get-TransportConfig | Fl Max* and ensure that MaxDumpsterSizePerDatabase is in MBs and not GBs and MaxDumpsterTime : 7.00:00:00. If not run Set-TransportConfig -MaxDumpsterSizePerStorageGroup <size> -MaxDumpsterTime <timespan>
  5. Now run Get-Queue and take a look at the count of messages.
  6. Goto services.msc and Pause the Microsoft Exchange Transport service.
  7. Again, run Get-Queue and ensure all pending messages are zeroed out.
  8. Once messages pending becomes zero, stop the Transport service.
  9. Move the mail.que file and all others to a new folder in the same location.
  10. Start the Transport service.
  11. Take a look at the queue again.
  12. You should see that messages would have started getting delivered.
  13. Now you can backup or safely delete the old mail.que file.

Best Regards.

February 11th, 2015 9:22pm

Hi,

This Error event indicates there is a version mismatch between an Extensible Storage Engine (ESE) database and its corresponding transaction logs on the Hub Transport server or Edge Transport server. When you rename the mail.que file, the transaction logs will be recreated automatically during the startup of the Microsoft Exchange Transport service. So thats why transport service was able to start successfully.

Whats more, the mail.que file temporarily stores all emails before it is delivered to the target. It is an ESE database which means it is similar in architecture like an Exchange mailbox database, the edb file.

Queue database:

https://technet.microsoft.com/en-us/library/bb125177(v=exchg.150).aspx

Here is the suggested way to get rid of the old mail.que file and get a new one without any downtime.

  1. Go to mailbox server.
  2. Locate to the location of mail.que file. (By default, the path is: C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\queue)
  3. Open exchange management shell and run Get-TransportServer | fl PipelineTracingEnabled, the value should be False. If not, run Set-TransportServer -PipelineTracingEnabled $False
  4. Now run Get-TransportConfig | Fl Max* and ensure that MaxDumpsterSizePerDatabase is in MBs and not GBs and MaxDumpsterTime : 7.00:00:00. If not run Set-TransportConfig -MaxDumpsterSizePerStorageGroup <size> -MaxDumpsterTime <timespan>
  5. Now run Get-Queue and take a look at the count of messages.
  6. Goto services.msc and Pause the Microsoft Exchange Transport service.
  7. Again, run Get-Queue and ensure all pending messages are zeroed out.
  8. Once messages pending becomes zero, stop the Transport service.
  9. Move the mail.que file and all others to a new folder in the same location.
  10. Start the Transport service.
  11. Take a look at the queue again.
  12. You should see that messages would have started getting delivered.
  13. Now you can backup or safely delete the old mail.que file.

Best Regards.

  • Marked as answer by md_raffiq81 9 hours 36 minutes ago
Free Windows Admin Tool Kit Click here and download it now
February 12th, 2015 5:21am

Hi Lynn-Li,

Thanks for your answer.

Cheers

February 12th, 2015 9:17pm

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

Other recent topics Other recent topics