Microsoft KB Archive/159876

From BetaArchive Wiki
Knowledge Base


XADM: Permissions Lost During Move Mailbox Operation

Article ID: 159876

Article Last Modified on 10/28/2006



APPLIES TO

  • Microsoft Exchange Server 4.0 Standard Edition



This article was previously published under Q159876

SYMPTOMS

The following error occurs in Schedule+ when attempting to "open other's appointment book" of a recently moved mailbox:

The schedule could not be open. Access is denied.

Moving a user mailbox is done in the Microsoft Exchange Administrator program by accessing the Move Mailbox command from the Tools menu and can only be done between Microsoft Exchange Severs in the same Microsoft Exchange Site. Moving mailboxes between Servers in a Site with the Move Mailbox utility can cause previously assigned permissions on the mailbox to be temporarily lost.

CAUSE

The Move Mailbox command ignores the default access control list (ACL) when resetting the ACL data during the move. Any users that previously accessed the appointment book using default access permissions subsequently fail. Users with explicit permissions to the appointment book do not experience this error.

WORKAROUND

To view the schedule:

  1. In Schedule+ on the mailbox that can't be opened, on the Tools menu, click Set Access Permissions and verify that the user attempting to view the schedule does have the required permissions.
  2. Click OK, which will effectively reset the permissions and allow clients with permissions to view the schedule.

If other users are unable to open this mailbox:

  1. Re-apply the permissions on the mailbox that has permissions set.
  2. Remove and re-add the other mailbox from the profile of the user that is having problems opening the mailbox.


STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 4.0. This problem was corrected in the latest Microsoft Exchange 4.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K


This problem was also corrected in Microsoft Exchange Server version 5.0.

Keywords: kbbug kbfix kbusage KB159876