| Event Id | 986 |
| Source | MSExchangeTransport |
| Description | GetMessageType returned hr=0x8007000e, MsgType=0xffffffff. Size=0x9c06 (Class=0x0), Prio=0x1, Flags=0x2, TypeOfMsg=0x2000 OrigDN=<> cRRHosts=0, ChkSum=0x0 6RRHs=<>,<>,<>,<>,<>,<> |
| Event Information | According to Microsoft: CAUSE: This problem occurs because of a memory leak in the Exchange routing engine. When messages go through the Routing Group connector after you change a routing group configuration, a new object is created. The Exchange routing engine performs an additional reference call on this object. When this behavior occurs, the Exchange routing engine cannot release memory. RESOLUTION: A supported hotfix is now available from Microsoft, but it is only intended to correct the problem.Only apply it to systems that are experiencing this specific problem. |
| Reference Links | Event ID 986 from Source MSExchangeTransport |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.