Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
SBS BPA 1.3 - do not set rule for maxrequestlength as noted by the BPA

Sticky SBS BPA 1.3 - do not set rule for maxrequestlength as noted by the BPA

  • Friday, June 22, 2012 7:34 AM
     
     
    Sign In to Vote
    0

    Hi all

    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?

    Many thanks,

    Jim


     

All Replies

  • Saturday, June 23, 2012 12:05 AM
    Moderator
     
     Answered
    Sign In to Vote
    2
    Known Issue in Windows Server Solutions BPA Update Rollup 3 - The
    Official SBS Blog - Site Home - TechNet Blogs:
     
    The bpa is wrong.  Put the value back to what it was.
     
     
  • Saturday, June 23, 2012 7:33 AM
     
     
    Sign In to Vote
    0

    Thanks Susan.....

    Jim


     
  • Sunday, September 09, 2012 6:44 PM
     
     
    Sign In to Vote
    2
    I 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.

    • Edited by RandyGlenn Sunday, September 09, 2012 6:45 PM
    • Edited by RandyGlenn Sunday, September 09, 2012 6:47 PM
    •  
     
  • Thursday, January 24, 2013 4:22 AM
    Moderator
     
     Answered
    Sign In to Vote
    0

    Windows Server Solutions BPA Updated January 2013 - The Windows Server

    Essentials and Small Business Server Blog - Site Home - TechNet Blogs:

    http://blogs.technet.com/b/sbs/archive/2013/01/23/windows-server-solutions-bpa-updated-january-2013.asp

    Update Rollup 4 for Windows Server Solutions Best Practices Analyzer 1.0 is available:
    http://support.microsoft.com/kb/2796170

    Issue 2


    After you apply the resolution of the EWSMaxReqLength rule, you cannot delete an email message from Outlook Web Access.

    Now fixed!

     
  • Friday, January 25, 2013 3:12 AM
     
     
    Sign In to Vote
    0

    Hi Susan

    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.

    Henry

    "Susan Bradley [MVP]" schrieb im Newsbeitrag news:8f61f9c0-0014-48bd-86f6-f89e9bfcd134@communitybridge.codeplex.com...

    After you apply the resolution of the EWSMaxReqLength rule, you
    cannot delete an email message from Outlook Web Access.