Re: OWA Access Problem
- From: "Oliver Moazzezi" <o.moazzeziNO@xxxxxxxxxxxxxxxxx>
- Date: Thu, 19 Apr 2007 13:47:48 +0100
Hi,
When running ExBPA (download from:
http://www.microsoft.com/downloads/details.aspx?familyid=DBAB201F-4BEE-4943-AC22-E2DDBD258DF3)
See if it outlines the following, which can cause a 400 bad request for OWA
users on an Exchange Backend:
IIS 6.0 MaxRequestBytes parameter not set correctly Send Feedback
: : : : : : :
(Declaration)
(Usage)
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:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters\MaxRequestBytes
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:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\CurrentVersion
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 ServerT 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:
a.. The Exchange back-end server is running Windows Server 2003.
b.. The Exchange back-end server is not configured as a front-end server.
c.. The Exchange back-end server has more then 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 2003 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.
Important:
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.
To set the MaxRequestBytes and MaxFieldLength parameters
1.. Open a registry editor, such as Regedit.exe or Regedt32.exe.
2.. Navigate to:
HKLM\System\CurrentControlSet\Services\HTTP\Parameters
Oliver
begin 666 pencil.gif
M1TE&.#EA$0`1`/4``/3LF*207/#;<U9&(-:\5/+JM[*60\IZ:3,P+OSZ]G=W
M>LN*?61C9R\L*Y R,._M[:IR7FMG7IY21^+=HV@X*=>9BJA;3:6LM<IL6&0I
M(G1Y?O+JMK:>5E='(O3MPZ5C5=&V4O/JNY P,/7OS[RWJ(IB6L7,UJ2176<I
M(K&32+241%5+,^3-:GJ BBTI)KZ\MY^.8O___P``````````````````````
M`````````````````````````````````"'Y! $``#$`+ `````1`!$```9Q
MP)AP2!26/L7D$%(Y2)1%YN+@A I/IND!(T)!`Y[)98&Q.#+*0 $`$)LIZ36;
MQ6G!DVHV0 !2=>)Z`@0&`X!L@H1I&X&#A4DP(8R)21HD(X>-4 P/"0F"*8Y*
9# H)#R\1*U8Q# @*"A$-JC$N"+6QLD$`.P``
`
end
begin 666 drpdown.gif
M1TE&.#EA#P`1`,0``-/=^];?^[6]Y):<N]SD_.[S_NOP_N7K_0```NGL^M[F
M_.OQ_MGB_ ``!.;L_>+I_0`!!0$!`^SQ_NCN_0``````````````````````
M`````````````````````````"'Y! ``````+ `````/`!$```5:8"*,9$F*
M1:JNZB!(BR'/].).SJ'OO.,^"H)P2%2X%(R <LEDN @!@'1*#3RC`,@4,;4*
IH-(&%\&5>L%21*1LOE(;5, 9&^^ZZ_8O'3_'Y]%^5@D#A(6&A0DA`#L`
`
end
begin 666 note.gif
M1TE&.#EA"@`*`+,)`/\$`/]=6L;#QM;3UO_/`(2&A(R.C ```/__SO___P``
M`````````````````````"'Y! $```D`+ `````*``H```0HT,@Y1 `&Z7T(
AWEIW)!E'C.16G$.2(L-1((5;%D-H@_H+HH>@,.B*```[
`
end
.
- Follow-Ups:
- Re: OWA Access Problem
- From: adac
- Re: OWA Access Problem
- References:
- OWA Access Problem
- From: adac
- OWA Access Problem
- Prev by Date: OWA Access Problem
- Next by Date: Outlook web
- Previous by thread: OWA Access Problem
- Next by thread: Re: OWA Access Problem
- Index(es):
Relevant Pages
|
