This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario. You use Microsoft Transporter Suite for Lotus Domino to migrate an e-mail message from Lotus Domino to Microsoft Exchange Server 2007. This e-mail message includes an attachment that is greater than 28 MB. In this scenario, you receive the following error message:
The message was migrated without the attachments. This error might be due to configuration limitations on the server. Error details: The request failed with HTTP status 404: Not Found.
This problem occurs because Internet Information Services (IIS) version 7.0 includes a built-in security feature that limits the maximum amount of data in a request. By default, this limit is 30,000,000 bytes, or slightly less than 29 MB.
To resolve this problem, you must make a change in one of the Web.config files on the Exchange Server 2007 computer. To do this, follow these steps:
Open Windows Explorer.
Locate the following folder.
Program Files\Microsoft\Exchange Server\ClientAccess\exchweb\ews
Use Notepad to open the Web.config file.
Locate the section that contains the following entries:
In this section, add the following entries between the <configuration> entry and the <runtime> entry:
The xxxxxxxx placeholder in the MaxAllowedContentLength property indicates, in bytes, the size of the attachment that you want to enable. For example, if you want to enable a size of 40 MB, you can use the following entry:
In the Services snap-in, restart the World Wide Web Publishing Service.
The "executionTimeout" attribute
If you configure the MaxAllowedContentLength property to enable very large attachments, you may also have to configure the executionTimeout attribute. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
953526 Error message when you try to migrate an e-mail message that is larger than 4 MB by using Microsoft Transporter Suite for Lotus Domino: "Maximum request length exceeded"
For more information about the executionTimeout attribute and the maxRequestLength attribute, visit the following Microsoft Developer Network Web site: