Exchange Transport Agent Causes Failure Event in Transport Logs RRS feed

  • Question

  • Hello,

    I have developed a custom transport agent.  I am receiving a FAIL event each time the agent runs.  The Recipient Status in the Message Tracking Log entry has the following text:

    : {[{LRT=};{LED=550 4.3.2 QUEUE.TransportAgent; message deleted by transport agent};{FQDN=};{IP=}]}

    The messages are delivered without issue and are processed by the agent correctly as well.  It is not clear to me why this error is occurring.  I have gone as far as disabling the code that actually alters the message by commenting it out an re-compiling the agent.

    Any ideas on what might be causing this kind of behavior.  Do I need to provide a return code from my agent that the logs would then read?

    The complete tracking log entry is below.


    RunspaceId              : c8761fd4-04a1-48d9-85bd-96d6beee2cd6
    Timestamp               : 7/15/2015 9:10:58 PM
    ClientIp                :
    ClientHostname          : exchangeserver-01
    ServerIp                :
    ServerHostname          :
    SourceContext           : My Custom Agent
    ConnectorId             :
    Source                  : AGENT
    EventId                 : FAIL
    InternalMessageId       : 11373073399823
    MessageId               : <>
    Recipients              : {}
    RecipientStatus         : {[{LRT=};{LED=550 4.3.2 QUEUE.TransportAgent; message deleted by transport
    TotalBytes              : 9638
    RecipientCount          : 1
    RelatedRecipientAddress :
    Reference               :
    MessageSubject          : test message 2
    Sender                  :
    ReturnPath              :
    Directionality          : Incoming
    TenantId                :
    OriginalClientIp        :
    MessageInfo             : 2015-07-16T01:10:58.411Z;;SRV=exchan
                    ;CAT|CATSM|CATSM-My Custom Agent
    MessageLatency          :
    MessageLatencyType      : None
    EventData               : {[E2ELatency, 0.333], [DeliveryPriority, Normal], [AccountForest,]}

    Thursday, July 16, 2015 1:58 AM

All replies

  • As a first step I would suggest you enable Pipeline tracing and then look through the logs that its generates it should tell you why this is happening.


    Thursday, July 16, 2015 4:44 AM
  • Hello,

    I actually expect the message to be deleted.  What I was after is a way to add useful information to the tracking logs for the action that the agent is taking rather than having the Tracking Logs Suggest that there is a problem.

    Ideally I would like to write useful information from the transport agent into the EventData property in the tracking log.


    Saturday, August 8, 2015 1:56 AM