Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

XADM: Leak In Repeated Calls to MAPILogonEx


View products that this article applies to.

Symptoms

Applications that repetitively log on to MAPI or Collaboration Data Objects (CDO) to process very large message volumes can exhibit problems after they run normally for long periods of time. The following problems might be seen:
  • Corrupt message properties
  • System resource depeletion
  • Unexpected termination

↑ Back to the top


Cause

A memory heap that is created at the start of a MAPI session is not destroyed when the session is released.

↑ Back to the top


Resolution

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Exchange Server 5.5 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Component:

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version      Size    File name
   --------------------------------------------------
 08/08/01  4:22:39PM 5.0.1462.14 1,210,640  wmsui32.dll
				
NOTE: Because of file dependencies, this fix requires Microsoft Exchange Server version 5.5 Service Pack 4.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5.

↑ Back to the top


More information

Steps to Reproduce Behavior

To reproduce the behavior, place the MAPILogonEx function in a loop construct and run the program so that the loop runs at least 6000 times. To do this, you can use the following code:
while (1)
   {
     LPMAPISESSION  lpSession = NULL;
     HRESULT hr;
     int iLoopCount;
     hr = MAPILogonEx(
            0,
            szLogonProfile, 
            NULL, 
            MAPI_NEW_SESSION | MAPI_LOGON_UI | 
            MAPI_NO_MAIL | MAPI_USE_DEFAULT, 
            &lpSession);
     if (hr !=  S_OK)
     {
       printf ("ERROR at MAPILogonEx: %x\n",hr);
       break;
     };

     iLoopCount++;
     printf("LOGON %d\n",iLoopCount);

     hr = lpSession->Logoff (NULL,NULL,0);
     if (hr != S_OK)
     {
       printf ("ERROR at Logoff: %x\n",hr);
       break;
     };

     if (lpSession) lpSession->Release();  
   }
				

↑ Back to the top


Article Info
Article ID : 293150
Revision : 4
Created on : 1/1/0001
Published on : 1/1/0001
Exists online : False
Views : 324