Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Event ID 17203 Invalid Trace Directory

(0) ShareShare
ReportReport
Posted on by Microsoft Employee

We have CRM 2016(8.1.1.1005) installed on premise. On the server, we keep on receiving below warning message

MSCRMTracing - 

Invalid Trace Directory. Additional Info:[ Invalid Trace Directory (Reporting Process:Trace Diretory is Null. TraceSettings: {Filename:  ,FileCountSuffix:1 ,TraceFileSize:10485760 ,TraceDirectory: ,TracingCallStack:No ,IsTracingOff:Yes ,LoadState:LoadSuccessfulUnreported ,RefreshTraceInt:-1 ,SiteWideRefreshTraceInt:-1 ,RegistryRefreshTraceInt:-1 ,Precedence:Default} ] , AppDomain:w3wp)

Event ID: 17203.
Log Name: Application.
Type: 1.

Right now the tracing is disabled on server and TraceDirectory path is also existing on the server.

I have already applied fixes mentioned on https://spandcrm.com/2017/04/17/how-to-fix-invalid-trace-directory-errors/

This message has been logged by many users on Microsoft network, but didn't found solution for it. please check

https://social.microsoft.com/Forums/en-US/8e1ac56e-aca6-485c-86d2-a97b3a19d8db/event-id-17203-invalid-trace-directory?forum=crm

https://partnersupport.microsoft.com/en-us/par_msdyn/forum/par_dyn365p/high-number-of-sandbox-worker-processes/07e3bbc3-c614-4fe9-8f5d-45fc721c038c?auth=1


Do anybody have any clue on why we keep on receiving the warning message in event viewer?


*This post is locked for comments

  • ALTOSHAAM Profile Picture
    ALTOSHAAM 180 on at
    RE: Event ID 17203 Invalid Trace Directory

    What I've found so far.

    If tracing is enabled (by registry key or by PS - makes no difference) - traces are correctly written to specified folder (default or custom) and no error is logged into event log.

    But, if tracing is switched off in both (registry and Config DB) - this error is logged.

    Definitely some bug in code which parses tracing settings.

    D365 on-premise, 9.0.8.9

  • ALTOSHAAM Profile Picture
    ALTOSHAAM 180 on at
    RE: Event ID 17203 Invalid Trace Directory

    The same thing for the latest On-Premise, 9.0.6.9. Tracing settings are correctly set in Config DB. Haven't tried the registry way yet...

    But the fact that software product having over 10 years of history and released 9th major version, still have such annoying issues like trace settings load or encryption key renewals, that are reported during years, but with no fixes... That is really frustrating =(

  • Suggested answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Event ID 17203 Invalid Trace Directory

    The same problem, but solved

    - Setting the trace settings using the powershell

    Add-PSSnapin Microsoft.Crm.PowerShell

    Get-CrmSetting TraceSettings

    $setting=Get-CrmSetting TraceSettings

    $setting.Directory=”D:\DCRM\Trace”

    $setting.Enabled=”True”

    Set-CrmSetting $setting

    Get-CrmSetting TraceSettings

    can fix AppDomain:w3wp,CrmAsyncService etc

    but  can not fix Microsoft.Crm.Sandbox.WorkerProcess

    - Setting the trace settings using the Windows Registry

    TraceDirectory   D:\DCRM\Trace    REG_SZ

    TraceEnabled   0x00000000 (1) REG_DWORD

    can fix AppDomain:Microsoft.Crm.Sandbox.WorkerProcess

    it Effective for me,

    hope can help you

  • Suggested answer
    Kokulan Profile Picture
    Kokulan 18,052 on at
    RE: Event ID 17203 Invalid Trace Directory

    Could you the following tool to set directory and enable trace and see if that fixes your issue?

    ScreenClip-_5B00_155_5D00_.png

    https://archive.codeplex.com/?p=crmdiagtool2011

    Hope this helps

  • Boolean1 Profile Picture
    Boolean1 60 on at
    RE: Event ID 17203 Invalid Trace Directory

    I'm seeing the same thing, except as an error, on 8.1.1.1100.

    Tracing is disabled.

    Is this just a nuisance error?

  • RE: Event ID 17203 Invalid Trace Directory

    We are still facing the same issue with Microsoft Dynamics 365 for Customer Engagement (9.0) On-Premise. Any updates or solutions?

    We tried all the following, but nothing work.

    - Setting the trace settings using the powershell 

    - Setting the trace settings using the Windows Registry 

    - Restarting the server

    Evern Log:

    Invalid Trace Directory. Additional Info:[ Invalid Trace Directory (Reporting Process:Trace Diretory is Null. TraceSettings: {Filename:  ,FileCountSuffix:1 ,TraceFileSize:10485760 ,TraceDirectory: ,TracingCallStack:No ,IsTracingOff:Yes ,LoadState:LoadSuccessfulUnreported ,RefreshTraceInt:-1 ,SiteWideRefreshTraceInt:-1 ,RegistryRefreshTraceInt:-1 ,Precedence:Default} ] , AppDomain:Microsoft.Crm.Sandbox.WorkerProcess)

  • Suggested answer
    indlad Profile Picture
    indlad 450 on at
    RE: Event ID 17203 Invalid Trace Directory

    Hi,

    Interesting observation is that the DIRECTORY was Mis-spelled (

    Invalid Trace Directory. Additional Info:[ Invalid Trace Directory (Reporting Process:Trace Diretory is Null. TraceSettings: {Filename: ,FileCountSuffix:1 ,TraceFileSize:10485760 ,TraceDirectory: ,TracingCallStack:No ,IsTracingOff:Yes ,LoadState:LoadSuccessfulUnreported ,RefreshTraceInt:-1 ,SiteWideRefreshTraceInt:-1 ,RegistryRefreshTraceInt:-1 ,Precedence:Default} ] , AppDomain:w3wp)

    So even if you set the Trace Directory using Powershell or in the Registry this event continue to appear in the Event logs i believe.

    Any thoughts?

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Event ID 17203 Invalid Trace Directory

    I know this thread is a bit old but I am having the same problem.  I cannot get the PowerShell Add-PSSnapin Microsoft.Crm.PowerShell to run on my desktop.  I have looked and looked and cannot seem to find the right module package to import.  Can you tell me where they are so I can download and run on a Windows 10 Desktop?

    TIA,

    Jim

  • Suggested answer
    Johannes Leppert Profile Picture
    Johannes Leppert 70 on at
    RE: Event ID 17203 Invalid Trace Directory

    You can change the default trace directory of CRM via PowerShell:

    Add-PSSnapin Microsoft.Crm.PowerShell

    Get-CrmSetting TraceSettings

    $setting=Get-CrmSetting TraceSettings

    $setting.Directory="C:\Program Files\Microsoft Dynamics CRM\Trace"

    Set-CrmSetting $setting

    Get-CrmSetting TraceSettings

  • Karsten Wirl Profile Picture
    Karsten Wirl 4,477 on at
    RE: Event ID 17203 Invalid Trace Directory

    Okay, this article describes same Event Viewer error, but the reason for the problem was really strange...

    community.dynamics.com/.../235366

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Vahid Ghafarpour – Community Spotlight

We are excited to recognize Vahid Ghafarpour as our February 2025 Community…

Tip: Become a User Group leader!

Join the ranks of valued community UG leaders

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,494 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,305 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans