IIS 6.0 MaxRequestBytes parameter not set correctly
Topic Last Modified: 2007-01-05
The Microsoft® Exchange Server Analyzer Tool reads the following registry entry to determine whether the maximum size for HTTP requests has been hard-coded in the registry:
The Exchange Server Analyzer also examines the following registry entry to determine the version of the Microsoft Windows® operating system that is running on the destination computer:
A CurrentVersion value of 4.0 indicates the computer is running Microsoft Windows NT® Server 4.0. A value of 5.0 indicates the computer is running a Microsoft Windows 2000 Server operating system, and a value of 5.2 indicates the computer is running a Microsoft Windows Server™ 2003 operating system.
Finally, the Exchange Server Analyzer examines the Exchange_Server Windows Management Instrumentation (WMI) class in the root\MicrosoftExchangeV2 namespace to determine the value for the IsFrontEndServer key. A value of False indicates that the Exchange Server computer is not a front-end server. A value of True indicates that the Exchange Server computer is a front-end server.
The Exchange Server Analyzer displays a warning if the Exchange Server Analyzer finds that the value for MaxRequestBytes is set to 32768 on an Exchange back-end server on which the following conditions are true:
The Exchange back-end server is running Windows Server 2003.
The Exchange back-end server is not configured as a front-end server.
The Exchange back-end server has more than 500 mailboxes.
The MaxRequestBytes registry value, which is not present by default, determines the upper limit for the total size of the Request line and the headers. This value is typically set in tandem with a companion value, MaxFieldLength. The MaxFieldLength IIS registry parameter specifies the maximum size of any individual HTTP client request. In larger environments, if these values are not set to 32768, Microsoft Office Outlook® Web Access for Exchange Server users can experience logon failures. Specifically, the absence of these values can cause HTTP 400 - Bad Request errors. When configuring the MaxFieldLength registry value, you must also set the MaxRequestBytes parameter to 32768 to enable users who are members of more than 75 groups to log on to Outlook Web Access. If its value is lower than MaxFieldLength, the MaxFieldLength value is adjusted.
|This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore the registry if a problem occurs. For information about how to restore the registry, view the "Restore the Registry" Help topic in Regedit.exe or Regedt32.exe.|
Open a registry editor, such as Regedit.exe or Regedt32.exe.
Right-click Parameters, select New | DWORD value, and then name the value MaxFieldLength.
Right-click Parameters, select New | DWORD value, and then name the value MaxRequestBytes.
In the right pane, double-click MaxFieldLength, and then set its value to 32768 (decimal).
In the right pane, double-click MaxRequestBytes, and then set its value to 32768 (decimal).
Close the registry editor and restart the IIS Admin service for the change to take effect.
Before you edit the registry, and for information about how to edit the registry, see the Microsoft Knowledge Base article 256986, "Description of the Microsoft Windows Registry" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=256986).
For more information about the HTTP registry settings for Internet Information Services (IIS), see the Knowledge Base article 820129, "INF: Http.sys Registry Settings for IIS" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=820129).