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

Hi,

Based on my search, this event can be ignored and is a cosmetic issue in Exchange 2013, if we are not seeing any transport issues in the productive environment.

Best regards,

Free Windows Admin Tool Kit Click here and download it now
October 10th, 2014 4:54am

Belinda,

any publicly accessible reference about that ?

Have that in my CU8 Lab as well and feel they might have fixed it meanwhile...

March 28th, 2015 1:03am

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

Other recent topics Other recent topics