The Microsoft Exchange Mailbox Transport Submission service terminated unexpectedly
Hi, I get following error on my new Exchange 2013 server: It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. Mailbox database is mounted and contains mailboxes (also system mailbox), ipv6 is enabled on the exchange server. Is there any logging I can find to see what's going on actually? The transport service won't start either.
April 29th, 2013 10:51am

Hello, Could you please check the application log and let us know the related event ID and its details? Thanks, If you have feedback for TechNet Subscriber Support, contact tnsfl@microsoft.comSimon Wu TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
April 29th, 2013 11:25pm

Hi Simon, thanks for your reply. For the Mailbox Transport submission service I get: event id 1000: Faulting application name: MSExchangeSubmission.exe, version: 15.0.620.20, time stamp: 0x512192de Faulting module name: Microsoft.Exchange.Net.ni.dll, version: 15.0.620.18, time stamp: 0x511c5c25event id: 7031: The Microsoft Exchange Mailbox Transport Submission service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. For the transport service I get: event id 1000: Faulting application name: edgetransport.exe, version: 15.0.620.20, time stamp: 0x51219273 Faulting module name: Microsoft.Exchange.Net.ni.dll, version: 15.0.620.18, time stamp: 0x511c5c25 event id 1016: The worker process crashes continuously on startup: C:\Program Files\Microsoft\Exchange Server\V15\Bin\edgetransport.exe. The service will be stopped.
April 30th, 2013 2:34am

nobody has a clue on how to troubleshoot this?
Free Windows Admin Tool Kit Click here and download it now
May 3rd, 2013 3:24am

I have the same Problem. Have you solved it?
May 7th, 2013 8:07am

Yes I noticed in some event log about starting submissions that dns took more than 50 seconds so assumed it was a dns problem. After fixing it I had several other DNS issues with the other services and mail flow, here is what I did to resolve it: In Server options, set the internal & external DNS lookup to internal and external DNS server addresses. On the receive connectors for the Exchange 2013 server, scope to only the address of the Exchange 2013 server. On the Send connectors for the internet, mark the option to use the external DNS lookup addresses. Reboot the server.
Free Windows Admin Tool Kit Click here and download it now
May 7th, 2013 8:29am

In Server options, set the internal & external DNS lookup to internal and external DNS server addresses. Thanks! That was it. It's a bug! I had set the DNS Servers at NIC configuration. So I let the Exchange server use the adapter settings... this did not work! Now I have set it to "Custom" in the server object and with the same DNS Servers like in the NIC configuration, it works =) .
May 7th, 2013 3:25pm

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

Other recent topics Other recent topics