Event ID 17203 Invalid Trace Directory

(0) Share

Report

Posted on by Community Member

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

I have the same question (0)

All responses (23)

Answers (0)

Suggested answer

Karsten Wirl 4,477 on at

Like (0)

Report

Hello Neerja.

We have faced same issue.

You must set the tracing folder via PowerShell and add two registry keys...

Without the second key, the error will still occur in your Event History!

Kind regards,

Karsten

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hey Karsten,

i have already set the tracing folder via powershell, but haven't set the registry key. which location we need to add it? is it HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\MSCRM

Was this reply helpful? Yes No
Suggested answer

Karsten Wirl 4,477 on at

Like (0)

Report

Hello Neeraj.

Correct, that's the folder.

Kind regards,

Karsten

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report

But i am not sure how this will work. as per support.microsoft.com/.../how-to-enable-tracing-in-microsoft-dynamics-crm, these are valid upto CRM 2013. Are you sure it worked for you and you are using CMR 2016, because it didn't worked for us.

I restarted the Microsoft SQL Server Reporting Services as well, but it keeps logging this message in event viewer.

Was this reply helpful? Yes No
Karsten Wirl 4,477 on at

Like (0)

Report

Hi Neeraj.

Yes, I'm sure that we use MS CRM 2016 and that this solution worked for us.

Please restart the server... Some changes in the registry only take effect after a reboot.

Kind regards,

Karsten

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

ok, will try restarting the server. Thanks for quick reply.

Was this reply helpful? Yes No
Karsten Wirl 4,477 on at

Like (0)

Report

Good luck!

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Didn't worked for me. This is what i have done so far

Added both the registry key 'Traceenabled - set to 0' and 'TraceDirectory - set to valid path' at HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\MSCRM. Also have already set these from powershell.

Restarted the SQL Reporting services and server as well.

But can still see the same events getting logged.

Was this reply helpful? Yes No
Karsten Wirl 4,477 on at

Like (0)

Report

Hi there.

Okay, next try... have you checked via PowerShell, whether the tracing folder is set?

Does the tracing folder exist?

Kind regards,

Karsten

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

yes, it exists . i even verified in dbo.DeploymentProperties in MSCRM_Config db, there too the entries are correct.

Was this reply helpful? Yes No