Error Maximum message size

freek

Solved

Question

Hi There,

I have a error in Service Studio 9 when opening a espace. It gives the following error:

The maximum message size quota for incoming messages (33554432) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element.

Any advice?

17 Nov 2014

Carlos Filipe Simões

Staff

Solution

Hello, guys,

Regarding these latest developments of the bindings file: the file is indeed missing, since there were changes to the way Service Studio works at a more core level, which mean the file is no longer read; this happened starting with Development Environment 11.6.17.

Having said that, the good news is that the underlying value of "MaxReceivedMessageSize" was set to the maximum possible, starting with Development Environment 11.6.21.8208, which means you wouldn't need to set the value in these scenarios anyway.

Could you please test it again using this version and let us know how it went?

Thanks and best regards,

Carlos

See solution in context

08 Jan 2020

AcacioPN

Staff

Hi freek

I had never seen such an error before, but a quick google points me into being a standard .NET issue and not something that's OutSystems related.

According to this post on stackoverflow it seems like a hardcoded limit in Service Studio. I went into the folder where Service Studio is installed (C:\Program Files\OutSystems\Development Environment 9.0\Service Studio), and it seems these values are configured in file ServiceStudio.WS.bindings.config.

From the message, it seems the parameter relevant for this is the maxReceivedMessageSize. Still, as I found out testing, it seems there are other dependent values that need to be consisent. And also, this setting is repeated a lot of times in the file, what I would suggest is:
> Creating a backup copy of the file (in case you get something out of place
> Replace all occurrences of "33554432" with "2147483647" (before you ask, it seems these parameters, such as maxReceivedMessageSize, are all 32-bit integer, and this is the max value is this one).

I just tested this and at least Service Studio starts and is able to connect to Platform Server 9, downloading eSpaces and publishing them without any issues. I did not try to bring the value down to get the error, but this fix makes sense.

Please let me know if this fixes your problem.

Acácio

27 Jan 2015

Luís Cardoso

Hi,

I get this error on my Cloud Account. How can I fix this?

Thanks

16 Feb 2015

AcacioPN

Staff

Hi Luis

just use the instructions above. These apply to Service Studio (AKA Development tools) which are installed in your workstation, so they also apply if you are using the platform in the cloud.

Acácio

16 Feb 2015

Luís Cardoso

Thanks Acacio, but I'm using a Personal Environment, I don't have access to the workstation.

16 Feb 2015

AcacioPN

Staff

Hi Luis The workstation is your computer - where you installed Service Studio. Check the path I indicated above: It's where Service Studio is installed in your computer. Acácio

16 Feb 2015

Ryan Heiser

You need to update the file in the dev elopment folder as well as the service center folder

c:\Program files\OutSystems\Development Environment 8.0\ServiceStudio.WS.bindings.config

c:\Program files\OutSystems\Service Studio 8.0\ServiceStudio.WS.bindings.config

backup the file and then do a find a nd replace

Replace all occurrences of "33554432" with "2147483647" (before you ask, it seems these parameters, such as maxReceivedMessageSize, are all 32-bit integer, and this is the max value is this one).

18 Feb 2015

Bruno Silva

Any idea where this file in in in the MAC version of Service Studio?

08 Apr 2019

1 reply

31 May 2019

Show thread

Hide thread

Anbarasu Theresnathan

Bruno Silva wrote:

Any idea where this file in in in the MAC version of Service Studio?

Find the Path below

Macintosh HD/Applications/OutSystems Service Studio.app/Contents/Resources/OutSystems Service Studio.app/Contents/Resources/wine-prefix/drive_c/Program Files/OutSystems/Development Environment 11.0/Service Studio

31 May 2019

Kilian Hekhuis

MVP

Hi Bruno,

Do you get the same error? Note this is a very old topic, talking about version 9!

08 Apr 2019

3 replies

Last reply 08 Apr 2019

Show thread

Hide thread

Bruno Silva

Kilian Hekhuis wrote:

Hi Bruno,

Do you get the same error? Note this is a very old topic, talking about version 9!

Hi, yes ... I get tis error still in version 11, On the windows version of service studio I am able to do the suggestion on the top of this thread, but I'm working with the OSX version and cant find the ServiceStudio.WS.bindings.config file

08 Apr 2019

Craig St Jean

Staff

Bruno,

It should be in /Applications/OutSystems Service Studio.app/Contents/Resources/OutSystems Service Studio.app/Contents/Resources/wine-prefix/drive_c/Program Files/OutSystems/Development Environment 11.0/Service Studio/ServiceStudio.WS.bindings.config

Right click on your OutSystems Service Studio app and click Show Package Contents in order to drill down to it.

Hope that helps!

08 Apr 2019

Bruno Silva

Craig St.Jean wrote:

Bruno,

Right click on your OutSystems Service Studio app and click Show Package Contents in order to drill down to it.

Hope that helps!

Yep, this is the path, I was able to find it, do the changes suggested above and it all worked.

Thank you very much for the fast replies!

08 Apr 2019

Kilian Hekhuis

MVP

Ok, I'll ask around.

08 Apr 2019

Luis Morales

Hey guys,

I see how we should go about changing the max size, but is there a way to figure out where it's trying to send something of that size. I have a small app I'm just starting the build process on and I'm getting this. I'd like to know where in the app something is supposed to be sending a message that would exceed the max size?

11 Apr 2019

Nicholas Carter

There has got to be a better way of doing this, I sware I have modified this file 5 times now. It just keeps reverting and causing this extremely frustrating error.

05 Nov 2019

1 reply

06 Nov 2019

Show thread

Hide thread

AcacioPN

Staff

Nicholas Carter wrote:

There has got to be a better way of doing this, I sware I have modified this file 5 times now. It just keeps reverting and causing this extremely frustrating error.

Hi Nicholas

I understand what you are going through. Editing the file with Service Studio open is nearly impossible - it seems it keeps refreshing it; add that to the way Windows manages permissions of the Program Files folder these days...

How I did it in the past was: copy the file to your desktop; edit the file there. Then close Service Studio; rename the file to OLD_ServiceStudio.WS.bindings.config , move your edited file there and open Service Studio. Should work like a charm!

Hope this helps!
Acácio

06 Nov 2019

Filipe Barretto

Hi everyone.

I'm sorry to re opem this post but

I'm get the same error ("33554432") and I dowloaded Outsystens 11 today(06/01/2020) version 11.6.18, build 8128 and the file ServiceStudio.WS.bindings.config don't existe in

\OutSystems\Development Environment 11.0\Service Studio

could somone help me?

06 Jan 2020

Hanno

Don't go above version 11.6.16.7525. That is the last version that uses the config files. Versions after that "might" work, but mine did not.

08 Jan 2020

Carlos Filipe Simões

Staff

Solution

Hello, guys,

Could you please test it again using this version and let us know how it went?

Thanks and best regards,

Carlos

08 Jan 2020

Ravi Vakkalanka

Hi Carlos,

I am using 11.6.30 and still getting this error while trying to consume a WSDL. Is there anyway to resolve this error ?

Invalid WSDL (Detail: Metadata contains a reference that cannot be resolved: 'https://wd2-impl-services1.workday.com/ccx/service/standard_gms1/Resource_Management/v34.0?wsdl'. There is an error in XML document (1, 801). The maximum message size quota for incoming messages (3000000) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element.)

Thanks

Ravi

12 Mar 2020

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.

See the full guidelines