|Show/Hide Hidden Text|
The SSP7 logging or Scheduler may display the following or similar error message:
SMTX.Common.Classes.SMTXException: RetrieveList generated an error for parameter: 'ConfigurationItem'. ---> System.ServiceModel.CommunicationException: The maximum message size quota for incoming messages (6553600) 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 (6553600) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element.
--- End of inner exception stack trace ---
The cause of this error is the sizing of the XML files that are sent between 2 webservices. In the web.config file of the IIS applications, the maximum size of these XML files is defined. In the example above, a list with configuration items is retrieved from ServiceDesk, but the number of CI's is so large that the data doesn't fit within the maximum size of the message (in this case 6553600 bytes).
Try to redefine your datastore parameter definition in such a way that this limit is not reached. When this is not possible, enlarge the maximum message size for incoming messages in the web.config file of all the SSP7 applications and the Scheduler application. Especially when the error is shown in tasks, it is important to also update the sizing in the scheduler application.
To enlarge the message size, find the following part in the config file:
<binding name="SSP7Binding" closeTimeout="00:01:00" openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00" allowCookies="false" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard" maxBufferSize="65536" maxBufferPoolSize="524288" maxReceivedMessageSize="65536" messageEncoding="Text" textEncoding="utf-8" transferMode="Buffered" useDefaultWebProxy="true">
To change the maximum size of the message, please change the value for maxReceivedMessageSize="65536" into for example maxReceivedMessageSize="655360". There is no real algorithm to define the right sizing and it may need some trial and error to find the right size. Please consider that larger message sizes cause more network traffic.
Other settings than the maxReceivedMessageSize may give similar error messages and can be enlarged in a similar way.