XADM: Item Count Incorrect for Messages with Permissions Modified by Using Drive M (302456)
The information in this article applies to:
- Microsoft Exchange 2000 Server
This article was previously published under Q302456 SYMPTOMS
After you use drive M to change the permissions of a message, the item count in folders may be incorrect if you are using Microsoft Outlook 2000 or Microsoft Outlook 98. This problem occurs when you move messages from one folder to another.
CAUSE
Exchange 2000 splits the message counts into multiple parts: the count of items with default Access Control Lists (ACLs) in the JTAB, and counts for each discretionary access control list ID (DACLID) in the discretionary access control lists (DACLs). The client notification uses the value from the JTAB, which does not correspond to the actual count of rows in the folder, or the count of rows that are available to the client. The clients later retrieve only this number of rows, which makes it seem as if the mail is lost.
This problem occurs because the count of items from the JTAB (the default items) is pushed to the client in the remote procedure call (RPC) notify. The client caches these values (EMSMDB) and returns them for the next PR_CONTENT_COUNT request, instead of hitting the server.
RESOLUTION
This fix is for Exchange 2000 servers only. A separate fix for clients is scheduled to be made available shortly. If you encounter this problem, you need this fix for gateway computers. To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix should have the following file attributes or later:
Component: Messaging Database (MDB)
NOTE: Because of file dependencies, this fix requires Microsoft Exchange Server 2000 Service Pack 1.
STATUSMicrosoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 2.
Modification Type: | Minor | Last Reviewed: | 6/5/2003 |
---|
Keywords: | kbbug kbExchange2000preSP2fix kbExchange2000SP2Fix kbfix KB302456 |
---|
|