Hello guys,

we have been facing some issues for 3 days with Microsoft Exchange 2013 CU3,

As we have noticed after troubleshooting that Mail submission service is crashing (event 9036)

Service Microsoft Exchange Mailbox Transport Submission.  29 starts were made since the last clean stop. Startup will be delayed until 1/17/2014 11:26:35 AM.

For example at 11:26 email flow works normally for few minutes, then i get another event id 9036 with + 2 hours (so i should wait 2 more hours before mailflow works again)

What i mean by Mailflow is Outbound email (Inbound works normally) even if i send email to myself, i don't get it unless i reach this 2 hours time.

I am also having event ID (6535)

The description for Event ID 65535 from source Application cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

<TraceRecord xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord" Severity="Error"><TraceIdentifier>http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.ThrowingException.aspx</TraceIdentifier><Description>Throwing an exception.</Description><AppDomain>MSExchangeFrontendTransport.exe</AppDomain><Exception><ExceptionType>System.ServiceModel.CommunicationException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:01:00'.</Message><StackTrace>   at System.ServiceModel.Channels.StreamConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout)
   at System.ServiceModel.Channels.FramingDuplexSessionChannel.CloseOutputSessionCore(TimeSpan timeout)
   at System.ServiceModel.Channels.TransportDuplexSessionChannel.CloseOutputSession(TimeSpan timeout)
   at System.ServiceModel.Channels.TransportDuplexSessionChannel.OnClose(TimeSpan timeout)

and eventID 4999

Watson report about to be sent for process id: 17352, with parameters: E12, c-RTL-AMD64, 15.00.0775.038, MSExchangeSubmission, unknown, M.E.D.I.T.VirtualBuffer.Read, System.ArgumentOutOfRangeException, cf47, unknown.
ErrorReportingEnabled: True

Any help?

Thanks

Hi

Is there any AV on the server? Does it help to restart the server? Any pending updates on the box?

@DareDevil57,

No there is no antivirus on the server,

It doesnt help restarting the server (Even the MS Exchange Transport submission service appears as running in Services.msc)

No Pending updates, all updates are installed

Windows server 2012 , Exchange 2013 CU3

Hi

How much procent from RAM is used?

Around 40% , we have 24 GB of memory, and usually it is around 40% of usage.

Thanks

@SSorin, i didn't understand very well, can you please explain ?

I have the 5 default receive connectors, which one should i change?

Do not change the Default Receive Connectors.

My question was if you created a new Receive Connector

@jpc0706,

We opened a case with PSS (it was escalated to the whole world, starting from US to UK to Egypt)

and it wasn't resolved,

In order to move on, we created another exchange server, and we migrated mailboxes to it, mailfow was fine, and we kept the old server running (with no mailboxes on it)

Few weeks later, we tried creating a test mailbox on the old server, and mailflow was fine again,

How did it work ? no one knows, even Microsoft :)

So i advise you to install a new exchange server in your organization and move mailboxes to it

Create New Exchange Server, 

Same license different name, migrate mailboxes to it, Fix OWA, EWS, OAB... Virtual directories.

The Cause is that Frontend Mail Submission is Crashing, and will retry starting every 2 hours.

i Hope u did find my Suggested  Solution helpful my Friend @sysadmin89

You are having mail submission issues. Kindly verify Mail submission service is running and if there are any logs related to mail submission service then kindly let me know. Meanwhile kindly messaging tracking from EAC and check the flow of messages for troubleshooting.  Thanks.

Kindly mark this as answer if it helps you to achieve the goal.

We had the same issue. Our Edgetransport crashed every 3 minutes. Turns out we had a linux server try to relay e-mails every 3 minutes via Exchange to itself, but via wrong hostname. Nullmailer on Ubuntu Server with Eprints.

Once the nullmailer was disabled and stopped sending the "killer e-mails" the Exchange service stopped crashing. We found the "killer e-mails" by enabling SMTP logging on the send connector and our relay recieve connector.

We are on Exchange 2010 SP3, Rollup 10.

• Edited by Christian_Wimmer 17 hours 51 minutes ago

We had the same issue. Our Edgetransport crashed every 3 minutes. Turns out we had a linux server try to relay e-mails every 3 minutes via Exchange to itself, but via wrong hostname. Nullmailer on Ubuntu Server with Eprints.

Once the nullmailer was disabled and stopped sending the "killer e-mails" the Exchange service stopped crashing. We found the "killer e-mails" by enabling SMTP logging on the send connector and our relay recieve connector.

We are on Exchange 2010 SP3, Rollup 10.

• Edited by Christian_Wimmer Thursday, August 27, 2015 1:36 PM