Looks like another piece of CRM team awesomeness.
The Tracing directory should be:
C:\Program Files\Microsoft Dynamics CRM\Trace
But some update somewhere changes it to:
c:\crmdrop\logs
That’s not very helpful.
I initially tried to change the trace directory back to the right place using CRM PowerShell, but that failed with authentication errors (that i have also posted on here – http://paulobrien.co.nz/2018/03/07/get-crmsetting-powershell-the-caller-was-not-authenticated-by-the-service-the-request-for-security-token-could-not-be-satisfied-because-authentication-failed/).
This is the guide i tried using the powershell method – makes sense, if powershell crm wasn’t broken as well.
How to fix ‘Invalid Trace Directory’ errors
So ended up changing in the CRM Database and registry:
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM] "TraceDirectory"="C:\\Program Files\\Microsoft Dynamics CRM\\Trace" "TraceEnabled"=dword:00000001
And in the MSCRM_CONFIG database:
SELECT NVarCharColumn FROM [MSCRM_CONFIG].[dbo].[ServerSettingsProperties] where ColumnName = 'TraceDirectory' update [MSCRM_CONFIG].[dbo].[ServerSettingsProperties] set NVarCharColumn = 'C:\Program Files\Microsoft Dynamics CRM\Trace' where ColumnName = 'TraceDirectory'