- Blog


This blog is deprecated since July 2020.The articles below are no longer maintained and might contain outdated information. 
You can find the most acutal and relevenat information in our Knowledge Base at Blog


Hello and welcome to our blog! What can we do for you? Are you looking for further technical information or step-by-step instructions to our products? Or would you like to read the latest news on mscrm-addons? Please feel free to browse our blog for detailed information and to share our posts!

How to enable debugging for DocumentsCorePack Server Based (ON PREMISE/IFD)

Please note: This article applies to 

DocumentsCorePack ServerBased Document Generation & Processing
for Microsoft CRM 2013, 2015 
and Microsoft CRM 2015/2016


(Click here for information on debugging in DocumentsCorePack Online) 


This article describes two different possibilities to activate debugging for DocumentsCorePack:

Solution 1: Activate debugging by using the AutoMerge Configuration (recommended)

Solution 2: Activate debugging manually via Settingskeys

Furthermore, it provides you with information on how to access the logfiles

Solution 1: How to enable debugging using the AutoMerge Configuration 

Step 1
Open your CRM and navigate to Settings > Solutions

Example for Microsoft Dynamics CRM 2015 and lower

 Figure 1: Microsoft Dynamics CRM 2015 and lower

Example for Microsoft Dynamics CRM 2015/2016 and higher:

Figure 2: Microsoft Dynamics CRM 2015/2016 and higher

Step 2
With a double-click on the AutoMergeServerCore-solution...
Figure 3: All solutions > AutoMerge Core Solution

Open the AutoMerge configuration window: 
Figure 4: AutoMerge Config

Step 3

Check Activate Debugging and Active File Debugging and click on the [Save]-button. Now debugging is activated.

Step 4
Please reproduce the error and enter the logfile

Solution 2: 
How to enable debugging manually via Settingskeys      

Step 1
Navigate to Settings and select Products.
Figure 5: Select products

Step 2
In the next window, double-click on AutoMerge.
Figure 6: Active Products

Step 3
This action will open the AutoMerge SettingsKey. Look for debugging and double-click on it.
Figure 7: AutoMerge debug 

Step 4
This action will open the debug SettingsKey. Set the KeyValue on true (highlighted in yellow)
and click on the icon in the right corner at the bottom of the window (highlighted as well in yellow) in order to save your settings.
Figure 8: debug SettingsKey

Step 5
You will also have to activate the file-debugging. Therefore, click on filedebugging in the 
AutoMerge Settingskey and apply Step 4 also to filedebugging
Figure 9: filedebugging SettingsKey

Debug and filedebugging are now active. The log-files will be saved in the log-folder in your AutoMerge installation folder.
Please send the files in the log-folder with an error description to our support address (

How to access the logfiles     
Navigate to the installation-path of AutoMerge and send the files in the log-folder with an error description to our support address (

Example how the path could look like:

C:\Program Files (x86)\PTM EDV-Systeme GmbH\AutoMerge for Microsoft CRM 2013\log

Figure 10: Example path I

Figure 11: Example path II

Figure 12: Example path III

Figure 13: Example path IV


How to activate local DCP service debugging

Please note: If you have a DocumentsCorePack service issue, please activate Debugging this way:

Go to the start-pane and look for the DocumentsCorePack ServiceManagement. 
In the so opened window, you have the possibility to activate debugging, like you can see highlighted in yellow below. 
Please note: The DocumentsCorePack service has to be stopped first. 

Figure 14: Activate DCP service debugging

Once activated, proceed like above described. 

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to

Comments are closed.