This blog article outlines how to configure the DocumentsCorePack Print Application for Microsoft Dynamics 365.

This article outlines why DocumentsCorePack need Application Permissions.

This blog article outlines how to proceed if you have an issue with your Load Balancing service for DocumentsCorePack On-Premise.

This blog article outlines the AttachmentExtractor plugin file access behavior if your service stops running.

This blog article outlines how the Cloud service structure for AttachmentExtractor works. AttachmentExtractor will retrieve documents from Dynamics 365 instance, move it to an alternative storage location and deliver it back to Dynamics 365 upon user request.

This blog article outlines that it is possible to use non-interactive users to create a service for AttachmentExtractor or DocumentsCorePack.

This blog article outlines how the heartbeat service restart behaviour works in case that Dynamics 365 is not available for some reason.

The error message displayed in Figure 1 indicates, that there are either too many documents to generate (rather unlinkely) at the moment or that the DCP service is not running. 

This blog article outline how to react if your DocumentsCorePack (DCP) Service stopped working. It is most likely because the username and password credentials are not working anymore.

Please note: In most of the cases this happens because the password of the Office365 account has expired. We would recommend you to "Setup your password to never expire" for the account on which you run the DCP service. 

When using our products, the CRM discovery service is contacted to retrieve the service URLs for accessing the CRM WebServices.

In some cases the URL returned by the discovery service is not useable to contact the CRM WebService.