ManagedAvailability problem with Mailbox Transport Submission after CU6

We are getting the following error after CU6 implementation:

Seems like a latency issue... But, all tests are succesful, we are not experience any harm/issue. So, can we consider it as "by design" or should we take action?


Mailbox Transport Submission - the verification that the probe messages were successfully submitted within 5 minutes to HUB has failed.

This could indicate that the mailbox submissions are taking too long or not progressing at all.

SequenceNumber: 635484312145508431

Error: MapiSubmitLAMProbe finished with CheckPreviousMail failure.

FailureContext: MapiSubmitLAMProbe finished with CheckPreviousMail failure.

ExecutionContext: MapiSubmitLAMProbe started. This performs - 1. Submits a new message to Store 2. Checks results from previous Send Mail operation. Sequence # = 635484312145508431. First Run? = False. Previous mail submission to store was successful. Results - # of previous results: 0. Could Not Find stages that ran. Previous SendMail failure - Mail submitted to Store during the previous run never reached SendAsCheck.

This may indicate a latency from Store to Submission Service. Investigating. Found lower SA latency. Indicates an issue in Submission service.

  • Edited by leflo22 Thursday, October 09, 2014 7:43 AM
October 9th, 2014 7:42am

Using the message tracking logs, i found that my single exchange server tries to be high available and therefore wants to copy the mail to be transported to a different server before it transports it.As it can not find a suitable server to backup to, *THIS BACKUP ONLY STEP* failes. The transport will be done nevertheless, without problems.


Get-MessageTrackingLog -Server MyServer -messageid 1428709894973.44787@MyServer.noip.me | ft Timestamp, EventID

Timestamp                                                                                 EventId
---------                                                                                 -------
11.04.2015 01:51:36      DELIVER
11.04.2015 01:51:36      RECEIVE
11.04.2015 01:51:36      SUBMIT
11.04.2015 01:51:36 -->  HAREDIRECTFAIL <--
11.04.2015 01:51:36      RECEIVE
11.04.2015 01:51:36      AGENTINFO
11.04.2015 01:51:36      SEND

  • Edited by s_run 17 hours 25 minutes ago Added Example
Free Windows Admin Tool Kit Click here and download it now
April 24th, 2015 9:41am

Using the message tracking logs, i found that my single exchange server tries to be high available and therefore wants to copy the mail to be transported to a different server before it transports it.As it can not find a suitable server to backup to, *THIS BACKUP ONLY STEP* failes. The transport will be done nevertheless, without problems.


Get-MessageTrackingLog -Server MyServer -messageid 1428709894973.44787@MyServer.noip.me | ft Timestamp, EventID

Timestamp                                                                                 EventId
---------                                                                                 -------
11.04.2015 01:51:36      DELIVER
11.04.2015 01:51:36      RECEIVE
11.04.2015 01:51:36      SUBMIT
11.04.2015 01:51:36 -->  HAREDIRECTFAIL <--
11.04.2015 01:51:36      RECEIVE
11.04.2015 01:51:36      AGENTINFO
11.04.2015 01:51:36      SEND

  • Edited by s_run Friday, April 24, 2015 2:01 PM Added Example
April 24th, 2015 1:39pm

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

Other recent topics Other recent topics