This content has been marked as final. Show 4 replies
Yes. Find the Web.config file located at:
Open it in your favorite text editor (Notepad, Notepad++, etc). Find the "httpRuntime" xml node (xpath: /configuration/system.web/httpRuntime).
The "maxRequestLength" attribute is the approximate max file size in KB. I say approximate because some of the request is taken up by http header information. So, for a max file size of 11 MB set this value to 11000. For a max file size of 1GB (this is NOT_ recommended) set this value to 1000000.
However, depending on the file size and the speed of your network, this may not be the only value you need to adjust. There is another attribute of the "httpRuntime" node named "executionTimeout", which may or may not be present in your DRL Web.config. If it's absent, simply add it. I believe the default value is 30 seconds. If the file upload is timing out, try increasing this value to 60 or 90 seconds as needed.
For a maximum file size of 25 MB with a timeout of 90 seconds, your httpRuntime node will look like this:
<httpRuntime executionTimeout="90" maxRequestLength="25000" />
The business is needing this fixed as soon as possible, any word on a solution??
You would have to check the DRL-Prodika event log to find out exactly why the uploads are failing.
I should note that there is no explicitly defined maximum upload file size.
Also, I was informed that approximately 30% of the request length is consumed by SOAP encoding. So, the maxRequestLength value should be set to 1.4 * desired maximum KB.
For a maximum of 11MB, use maxRequestLength=16000. Since, 11000 * 1.4 = 15400, then take the ceiling.
For a maximum of 25MB, try maxRequestLength=35000.