Slow Performance Occurs When You Use a Program That Uses the Outlook Object Model with Exchange 2000 and Exchange 2003 (826755)


The information in this article applies to:

  • Microsoft Exchange 2000 Server
  • Microsoft Exchange Server 2003 Enterprise Edition
  • Microsoft Exchange Server 2003 Standard Edition

SYMPTOMS

When you use a program that was written to use the Microsoft Outlook object model, you notice that the Items.Find operation and the Items.FindNext operation on your Microsoft Exchange Server computer exhibit slow performance. You may also notice that the same program seems to perform faster on a Microsoft Exchange Server 5.5 computer than it does on a Microsoft Exchange 2000 Server computer or on a Microsoft Exchange Server 2003 computer.

CAUSE

This problem occurs because of the way that the Outlook object model uses MAPI bookmarks for the Items.Find operation and the Items.FindNext operation.

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, Microsoft recommends that you wait for the next Microsoft Exchange 2000 Server service pack or Microsoft Exchange Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS

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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. Component: Store

The English version of this hotfix 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.

Exchange 2000 Server

Date         Time   Version            Size    File name
--------------------------------------------------------------
14-Aug-2003  17:42  6.0.6498.0      3,915,776  Cdoex.dll        
14-Aug-2003  17:37  6.0.6498.0        851,968  Davex.dll        
14-Aug-2003  17:37  6.0.6498.0         53,248  Davexpc.dll      
14-Aug-2003  17:22  6.0.6498.0        131,072  Drviis.dll       
14-Aug-2003  17:22  6.0.6498.0        577,536  Dsaccess.dll     
14-Aug-2003  04:23  6.0.6498.0        184,320  Dscmsg.dll       
14-Aug-2003  04:23  6.0.6498.0        958,464  Emsmdb32.dll     
14-Aug-2003  17:42  6.0.6498.0      3,575,808  Excdo.dll        
14-Aug-2003  17:22  6.0.6498.0        258,048  Exmime.dll       
14-Aug-2003  17:37  6.0.6498.0        143,360  Exodbesh.dll     
14-Aug-2003  17:37  6.0.6498.0         57,344  Exodbpc.dll      
14-Aug-2003  17:37  6.0.6498.0        200,704  Exodbprx.dll     
14-Aug-2003  17:37  6.0.6498.0      2,174,976  Exoledb.dll      
14-Aug-2003  17:21  6.0.6498.0         81,920  Exosal.dll       
14-Aug-2003  17:37  6.0.6498.0        307,200  Exprox.dll       
14-Aug-2003  04:25  6.0.6498.0        143,360  Exschema.exe     
14-Aug-2003  17:37  6.0.6498.0        315,392  Exsmtp.dll       
14-Aug-2003  04:27  6.0.6498.0        675,840  Exwform.dll      
14-Aug-2003  04:02  6.0.6498.0         49,152  Mdbevent.dll     
14-Aug-2003  04:20  6.0.6498.0      2,285,568  Mdbmsg.dll       
14-Aug-2003  04:03  6.0.6498.0         32,768  Mdbrole.dll      
14-Aug-2003  17:23  6.0.6498.0         24,576  Mdbtask.dll      
14-Aug-2003  17:20  6.0.6498.0         94,208  Peexch50.dll     
14-Aug-2003  17:21  6.0.6498.0        397,312  Phatcat.dll      
14-Aug-2003  17:23  6.0.6498.0        528,384  Reapi.dll        
14-Aug-2003  17:37  6.0.6498.0        311,296  Resvc.dll        
14-Aug-2003  17:22  6.0.6498.0      4,657,152  Store.exe

Note Because of file dependencies, this hotfix requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

301378 How to Obtain the Latest Exchange 2000 Server Service Pack

Exchange Server 2003

Date         Time   Version            Size    File name
--------------------------------------------------------------
04-Sep-2003  18:01  6.5.6980.23        49,152  Mdbevent.dll     
04-Sep-2003  18:39  6.5.6980.23     3,186,176  Mdbmsg.dll       
04-Sep-2003  18:03  6.5.6980.23        24,064  Mdbrole.dll      
04-Sep-2003  20:24  6.5.6980.23        13,312  Mdbtask.dll      
04-Sep-2003  20:22  6.5.6980.23     5,038,080  Store.exe

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.

MORE INFORMATION

To obtain optimal performance when you use the Outlook object model and Exchange 2000 or later, Microsoft recommends that you follow these guidelines:
  • Install the server-side hotfix that is described in this article.
  • In the client-side code where the Outlook object model is used, call the Items.Sort operation before you make the first call to the Items.Find operation. When you perform an Items.Sort operation first, this makes sure that the server creates an index for the property that you search against. Because the index is created, you can expect subsequent calls for the Items.Sort method that use the same property name to be faster, although the improved performance requires you to create the index the first time that the Items.Sort call is made.
  • When the property name is provided to Items.Sort, the property name must appear without the opening and closing brackets if the property is a user-defined property. The brackets cannot be used because of a problem in Microsoft Outlook 2000 and Microsoft Outlook 2002 with processing property names with brackets during the Items.Sort logic.

    Note In Outlook 2000 and Outlook 2002, the use of opening and of closing brackets around user-defined property names is optional for the Items.Sort method; therefore, the brackets can be removed. For the Items.Find method in Outlook 2000, the opening and closing brackets around user-defined property names are required. In Outlook 2002, the opening and closing brackets around user-defined property names are optional.
For additional information about the standard terminology that Microsoft uses when it corrects software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the Standard Terminology That Is Used to Describe Microsoft Software Updates

Modification Type:MinorLast Reviewed:10/3/2005
Keywords:kbHotfixServer kbQFE kbQFE kbfix kbExchange2000preSP4fix kbbug KB826755 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.