===== [V7] ISSUE: ERROR=MAPI_E_CALL_FAILED Detail=Unspecified error (MS Exchange Mail Level restore) =====
This article only applies to Ahsay software version 7
Article ID:
5361
Reviewed:
2019-03-29
Product Version:
AhsayOBM: 7.3 to 7.x
OS: Windows
ATTENTION
1st January, 2022: v7 officially End-of-Life [details]
===== Problem Description =====
When performing a MS Exchange Mail Level restore, the following error is shown in the restore log:
No.
|
Type
|
Timestamp
|
Log
|
*
|
...
|
...
|
...
|
*
|
erro
|
YYYY/MM/DD
hh:mm:ss
|
[PostRestoreMailTask.run] Path=SERVER\Mailbox Store\Mailbox\Folder\mail_item Throwable=NewMessage ERROR=MAPI_E_CALL_FAILED Detail=Unspecified error
|
*
|
...
|
...
|
...
|
===== Cause =====
This issue can occur if the mail item(s) to be restored exceeded the message size limits (MaxReceiveSize) setting configured for the restore destination Exchange server.
===== Resolution =====
To resolve the issue, temporarily configure the maximum message size that can be received by recipients in the organization (MaxReceiveSize) to unlimited, before performing the restore.
- Check on the current "MaxReceiveSize" setting of the restore destination Exchange server, enter the following command in Exchange PowerShell:
For more details on the Get-TransportConfig cmdlet, refer to - https://docs.microsoft.com/en-us/.../get-transportconfig
- Temporarily modify the "MaxReceiveSize" setting to unlimited, enter the following command in Exchange PowerShell:
Set-TransportConfig -MaxReceiveSize unlimited
|
For more details on the Set-TransportConfig cmdlet, refer to - https://docs.microsoft.com/en-us/.../set-transportconfig
- Perform the MS Exchange Mail Level again afterward to see if the problem persist.
Important: Revert the "MaxReceiveSize" setting to its original value afterward, or modify the setting according to the requirement of the mailbox users.
===== Keywords =====
exch, mail, brick, restore, restoring, exchange, ex-change, MAPI_E_CALL_FAILED