How to Resolve Microsoft Exchange 2010 Large Message Restore Errors
Error Message
If you attempt to restore large messages from Microsoft Exchange 2010, you may encounter a Max EWS Request error:
Modify web.config
Use the following steps to resolve a failed restore:
Log into your Microsoft Exchange 2010 Server as the administrator, and navigate to the Program Files > Microsoft > Exchange Server > V14 > Client Access > exchweb > ews folder, and create a copy of the file web.config:
Open the original web.config file using Notepad running as the administrator.
In Notepad, go to Edit > Find, and enter max in the find what field:
Click Find Next until you locate the following line of code:
<httpsTransport maxReceivedMessageSize="13600000" authenticationScheme="Anonymous" maxBufferSize="81920" transferMode="Streamed" />The value
maxReceivedMessageSize="13600000" represents a maximum attachment size of 13MB. Therefore, any attachments over 13MB cannot be restored. Change this value to a larger value to handle the largest attachment failing to restore, for example, replace13600000with53600000which allows for attachments just over 50MB:
Click Find Next until you locate the following line of code:
<httpsTransport maxReceivedMessageSize="13600000" authenticationScheme="Anonymous" maxBufferSize="81920" transferMode="Streamed" />Replace
13600000with the same value you entered in step 5 above, for example,53600000.Click Find Next once again until you locate the following line of code:
<requestLimits maxAllowedContentLength="13600000" />Replace
13600000with the same value you entered in step 5 above, for example,53600000.
Click File > Save, and close Notepad.
Run appcmd
Log into your Microsoft Exchange 2010 Server, and at a command prompt, change the directory to the inetsrv folder:
cd c:\windows\system32\inetsrvAt a command prompt, run the appcmd command using the new size limit value you entered in the previous section:
appcmd set config "Default Web Site/ews" -section:requestFiltering -requestLimits.maxAllowedContentLength:53600000Close the command prompt.
Open Services and restart the following services:
Restart IIS Admin Service:
Restart Microsoft Exchange Transport:
Barracuda Backup Restore
Log in to your Barracuda Backup web interface, and restore the messages that originally failed.
Messages should now restore without any errors. However, if you continue to encounter errors when restoring large messages, continue to the next section, Configuration Settings.
Configuration Settings
Microsoft Exchange 2010 Configuration Settings
Use the steps in the following sections only if you continue to encounter errors when restoring large messages.
Verify Exchange Management Console Settings
Log in to your Microsoft Exchange 2010 Server, and open the Exchange Management Console (EMC).
Expand Organization Configuration, click Hub Transport, and click the Global Settings tab:
Right-click Transport Settings, and click Properties:
Verify the Transport Limits settings are large enough and listed correctly, then click OK.
In the EMC, expand Server Configuration, click Hub Transport:
Right-click on the Client Receive Connector, and click Properties:
Verify the value in the Maximum message size (KB) is large enough to accommodate message restore.
Right-click the Default Receive Connector, click Properties, and verify the Maximum message size (KB) is large enough to accommodate message restore.
If you modified any settings in the preceding steps, go to Services and restart both IIS Admin Service and Microsoft Exchange Transport services.
Exchange Management Shell
Open the Exchange Management Shell, and enter the following command:
get-tranportconfig:Verify that the following settings are large enough and listed correctly:
ExternalDsnMaxMessageAttachSizeInternalDsnMaxMessageAttachSizeMaxReceiveSizeMaxRecipientEnvelopeLimit (shown in KB)MaxSendSize
If any of the values need modification, run the following command:
Set-transportconfig -<setting to be changed> <size>
For example:set-transportconfig -MaxSendSize 50MBIf you modified any values through the Exchange Management Shell, go to Services and restart both IIS Admin Service and Microsoft Exchange Transport services.