This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 28.000000000000004%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EN%3C/text%3E%3C/svg%3E)
We have an on-premise Exchange 2016 server. I've noticed that we are getting the following event log entry MSExchange Common 4999 (randomly, not for all outbound emails)
Watson report about to be sent for process id: 26956, with parameters: E12IIS, c-RTL-AMD64, 15.01.1779.008, edgetransport, AsEx, A.E.SpamChecker.Dispose, System.NullReferenceException, bf8d-dumptidset, unknown. ErrorReportingEnabled: True
and then a few log entries later we get
The following messages were loaded at startup before Transport crashed. To avoid further crashes, it is recommended that a New-InterceptorRule is deployed matching the values for the message that caused Transport to crash.
As result, it seems that the email in question is then being sent multiple times. For example
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(41.6, 80%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAL%3C/text%3E%3C/svg%3E)
Hi,
Just checking in to see how things are going on with this thread.
Does this issue have any updates? If it has been resolved, please click "Accept as answer" to mark useful post or share your solution, your action would benefit others who have similar issues.
If you have any questions or need further assistance, please feel free to post back. Thanks!
Im guessing you have 3rd party anti-virus or some other installed add-in?
I would disable:
http://clintboessen.blogspot.com/2018/04/third-party-transport-agents-delaying.html
If you have 3rd party anti-virus, ensure its excluding the Exchange Dirs and processes:
Also ensure you are running the latest 2016 CU plus May 2022 SU:
You can check with the healthchecker
https://aka.ms/ExchangeHealthChecker
I'm thinking it could be avast we have installed for Exchange. We are already excluding the exchange dirs and processes as per https://learn.microsoft.com/en-us/exchange/antispam-and-antimalware/windows-antivirus-software?view=exchserver-2019
I'm thinking initially to disable the "Scan at transport level"
I would disable and stop any service associated yes. If it continues, consider opening a case with them.