XADM: Slow Performance When Opening Unread Item from Public Folder with Many Restrictions

ID: Q235679

The information in this article applies to:

Microsoft Exchange Server, version 5.5

SYMPTOMS

All users attempting to open any unread message item in a particular public folder experience a long delay before the message is opened.

CAUSE

The public folder has many server-side restriction tables (views) associated with it. Whenever a change is made to a message in a folder, or a new message created or deleted, the message must be evaluated against all the server-side restrictions so that they can be updated. Opening an unread message changes the state of the MSGFLAG_READ bit of the PR_MESSAGE_FLAGS MAPI property. Normally, each restriction is represented by a table in the database, and this table must be opened to be updated/evaluated. It is possible, however, for the information store to avoid opening the table if the client operation is simply changing the read/unread state of a message, because the server can tell (without opening the table) if the restriction involves the MSGFLAG_READ bit.

RESOLUTION

Code was added to the information store to check if the restriction involves the read/unread message flags and if not, it can avoid opening the restriction table (which improves performance).

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Microsoft Exchange Server version 5.5 service pack that contains this fix.

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 on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

The English version of this fix should have the following file attributes or later:

Component: Information Store

File name	Version
Store.exe	5.5.2644.0
Mdbmsg.dll	5.5.2644.0
Netif.dll	5.5.2644.0
Gapi32.dll	5.5.2644.0
Dsamain.exe	5.5.2600.0
Perfdsa.dll	5.5.2600.0

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:

Q154871 Determining If You Are Eligible for No-Charge Technical Support

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5.

Additional query words:


Keywords          : exc55 
Version           : winnt:5.5
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: August 8, 1999