Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
How to enable tracing in Microsoft Dynamics CRM
Article ID: 907490 - View products that this article applies to.
This article describes how to enable tracing in Microsoft Dynamics CRM.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756Microsoft Dynamics CRM lets you create trace files that monitor the actions that are performed by Microsoft CRM. Trace files are helpful when you have to troubleshoot error messages or other issues in Microsoft CRM.
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
You can create unmanaged trace files and managed trace files. The information in the unmanaged and managed trace files is determined by required and optional registry entries that you create manually. You create these registry entries on the Microsoft CRM server or on the computer that is running the Microsoft CRM client for Microsoft Office Outlook after you install Microsoft CRM or the Microsoft CRM client for Outlook.
In Microsoft Dynamics CRM 2011, you can also enable tracing by using Windows PowerShell applets. See the "Enable trace settings through Windows PowerShell" section for more information.
Required registry entriesThe following are the required registry entries. For more information about the location of these registry entries, see the "Registry entry locations" section.
Collapse this tableExpand this table
Optional registry entriesThe following are the optional registry entries.
If you do not create the optional registry entries, the default data values are used. For more information about the default data values, see the "Default data values for optional registry entries" section. If you create the registry entries but do not specify data values for the registry entries, tracing will not work.
Collapse this tableExpand this table
Enable trace settings through Windows PowerShellNote These changes made in Windows PowerShell do not update the Registry. These changes update the DeploymentProperties and ServerSettingsProperties tables in the MSCRM_CONFIG database.
Register the cmdlets
To obtain a list of the current settings, type the following command:
Get-CrmSetting TraceSettingsThe output will resemble the following:
CallStack : TrueCategories : *:ErrorDirectory : c:\crmdrop\logsEnabled : FalseFileSize : 10ExtensionData : System.Runtime.Serialization.ExtensionDataObject
Set the trace settings
$setting.Enabled=$FalseNote The format of the example commands for each value should be as follows:
$setting.Enabled=$EnabledValue ($True or $False)
$setting.CallStack=$StackValue ($True or $False)
$setting.Directory="C:\Program Files\Microsoft Dynamics CRM\Trace"
The output will resemble the following:
CallStack : TrueCategories : *:ErrorDirectory : c:\crmdrop\logsEnabled : TrueFileSize : 10ExtensionData : System.Runtime.Serialization.ExtensionDataObject
Microsoft Dynamics CRM 4.0 and Microsoft Dynamics CRM 2011 trace log file locationsWhen you create a trace in Microsoft Dynamics CRM 4.0 or Microsoft Dynamics CRM 2011, the TraceDirectory registry key is ignored. For tracing on the Microsoft Dynamics CRM 4.0 server and the Microsoft Dynamics CRM 2011 server, the trace log file is created in the following folder:
Drive:\Program Files\Microsoft Dynamics CRM\TraceFor tracing on the Microsoft Dynamics CRM 4.0 client for Microsoft Office Outlook and for tracing on Microsoft Dynamics CRM 4.0 Data Migration Manager, the trace log file is created in the following folder if you do not have Update Rollup 7 or a later cumulative update:
DriveName:\Documents and Settings\ InstallingUser \Application Data\Microsoft\MSCRM\Traces
For tracing on the Microsoft Dynamics CRM 2011 client for Microsoft Office Outlook and the Microsoft Dynamics CRM 4.0 client for Microsoft Office Outlook and for tracing on Microsoft Dynamics CRM 4.0 Data Migration Manager, the trace log file is created in the following folder if you have Update Rollup 7 or a later cumulative update installed:
DriveName:\ InstallingUser \Local Settings\Application Data\Microsoft\MSCRM\Traces
Registry entry locationsThe Microsoft CRM server tracing registry entries are located in the following registry subkey:
The Microsoft CRM client for Outlook tracing registry entries are located in the following registry subkey:
The Microsoft Dynamics CRM SSRS Data Connector tracing registry entries are located in the following registry subkey:
The Microsoft CRM Data Migration Manager tracing registry entries are located in the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\DATA MIGRATION WIZARD
Complete list of category values for the TraceCategories registry entry
Microsoft Dynamics CRM 2011
Trace level values
Complete list of valid trace level values for TraceLevel
Sample category and trace level combinations
Default data values for optional registry values
Microsoft Dynamics CRM E-mail Router serviceYou can update the Microsoft Dynamics CRM E-mail Router service to enable tracing. To do this, you must modify the registry and XML service configurations.
To enable verbose operations log level, you must manually update the configuration by updating the registry. To do this, follow these steps:
How to enable scheduled tracing
How to disable scheduled tracing