web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

MSCRMTracing - Tracing directory is null + high number of sandbox worker processes

(0) ShareShare
ReportReport
Posted on by 4,930

Hi,

since upgrading to SP2 UR2 8.2.2.112 we constantly receive errors from the event source MSCRMTracing on our backend and frontend servers, telling that the trace directory is null.

Additionally a huge number of sandbox worker processes is being created due to that.

I found lots of threads about that and some blog articles, like:

https://blog.qualtechsoftware.com/high-number-of-sandbox-worker-processes-dynamics-365/

But none of them helped me to fix that issue.

I checked that:

- Trace directory is set via Powershell

- Trace directory is set in registry

- Trace directory is set in mscrm_config db

I restarted all the servers. I tried with tracing activated/deactivated ...

But the error does not disappear.

Any ideas how to fix that issue?

thx a lot

Thomas

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Ben Thompson Profile Picture
    6,350 on at

    Thomas,

    Just because the trace directory is listed doesn't mean that it actually exists or that the system account that is writing to the trace directory can see it / write to it.

    Check the permissions on the trace directory and make sure that the service account the sandbox worker processes use have full execute permissions on that folder (and its parent directories for safe keeping) across all systems.

  • tpeschat Profile Picture
    4,930 on at

    Hi Ben,

    I already checked, if the directory exists and if the service accounts running the various CRM services have permissions on that folder. And all the service account have full control rights on that folder.

    Any other ideas?

    thx Thomas

  • Suggested answer
    Ben Thompson Profile Picture
    6,350 on at

    Did you include the permissions of parent folders? It's no good giving the system account access to d:\folder1\trace say if the system account can't read or access the parent d:\ and d:\folder directories.

    Apart from if these are standard Windows Servers that aren't running any custom software beyond the software that comes with Windows / SQL / Dynamics 365 - I suspect you'll need to talk to Microsoft.

  • tpeschat Profile Picture
    4,930 on at

    No I only set the permission to the folder D:\APPL\MSCRM 2015\TRACE.

    But it has been working like that with CRM 2015 and 2016 SP1 without any issues.

    It is normal windows 2012 r2 servers where only ms dynamics is deployed... 2 front end and 2 backend.

    Will give it a try to extend the permissions to the parent folders.

    Otherwise I will open a case tomorrow.

    Cheers Thomas

  • tpeschat Profile Picture
    4,930 on at

    Extending the folder permissions up to D: and rebooting the server did not help :(

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans