Maximum message size quota for incoming messages (65536) has been exceeded.

3 Years Ago
JorgeR
SCHEDULER AND UNDERLYING SERVICES

Summary

When integrating Bizagi with an external system through a Web Service and the method returns a several amount of records, end users may see an error when they try to complete the task due to the maximum message size has been exceeded.

Applies to

Bizagi 10.x .NET

Symptoms

When an end user tries to complete the task that precedes an automatic task for calling an external Web Service, he/she sees an error like the following:

Unable to process the case: Automatic task failed. ID task=xxx, ID case=xx. Error invoking Web Service Web. Url: http://[server]:[port]/[WebService].asmx, Method: [MethodName] Error:Exception has been thrown by the target of an invocation. The maximum message size quota for incoming messages (65536) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element. The maximum message size quota for incoming messages (65536) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element

Cause

By default, the maximum message size quota for incoming messages that can be shared is 65536 bytes (64 Kb). When the messages size exceeds this limit, Bizagi displays the previous error.

Solution

In order to solve this issue, you need to perform the following steps:

1. Stop Bizagi Web services (you may use IISRESET /Stop in a command prompt with administrator privileges).

2. Locate the server proxy generated by Bizagi in order to communicate with the Web Service, this proxy is normally located in the following path C:\Bizagi\Projects\[ProjectName]\SOA\[ServiceName] and edit the .config file with the text editor of your choice.

3. Locate <binding> tag inside <basicHttpBinding> and add the property maxReceivedMessageSize with any value according to your needs, the following image illustrates the addition of such property with a value of 2147483647 bytes (recommended):


4. Save the file mentioned in previous step and restart Bizagi Web services, you may use IISRESET /Start in a command prompt with administrator privileges.


Details

Last Modified:3 Years Ago
Last Modified By: Andread
Type: ERROR
Level: Advanced
Rated 5 stars based on 1 vote
Article has been viewed 8.6K times.

Options