| Event Id | 2050 |
| Source | MSExchange ADAccess |
| Description | Process %1 (PID=%2). The shared memory heap could not be created. This may be caused if physical memory limits have been exceeded. It may also be caused if too many other processes are running DSAccess. You may be able to resolve this error by restarting the Exchange server that logged this event. |
| Event Information | According to Microsoft : Cause : This Error event indicates that the Microsoft? Exchange Active Directory? Topology service (MSExchangeADTopologyService.exe) startup will fail because a shared memory heap cannot be created. This may be caused by the following: 1.Internal Epoxy (ExIPC) has failed. Epoxy is a shared memory mechanism that enables the Internet Information Services (Inetinfo.exe) and Microsoft Exchange Information Store service (Store.exe) processes to quickly shuttle data back and forth. This memory is also used by DSAccess, the Exchange component that caches Active Directory information. 2.Physical memory limits are exceeded. 3.Too many other processes are running DSAccess. Epoxy has a limit of 10 processes per heap. Resolution : To resolve this error, restart the computer. |
| Reference Links | Event ID 2050 from Source MSExchange ADAccess |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.