Friday, June 22, 2012 7:34 AM
Fully patched SBS2011, complete with Ex2010 SP2 and Ex2010 SP2 RU2.
I've run the BPA 1.3 and it reports that the /EWS virtual directories maxRequestLength doesn't match the get-transportconfig MaxSendSize.
Running get-transportconfig | ft MaxSendSize returns a value of 10485760. Updating the maxRequestLength value in C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\ews\web.config to 10485760 makes the BPA warning go away. All well and good.
However, adding a new user via the console triggers unable to send welcome email with Exchange Web Services. Looking at the adduser.log file I see this error:
[HttpException]: The value for the property 'maxRequestLength' is not valid. The error is: The value must be inside the range 0-2097151. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\web.config line 2376)
Does anyone have advice on the correct settings for this value please, to satisfy the BPA and also to allow addUser to send the welcome email?
- Edited by Susan BradleyMVP, Moderator Saturday, June 23, 2012 12:06 AM Edited title, made it sticky so it can be seen
Saturday, June 23, 2012 12:05 AMModeratorKnown Issue in Windows Server Solutions BPA Update Rollup 3 - TheOfficial SBS Blog - Site Home - TechNet Blogs:http://blogs.technet.com/b/sbs/archive/2012/06/21/known-issue-in-windows-server-solutions-bpa-update-rollup-3.aspxThe bpa is wrong. Put the value back to what it was.
- Marked As Answer by Jim WillsherMicrosoft Community Contributor Saturday, June 23, 2012 7:34 AM
Saturday, June 23, 2012 7:33 AM
- Edited by Jim WillsherMicrosoft Community Contributor Saturday, June 23, 2012 7:34 AM
Sunday, September 09, 2012 6:44 PMI think the problem is that the 'maxRequestLength' is expected to be in KB in the web.config, but the BPA is expecting it to be in Bytes as indicated in resolution step #4 of the BPA results. This has always been an area of frustration for me. Why doesn't (or didn't) MS just establish that bytes are declared as bytes, not has KB or MB, etc. In any *.config file, it's always a toss of the coin as to which metric is required, thus leading to these sorts of erros. Personally, it's not would I would consider top-notch design.
Thursday, January 24, 2013 4:22 AMModerator
Windows Server Solutions BPA Updated January 2013 - The Windows Server
Essentials and Small Business Server Blog - Site Home - TechNet Blogs:
Update Rollup 4 for Windows Server Solutions Best Practices Analyzer 1.0 is available:
After you apply the resolution of the EWSMaxReqLength rule, you cannot delete an email message from Outlook Web Access.
- Marked As Answer by Susan BradleyMVP, Moderator Thursday, January 24, 2013 4:22 AM
Friday, January 25, 2013 3:12 AM
Do you recommend we now should set the maxrequestlenth parameter as suggested by BPA?
Is there any known problem to not follow this suggestion and just to continue ignoreing this warning?
I never understood why this warning appears at all as I (and probably most others) never had problem with not setting this value to the value that is recommended by BPA.
"Susan Bradley [MVP]" schrieb im Newsbeitrag news:email@example.com...
After you apply the resolution of the EWSMaxReqLength rule, you
cannot delete an email message from Outlook Web Access.