You don't get a timeout either? if you do, you can add the executiontime in the requestLimits line.

Example:

<httpRuntime executionTimeout="110" maxRequestLength="131072" />

But I must admit that I have a similar issue in one (and only one) of our environments. I'm sure the length paramaters are sufficient, but when I start uploading the solution it dosn't do anything and returns to the list screen after a couple of seconds. No idea why because we use the same settings on several other environments and there it works.

This is something, you really need to contact support for it.

I would suggest trying to split the OSP up into smaller pieces if possible, just to get some traction on this.

Look at the dependencies of the application, do the "bottom" stuff first, then the top, see if that helps.

Also, why is it 200 MB? Is that a ton of images and other resources in the eSpaces, or is it really just a LOT of code/eSpaces?

J.Ja

Thanks for the responses.  We have tried the configuration change suggested by Kurt without success.  We have now contacted OutSystems support.

The reason that the file is 200MB is that it is a LOT of functionality.  It is a rewrite of our flagship product, which the previous version consisted of over 500MB of Java, ASP and .Net files.

OutSystems support were very helpful.  The fix was to tweak 4 parameters.

• Modify applicationHost.config (located at %WINDIR%\system32\inetsrv\config) by changing from the OutSystems installation checklist recommended values to larger value

  <requestLimits maxAllowedContentLength="134217728" /> to larger size 
  <requestLimits maxAllowedContentLength="250000000" />  - i.e. greater than OSP file size.

• Modify machine.config (located at %WINDIR%\Microsoft.NET\Framework64\v4.0.30319\CONFIG\machine.config) timeout from default 110 secs to 2000 secs (about 33minutes)  and maxRequestLength from 131072 to a larger value, we set it to 131072000 

           i.e. <httpRuntime executionTimeout="2000" maxRequestLength="131072000" />.  

Note that these can be configured  via IIS rather than having to edit the file manually

• Modify database default query timeout from 30 to 300 in the Advanced Database Connection Settings screen of OutSystems Configuration Tool as shown below

Thanks to the Support team for the quick response.

Helped a lot. Thank you.

I ran in the upload issue with really large OSP and this is really tricky. Gonna try these options.

Swatantra, you can set the timeouts in Service Studio under the Edit->Preferences menu option.

We had to set the timeout to longer (4x the original timeout) for .oml file(s) of 40MB or larger files on slow connections

Thanks Hanno. That's super handly.

Hi Hanno,

Even after setting it, I'm getting the error message related to 'Short operations Timeout'

Swatantra, have you tried uploading the .osp through Service Center?

Hello. Sorry to "wake" this topic after so much time.

I'm having the same problem when I try to upload my .osp file.  

But I use Service Studio on a Mac, so I don't know how to access the files mentioned above.

Can someone help me with that issue on a Mac? 

Thank you

For anyone who is on a free plan and needs to upload a .osp file that is too large please see the following help document.

https://success.outsystems.com/documentation/11/setup_outsystems_infrastructure_and_platform/setting_up_outsystems/unattended_installation_and_upgrade/solution_pack_tool_command_line_reference_osptool/

There is a program named "OSPTool.exe" located in your "C:\Program Files\Common Files\OutSystems\11" folder that allows you to turn .osp files into individual .oml & .xif files which you can upload one by one.