Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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"


View products that this article applies to.

Symptoms

You use Microsoft Transporter Suite for Lotus Domino to migrate a mailbox from Lotus Domino to Microsoft Exchange Server 2007. When you try to migrate an e-mail message that is larger than 4 megabytes (MB), you may 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: Maximum request length exceeded.

↑ Back to the top


Cause

This problem occurs because the default limit in ASP.NET for the input stream buffering threshold is 4 MB.

↑ Back to the top


Resolution

To resolve this problem, increase the input stream buffering threshold value. You may also have to increase the execution time-out period. To do this, follow these steps:
  1. Start Notepad.
  2. Under the following directory, open the Web.config file:
    drive:\%PROGRAMFILES%\Microsoft\Exchange Server\ClientAccess\exchweb\ews
  3. In the Web.config file, add the following line after the <system.web> tag:
    <httpRuntime executionTimeout="1200" maxRequestLength="51200" />
    After you add this line, the Web.config file section resembles the following section.
    <system.web>
          <httpRuntime executionTimeout="1200" maxRequestLength="51200" />
          <httpModules>
    Note The executionTimeout attribute is in seconds. This attribute indicates the maximum number of seconds that a request can run before ASP.NET automatically stops the request. The maxRequestLength attribute is in kilobytes (KB). Adjust each attribute as appropriate for your environment.
  4. Save and then close the Web.config file.
  5. Restart the World Wide Web publishing service.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

For more information about the executionTimeout attribute and the maxRequestLength attribute, visit the following Microsoft MSDN Web site:

↑ Back to the top


Keywords: KB953526, kbprb, kbtshoot, kbexpertiseinter

↑ Back to the top

Article Info
Article ID : 953526
Revision : 1
Created on : 6/9/2008
Published on : 6/9/2008
Exists online : False
Views : 389