Exchange error on SCOM OutlookMapiHttp.Protocol RRS feed

  • Question

  • Hi All,

    any one can help ? we got the below errors on SCOM related to exchange server

    • OutlookMapiHttp.Protocol health set unhealthy (OutlookMapiHttpDeepTestMonitor) - OutlookMapiHttpDeepTestMonitor is failing on EXCH-MB02
    • Error: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
    • The Ehlo options for the client proxy target did not match while setting up proxy for user on inbound session 08D31576680E544F

    Sunday, January 31, 2016 10:36 PM


  • Hi,

    According to the error message, please run blew command to double check the health set on EXCH-MB02:

    Get-ServerHealth -Identity "EXCH-MB02" -HealthSet "Outlook.Protocol" | FT Server,State,Name,AlertValue –Autosize

    Please run Get-ServerComponentstate -Identity “servername” to check the state of server component, if the state is Inactive, please run below command to active relevant component:

    Set-ServerComponentState <Identity> -Component “component name” -Requester HealthAPI -State Active

    For second question, it can be ignored if there's no any transport issues in the productive environment.

    For third question, it might be caused by mismatched configuration on the max receive size and transport size for receive connector. Please run below command to check:
    Get-TransportConfig | FT MaxSendSize, MaxReceiveSize
    Get-ReceiveConnector | FT Name, MaxMessageSize

    If it mismatch, please run below command to modify the value of limitation:
    Set-TransportConfig -MaxSendSize 25MB -MaxReceiveSize 25MB
    Get-SendConnector | Set-SendConnector -MaxMessageSize 25MB

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Allen Wang
    TechNet Community Support

    • Marked as answer by Allen_WangJF Wednesday, February 24, 2016 1:18 AM
    Monday, February 1, 2016 3:00 AM