-
Titre
The error "MAPI_E_NO_ACCESS" is seen in the Public Folder target log during public folder synchronization -
Description
The following errors are found in Public Folder Target Agent log file:
'C8469E775A911247992BCF7AA61E47FB0000006AA02C'). 3/13/2007 2:02:26 PM aeFolder::LoadFromString Error -2126512126 aeMAPIFolder::CopyToExchangeFolder failed - MAPI_E_NO_ACCESS, try to set folder ACL.. File: 'aeMAPIProp.h' Line: '375' (Folder: 'FOLDER_NAME ', SourceKey: '0CF1A9BAE034484E985487B7A7CC04300000000A9F28') 3/13/2007 2:02:26 PM aeFolder::LoadFromString Warning -2147024891 Access is denied. File: 'aeMAPIProp.h' Line: '375' (Folder: 'FOLDER_NAME ', SourceKey: '0CF1A9BAE034484E985487B7A7CC04300000000A9F28') 3/13/2007 2:02:26 PM CFolder::CopyFromPST Error -2147024891 You do not have sufficient permission to perform this operation on this object. See the folder contact or your system administrator. - MAPI_E_NO_ACCESS (Microsoft Exchange Server Information Store) File: 'aeMAPIFolder2.cpp' Line: '728' (Folder: 'NAME', SourceKey: 'C8469E775A911247992BCF7AA61E47FB0000006AA02C') (Folder: 'FOLDER_NAME ', SourceKey: '0CF1A9BAE034484E985487B7A7CC04300000000A9F28')However when logged into the mailbox of Administrator account with service credentials there are no problems in creating public folders under the same hierarchy where the agent fails.
-
Cause
This issue can be encountered in some secure environments where the Exchange Migration account was not granted Full Admin rights over the entire Exchange organization but just only over some Administrative Groups. Please refer to the resolution for more details.
-
Résolution
The account that is used with the Public Folder agent needs to have Full admin right over the Administrative Group of the target exchange server as well as the Administrative Group where the default MAPI public folder tree (APF) was initially created during the first exchange server install. If the above conditions are not met the MAPI_E_NO_ACCESS error is encountered when trying to set a folder ACL on the target.
Please see the appropriate documentation regarding Source preperation:
MigrationManagerExchange_8.x_SourceExchange2007_Preparation.pdf
or
MigrationManagerExchange_8.x_SourceExchange2010_Preparation.pdf
etc, depending on the Exchange version within the source Organization.