Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 2050 Source: MSExchangeDSAccess
Process <process name> (PID=Process_ID). The shared memory heap could not be created.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Microsoft Exchange Directory service?
What is a heap?
This issue occurs when the Davex.dll and Exprox.dll files are not running in the Inetinfo.exe process. See ME926085 for information on fixing this problem.
This issue may occur if the ExchangeApplicationPool application pool is deleted from the application pools in Internet Information Services (IIS). See ME906907 to solve this problem.
As per Microsoft: "This event indicates that DSAccess service startup will fail because it failed to create the shared memory heap. This may be caused by internal Epoxy failures, running out of memory generally, or too many processes running DSAccess. Epoxy has a limit of 10 processes per heap". See MSEX2K3DB for additional information about this event.
This issue may occur when the Exchange virtual directory is either not running in the correct application pool, or when the ExchangeApplicationPool property has the incorrect identity. See ME829167 and ME841546 to fix this problem.
|Private comment: Subscribers only. See example of private comment|
|Links: ME829167, ME841546, ME906907, ME926085, MSEX2K3DB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated