Many a times we are in need to enable tracing for On-Premise reports. Here is the way:

In Microsoft Dynamics CRM, you can create trace files that monitor the actions that are performed by Microsoft Dynamics CRM Reporting Extensions. Trace files are helpful when you have to troubleshoot error messages or other issues in Microsoft Dynamics CRM Reporting Extensions.

You can enable tracing for Microsoft Dynamics CRM Reporting Extensions in two ways:

Enable tracing using registry values

1. On the computer where you have installed Microsoft Dynamics CRM Reporting Extensions, locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\MSCRM
2. Set the following registry values:
   • TraceEnabled = 1
   • TraceDirectory = <directory path where traces will be stored>

   You can also set other row values like TraceCategories, but they already have defaults.

3. Restart Microsoft SQL Server Reporting Services.

Enable tracing using deployment properties

1. Go to the DeploymentProperties table in the Configuration Database.
2. Locate the row with the value “TraceEnabled” and set its “BitColumn” column’s value to “True”.
   Other row values like TraceCategories, TraceDirectory already have default values, but you can change these values.
   You will start seeing the traces in the directory specified in the TraceDirectory row in the DeploymentProperties table.
3. Restart Microsoft SQL Server Reporting Services.

Registry settings take precedence over deployment properties.

If there are any invalid entries in the registry, for example, and TraceDirectory does not exist, the deployment properties are used.

Source: Technet

Hope it helps!