XADM: You Cannot Remove a Deleted Universal Security Group from the Permissions of a Mailbox or Public Folder (327168)



The information in this article applies to:

  • Microsoft Exchange 2000 Server

This article was previously published under Q327168

SYMPTOMS

In Exchange 2000 Server, if a universal security group is deleted, an administrator or user may not be able to remove that universal security group from the Client permissions.

When you try to remove the deleted universal security group from the access control list (ACL), you may receive one of the following error messages:
  • If you try to use Exchange System Manager to remove a deleted universal security group (such as Microsoft Windows NT User:S-1-5-21-796845957-...) from the Client permissions of a public folder, you may receive the following error message:
    An unknown error has occurred.
    ID no:8004010f
    Exchange System Manager
  • If you use Microsoft Outlook to remove a deleted universal security group (such as Windows NT User:S-1-5-21-796845957-...) from the permissions of a mailbox or a public folder, you may receive the following error message:
    Some permissions could not be displayed. The client operation failed.
    After you edit the ACL, and then click Apply, you may receive the following error message:
    The modified permissions could not be saved. The client operation failed.

RESOLUTION

To resolve this problem, obtain the Microsoft Exchange 2000 Server Post-Service Pack 3 MDB patch. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

329882 XGEN: Exchange 2000 Server Post-Service Pack 3 MDB Fixes Available


WORKAROUND

To work around this problem, use one of the following two methods.

Method 1

Delete the mailbox or public folder, and then create the mailbox or public folder again.

Method 2

  1. Create new folders with the same name as the problem folders and add a "1" at the end of the folder name. For example, ProblemFolder1.
  2. Assign the same permissions on the new folders.
  3. Copy all items from the problem folders to the new folders.
  4. Delete the problem folders.
  5. Rename the new folders to the original folder names.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Modification Type:MinorLast Reviewed:9/27/2005
Keywords:kbHotfixServer kbQFE kbbug kbExchange2000preSP4fix kbfix kbQFE KB327168