Wednesday, May 8, 2019

Dynamics365 - The size necessary to buffer the XML content exceeded the buffer quota

During a regular deployment the last weeks, we were running into a generic error.


Error - System.ServiceModel.QuotaExceededException: The size necessary to buffer the XML content exceeded the buffer quota

Since our Solution size is far away from being critical, this could not be the problem. Also the deployment worked fine in the QA environment

After investigating a bit, we came to know that this was related to the Database replication which has been extended by the DB team of the customer independently. After reverting this change, the deployment worked fine.

cheers

Tuesday, May 7, 2019

Dynamics365 - SQL Reporting working / FetchXML Reporting not working (rsProcessingAborted)

There are thousands of posts about the rsProcessingAborted error but most of them are pointing to general reporting (rdl) issues.

In the current project (ongoing for few years), we introduced the first FetchXML based report now. The previous ones have been SQL based (OnPrem).

After deploying the report from Test to QA, the following error code appeared.

The report cannot be displayed. (rsProcessingAborted)

Since SQL based reports were working fine it could not be a general reporting issue.
Also a newly created temp report with only one column was not working so also an error with the newly designed report could not be the reason.

After checking the SSRS logs (\Reporting Services\LogFiles), I could see following message.

Could not connect to net.tcp:///CrmSandboxSdkListener-w3wp.

After checking the Implementation Guide - "Dynamics365_PlanandDeploy.pdf", I found the following entry.


After opening the TCP 808 port, the rendering worked as expected.

cheers

Monday, March 25, 2019

Dynamics365 - Upgrade Issues 8.2.3

There are some nice articles out there explaining issues/experiences with the 8.2.3 upgrade.
E.g. the one from Kylie Kiser (Link).

One thing we recognized after the upgrade was the broken Signature Feature.

Scenario

  • Signature is owned by a Team
  • User is assigned to that Team
  • User creates an email and clicks "Insert Signature"
  • The user can see the list of available Signatures (e.g. DE)
  • Now, the user changes the language (e.g. to EN) and would expect the configured english signatures
  • Instead of that, the list remains empty
  • Also switching back to the base language (e.g. DE) does not work anymore. The list remains empty.


The problem does not appear, when the template is owned by an User.
Microsoft accepted this as a defect and will fix it - Let´s see when.

cheers