Patch Management Solution

 View Only
  • 1.  MetaData Import Task error "The page was not displayed because the request entity is too large"

    Posted Sep 30, 2014 04:10 PM
      |   view attached

    Trying to save changes to 'Vendors and Software' in the MetaData Import Task result in the error "The page was not displayed because the request entity is too large".  I am using IE11, but have had the same results in IE9.  I am using Patch 7.5 SP1 (7.5.3219) but I have had this issue since 7.1.  Sometimes reopening IE or making a smaller set of changes helps, but often it does not.  Could this be an issue with IIS?



  • 2.  RE: MetaData Import Task error "The page was not displayed because the request entity is too large"
    Best Answer

    Posted Oct 03, 2014 12:17 PM

    Hello there,

     

    Just fought and fixed the same issue.  It was our first time using SSL in Altiris and my NS was choking on the overhead caused by https traffic. 

    1. On the Notification Server, navigate to %windir%\System32\inetsrv and copy the applicationHost.config file to a safe location

    2. While still on the Notification Server, open an elevated command prompt and execute the following command without line breaks.

     

    appcmd.exe set config "Default Web Site/Altiris" -section:system.webServer/serverRuntime /uploadReadAheadSize:"1048576" /commit:apphost

    You should recieve output to the effect of "Wow that was successful" (or something similar)

    3. Restart IIS and give it another try.  Magically, the SSL traffic has enough room to breath and the error shouldn't bother you anymore.

     

    CAUTION NOTE:  If something should go wrong, simply stop IIS, replace your applicationHost.config file with the one that you carefully copied to a secure location and restart IIS. 



  • 3.  RE: MetaData Import Task error "The page was not displayed because the request entity is too large"

    Posted Oct 03, 2014 02:38 PM

    Thank you, PS_Guru.  I saw some articles on this but I was a little trigger shy.  Thank you for confirming.  I did get the output "Wow that was successful", though I was more surprised that it came out of me, not the command line  :)