Symptoms

The connection between the adTempus Master and an Agent fails with a status message similar to the following:

System.ServiceModel.FaultException: The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameter http://arcanadev.com/adTempus/4.0:job. The InnerException message was 'There was an error deserializing the object of type ArcanaDevelopment.adTempus.EntityCore.JobDTO. The maximum read depth (256) has been exceeded because XML data being read has more levels of nesting than is allowed by the quota. This quota may be increased by changing the MaxDepth property on the XmlDictionaryReaderQuotas object used when creating the XML reader.'. Please see InnerException for more details.

Cause

This issue can when the Master tries to send the Agent a job that is part of an extensive job chain (jobs connected through Responses, Conditions, or Triggers). The Master incorrectly tries to send data for all jobs in the chain, and this exceeds the allowed level of nesting for objects sent to the Agent.

Workaround

The preferred solution is to apply the software update that corrects this issue. Customers who are unable to do so may be able to work around the problem by increasing the limit mentioned in the error message. The Master will still be sending the excess data (which will reduce performance of Master/Agent operations), but the communications channel can be configured to allow the data.

To do this:

1. In the Console (connected to the Master) open the Advanced Server Options window.

2. Locate the option named "ServiceHost:ReaderQuotas.MaxDepth" and set it to at least 512.

3. Save the changes to the server options.

4. Restart the adTempus service on the Master. The Agent service does not need to be restarted.

If the problem still occurs with the new setting in place, increase the limit in increments of 512 until the problem is avoided.

Resolution

A software update corrects the problem so that the Master does not send the unneeded data.

Status

  • adTempus 4
    This issue has been resolved. Resolved in version 4.4.