If you have some problems with Dynamics CRM On-premise you are able to enable tracing with PowerShell. In my case, I needed to get debug information on why my solution import is failing when I’m going to move it to a new organization.
Open the powershell prompt and use the Add-PSSnapin command shown in 1). Thereby, You can list the trace setting with the command shown in 2). Before you start the tracing, you show determine the timeline for when the error occurs and just enble it as close as the error as possible. Run the command in 3) to start the tracing. You should stop the tracing immediately after the error has occured. Use command in 4) to stop the tracing.
# 1) add Add-PSSnapin Microsoft.Crm.PowerShell # 2) get crm trace settings Get-CrmSetting TraceSettings # 3) enable tracing $Setting = Get-CrmSetting TraceSettings $Setting.Enabled = $True $Setting.CallStack=$True $Setting.Categories="*:Verbose" $Setting.Directory="C:\temp\crmtrace" Set-CrmSetting $setting # 4) disbale tracing $Setting = Get-CrmSetting TraceSettings $setting.Enabled = $False Set-CrmSetting $setting
When you have tons of log file, the trace tool CRM Trace reader is nice to use for searing and filtering.