topic Re: MaxReceivedMessageSize in QlikView

MaxReceivedMessageSize

ali_hijazi — Mon, 26 Jan 2026 18:19:17 GMT

Hello

Got a task that distributes a document it was working properly until I added a new filed to the selected fields in the reduction tab:

I started getting the following error:

3/2/2015 11:21:32.0141064 Error Exception=System.ServiceModel.CommunicationException: DSC did not respond to request.
Last exception (for http://altqlikview:4730/DSC/Service😞 The maximum message size quota for incoming messages (262144) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element. ---> System.ServiceModel.CommunicationException: The maximum message size quota for incoming messages (262144) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element. ---> System.ServiceModel.QuotaExceededException: The maximum message size quota for incoming messages (262144) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element.

I went to C:\Program Files\QlikView\Management Service

and edited teh QVManagementService.exe.config file and increased the number 262144 to 2621440 (of course after stopping the management service)

but I still get the same error

Please advise

Re: MaxReceivedMessageSize

Giuseppe_Novello — Tue, 03 Mar 2015 19:47:27 GMT

Ali,

Instead can you just double the default number from 26144 to 52288? Make sure when you open the .config file, open it with notepad but "run as administrator", and like you know after the change, restart the QMC service.

Gio

Re: MaxReceivedMessageSize

ali_hijazi — Wed, 04 Mar 2015 08:15:18 GMT

I added a zero to the right so not multiplying it by 2 but rather by 10

but still the error message refers to the old number 262144 and not 2621440

Re: MaxReceivedMessageSize

Giuseppe_Novello — Wed, 04 Mar 2015 13:11:06 GMT

Ali,

Well, the reason I express this bc thats the magic number that has fix other people with same issue. if you believe it is unreasonable you are more than welcome to wait for another best answer.

Gio

Re: MaxReceivedMessageSize

Bill_Britt — Wed, 04 Mar 2015 13:50:54 GMT

I would not add a zero. Giuseppe is correct that doubling it works best most of the time.

Bill

Re: MaxReceivedMessageSize

ali_hijazi — Thu, 05 Mar 2015 10:14:56 GMT

I doubled the number

but I still get the error saying that 262144 has been exceeded

Re: MaxReceivedMessageSize

ali_hijazi — Thu, 05 Mar 2015 10:42:02 GMT

this configuration setting is only available for the Management Service

shall I add it to other services' config files (the MaxReceivedMessageSize)

please advise

Re: MaxReceivedMessageSize

Bill_Britt — Thu, 05 Mar 2015 13:18:21 GMT

No, this issue only affects the QMC.

You can try recreating the task to see if something is corrupted with the other task.

Bill

Re: MaxReceivedMessageSize

sgrice — Mon, 13 Aug 2018 13:03:40 GMT

There is a hard coded timeout of 20 seconds for the workorder to be completed. If a customer has a lot of old disabled tasks, or has had to lower their Chunk Size in the past, this can cause the workorder communication to take longer than 20 Seconds. It will attempt to start over and continue in this loop. This will cause the QMC to list tasks as “Unrunnable” , the QDS status to show as “Cluster Down” and errors in the QMS logs regarding “Quotasize errors.”

In order to resolve the issue, it may be necessary to increase the "MaxReceivedMessageSize" setting found in C:\Program Files\QlikView\Management Service\QVManagementService.exe.config. The issue may also be resolved by adjusting the Chunk Size to a higher value, or cleaning out old disabled tasks, in order to reduce the time the Workorder takes to complete.

In some cases it may be necessary to decrease the chunk size!

Further information can be found in Task Won't Run in Publisher - Adjust Chunk Size as well as QDS Distribution Task Fails With Error "The maximum message size quota for incoming messages (262144) has been exceeded.

Lik to Orig Post

QMC displays “Cluster down” and the status of all tasks is listed as “Unrunnable” - Public Knowledge Base - IPC Global C…