topic The maximum message size quota for incoming messages (65536) has been exceeded in QlikView

The maximum message size quota for incoming messages (65536) has been exceeded

Mon, 26 Jan 2026 18:19:17 GMT

I am trying to get a list of list of source documents -

ServiceInfo[] ServiceList = Client.GetServices(ServiceTypes.All);
Guid QvsGuid = ServiceList[2].ID;
            
foreach (ServiceInfo info in ServiceList)
{
      Console.WriteLine(info.Name);
}

QVSSettings QvsSettings = Client.GetQVSSettings(QvsGuid, QVSSettingsScope.Distribution | QVSSettingsScope.Documents);
QDSSettings qdsSettings = Client.GetQDSSettings(QvsSettings.Distribution.QDSID, QDSSettingsScope.All);


Guid qdsGuid = QvsSettings.Distribution.QDSID;

//Get source documents  
DocumentNode[] sourceDocuments = Client.GetSourceDocuments(qdsGuid);

The last step fails with following error -

An unhandled exception of type 'System.ServiceModel.CommunicationException' occurred in mscorlib.dll

Additional information: 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.

I am not sure why I am getting this error - I don't think I have that many documents. Any suggestions?

Re: The maximum message size quota for incoming messages (65536) has been exceeded

Tue, 29 Sep 2015 05:33:52 GMT

You get due to you have many Source documents and the total message returned is larger than 65536.

This limitation is the default behaviour by Microsoft. However you can modify is by changing the MaxRecievedMessageSize on the binding to API (see https://msdn.microsoft.com/en-us/library/system.servicemodel.basichttpbinding.maxreceivedmessagesize(v=vs.100).aspx)

Also in all QlikView services you can change this value in the config file per executable like this (QlikView a higher default value of 262144):

Re: The maximum message size quota for incoming messages (65536) has been exceeded

Tue, 29 Sep 2015 13:25:48 GMT

Thank you! I increased the max limit in the app config file, and it solved the problem.