This blog article explains what to do when you receive the following error message while saving documents to SharePoint.

DocumentsCorePack failed to generate the document

ERROR:|CHECKLICENSE|SUCCEEDED|new AutoMerge|StartMerge|ErrorMessage:No part of the path

If you receive the following error when creating a label template in DCP for CRM 2013, your DCP Server Component is very likely not up to date.

The settings of DocumentsCorePack now allows you to configure the "Name" and the "Subject" for the "Document Name" separately. Available vor v5.93 and higher.

This  feature offers you the option to save a document directly to the proper location in CRM without having to generate an activity. 
The location depends on the configuration, which is defined within the DocumentsCorePack server configuration tool.

To take adavantage of this new feature you need at least the following version:

 - DocumentsCorePack Client for MS CRM 2011 5.73

Each product installs the following entities in CRM:

ptm_mscrmaddonstemp

If you hit the [OK]-button on the RecordCounter Server Config first, it will generate and save the fetches and then generate and import the RecordCounterServerConfig-solution.

In some cases it will be helpful to only save the fetches or only to import the solution.

This article describes how this can be achieved.

If the calling/called phone number is stored in Microsoft Dynamics CRM, then the number should be resolved to the corresponded CRM record. If the number does not resolve, make sure that the number is stored in the "MSCRM-ADDONS.com CTI CallInfos" entity. 

In CRM 2011, all DocumentsCorePack templates are stored in custom entities.
The name of this custom entity is DocumentsCorePack Template (ptm_mscrmaddons_dcptemplates).
Every record of this entity has the template attached as a note.