RE: got this message

Hi Bob,

Thanks for your pasting here!

Based on my experience and research, the problem occurs because of a memory
leak in the Exchange Server. Error 0x8007000e means E_OUTOFMEMORY, which
happens when Exchange Server runs out of available address space. The issue
may happen due to various causes. Debugging by Memory Dump is an efficient
method for this kind of issue. But, for newsgroup support, debugging is out
of our service boundary, so a suggestion would be to contact Microsoft
Customer Support Services (CSS) via telephone so that a dedicated Support
Professional can assist with your request.

To obtain the phone numbers for specific technology request please take a
look at the web site listed below.

http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

If you are outside the US please see: http://support.microsoft.com for
regional support phone numbers.

Personally, I would like to provide the following most possible causes for
Memory Leak and corresponding solutions.

1. The issue may happen when BlackBerry Enterprise Server is installed on
Exchange Server? More info here:

http://www.blackberry.com/knowledgecenterpublic/llisapi.dll/fetch/2000/8021/
8149/8064/Support_-_MAPI_E_NOT_ENOUGH_MEMORY.html?nodeid=25917&vernum=0

2. Memory leak caused by the Lsass.exe process:

1). 821008 Windows Server 2003-Based Computer Becomes Slow and Unresponsive
After - http://support.microsoft.com/?id=821008
2). 829993 Memory Leak Occurs in the Lsass.exe Process on a Windows Server
- http://support.microsoft.com/?id=829993

3. Other memory leak issues is most likely related to VSS (while be used
with some 3rd party backup program, such as Veritas, Ultrabac.) If it is
the case, you can reinstall Windows Server 2003 SP1.

4. The memory leak may also occur after you change the routing group. More
info here:

883309 You cannot send messages after you change the routing group
http://support.microsoft.com/?id=883309

Although the article applies to Exchange 2000, you can also reinstall
Exchange Server 2003 SP1 to fix the issue.

If the issue persists, please contact CSS to capture and debug Memory Dump
so that a dedicated engineer will help you solve the issue in more
efficient way. I highly appreciate your understanding and cooperation
regarding this.

Thanks and have a nice day!

Lee Li
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

.

Relevant Pages

  • Re: Memory Leak
    ... Regarding .Net memory leak issue, an important step is determing if it is ... should not use the "Mem Usage" column in task manager which is misleading. ... Microsoft Online Community Support ...
    (microsoft.public.dotnet.languages.csharp)
  • RE: Memory increasing even when in debug-break
    ... there are 2 types of memory leak in .Net: ... More interesting is the debugger breaks while memory still increasing ... Microsoft Online Community Support ...
    (microsoft.public.vsnet.debugging)
  • RE: Memory Leak
    ... managed leak or unmanaged memory leak. ... should not use the "Mem Usage" column in task manager which is misleading. ... Microsoft Online Community Support ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: 2 Critical Alerts since I added more RAM
    ... the memory alert issue is ... Issues that are fixed in Exchange Server 2003 Service Pack 2 ... This newsgroup only focuses on SBS technical issues. ... the allocating more memory than usual alert issue ...
    (microsoft.public.windows.server.sbs)
  • [NT] Services for UNIX 2.0 Suffer from a Remotely Triggered Memory Leak
    ... Services for UNIX 2.0 Suffer from a Remotely Triggered Memory Leak ... 2000 are not affected by the vulnerability. ... * A vulnerability that could enable an attacker to cause the NFS service ...
    (Securiteam)
Loading