How to Enable Tracing in Microsoft Dynamics 365 / Dynamics CRM

Introduction

Microsoft Dynamics CRM lets you create trace files that monitor the actions performed by Microsoft Dynamics CRM. Trace files are helpful when troubleshooting error messages or other issues in Microsoft Dynamics CRM.

There are tools available to help manage tracing and log creation. This article concentrates on managing tracing using the Registry.

Warning

Changes to the registry should be completed by a system administrator.
You should only enable tracing for as long as you need. Running a trace for extended periods will affect performance.

Incorrect changes to the registry can have adverse effects on your system. We recommend you make a full back up of your systems and registry before making any changes.

Registry Locations

Here are the registry locations for each component of Microsoft Dynamics CRM that allows tracing.

Microsoft Dynamics CRM Server:
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\MSCRM

Microsoft Dynamics CRM for Outlook:
HKEY_CURRENT_USER\SOFTWARE\MICROSOFT\MSCRMClient

Microsoft Dynamics CRM for SSRS Data Connector:
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\MSCRMBidsExtensions

Required Registry Entries

Optional Registry Entries

Here are optional entries used for specific purposes. Note: Using these may result in an incomplete trace file. For a complete trace, leave these as default. Further information on option registry entries can be found on the Microsoft Knowledge base

Enabling Tracing using Windows PowerShell

It is also possible to enable and disable tracing using PowerShell.

Enable Tracing

$CrmTraceSettings = get-CrmSetting TraceSetting
$CrmTraceSettings.Enabled=$True
Set-CrmSetting $CrmTraceSettings

Disable Tracing

$CrmTraceSettings = get-CrmSetting TraceSetting
$CrmTraceSettings.Enabled=$False
Set-CrmSetting $CrmTraceSettings

Further information on the PowerShell commands available can be found on the Microsoft Knowledgebase