locked
4.0 trace registry settings not respected RRS feed

  • Question

  •  

    I have an odd issue I can't figure out.

    The trace on a 3.0 -> 4.0 upgrade is not respecting my registry settings.

    I set the traceenabled=1, tracedirectory=c:\mytracefolder and restarted iis and the async services.

    The trace still goes to the default C:\Program Files\Microsoft Dynamics CRM\Trace

    I looked in the DeploymentProperties table in MSCRM_CONFIG and the database values to the corresponding registry settings is completely different, trace = false and tracedirectory = c:\crmdrop\logs.

    When i change the database values to what it should be, regardless of what the registry settings are, it logs to the correct location.

    Are all registry setting depreciated now?

    What am I missing here? Any help would be appreciated.

    Thursday, September 25, 2008 1:20 PM

Answers