Incase of an unusually low value, verify the status of the interchange in the suspended queue using the BizTalk server administration. If the status corresponding to an interchange is Encoding, then it implies that the BizTalk server could not encode the interchange. This problem may be solved by resubmitting the interchange to the BizTalk server.

Incase of an unusually low value, verify the status of the interchange in the suspended queue using the BizTalk  server administration. If the status corresponding to the interchange is Encrypting then it signifies that the BizTalk server could not encrypt this interchange. Also, verify the expiration of the certificate in the Certificate Microsoft Management Console snap-in.

Incase of an unusually low value, verify the status of the interchange in the suspended queue. If the status corresponding to the interchange is Serializing then it implies that the BizTalk server could not convert the interchange to its native format.

Resubmitting the interchange can solve this problem.

A value of –1 for this measure implies that the BizTalk Messaging Service or Distributed Transaction Coordinator (MSDTC) or XLANG Schedule Restart Service may not be running.

If the value of this measure is unusually low, verify the transport address in the channel. Correct the problem in the channel and resubmit the interchange.

Alternatively, the BizTalk server might have taken a long time to transmit the interchange. Verify the transport mechanism used.

Another reason could be that the BizTalk administrator might have moved the interchange to the suspended queue, resubmitted the interchange from the suspended queue.

Alternatively, the computer on which the BizTalk server could be running out of memory, restart the server and resubmit all the interchanges in the suspended queue.