High number of sandbox worker processes

(1) Share

Report

Posted on by Xavier Villafuerte

352

Hi, I just installed a Dynamics 365 On Premise with separated roles, update 2.1 running on top of Windows Server 2016 and SQL Server 2014. The setup process finished fine but I noticed some sluggish performance in the whole CRM after the setup. I checked the backend server, where the SQL and Async/Sandbox services are running and I found almost 60 instances of the sandbox worker process running in memory (no users were using the CRM at that time). I rebooted the server but those process are still there. I would appreciate any advise on why this is happening and if there is some know performance tweak that need to be implemented in order to reduce the number of those processes.

Xavier

*This post is locked for comments

I have the same question (0)

All responses (21)

Answers (0)

Tony Amaral 190 on at

Like (0)

Report

RE: High number of sandbox worker processes

Hi Xavier, have you got an answer to this? I've installed the Dynamics 365 update a month ago and everything has been working fine until today after installing the latest windows updates. Now I get several instances of the sandbox service being spawned and the following error being logged:

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)

I have confirmed that everything related to Tracing is setup correctly including the tracing folder.

Thanks

Was this reply helpful? Yes No
Xavier Villafuerte 352 on at

Like (0)

Report

RE: High number of sandbox worker processes

Hi Antonio, no, I still have no answers on this. My scenario is the same regarding the updates and messages in the event viewer.

Xavier

Was this reply helpful? Yes No
Tony Amaral 190 on at

Like (0)

Report

RE: High number of sandbox worker processes

Hi Xavier, thanks for checking in.

This customer has a few plugins running in the sandbox. I thought maybe these plugins haven't been updated for Dynamics 365 and might be causing the problem but that's not the case. I disabled all the sandbox plugins and the sandbox service is still doing the same.

Tony

Was this reply helpful? Yes No
Tony Amaral 190 on at

Like (0)

Report

RE: High number of sandbox worker processes

Someone else with the same problem

social.microsoft.com/.../event-id-17203-invalid-trace-directory

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: High number of sandbox worker processes

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

Was this reply helpful? Yes No
Xavier Villafuerte 352 on at

Like (0)

Report

RE: High number of sandbox worker processes

Thanks Roman. Have you found any workaround? I have received the same report for other couple of customers and I am almost sure this is some kind of bug.

Was this reply helpful? Yes No
Tony Amaral 190 on at

Like (0)

Report

RE: High number of sandbox worker processes

I have a ticket open in the partner forum. They have been researching the problem for at least 3 days now. I will update this thread once hear from them with the findings.

Was this reply helpful? Yes No
Xavier Villafuerte 352 on at

Like (0)

Report

RE: High number of sandbox worker processes

Thanks. As an extra information regarding this case, running a netstat -ano command on the server where the sandbox service is installed, shows that each sandbox worker process has created a separated connection to 127.0.0.1 on a range of ports starting on 8000. As far as I know only port 808 is required for communication associated to the Sandbox Service.

Crossing fingers to get any clue about this issue soon.

Was this reply helpful? Yes No
joman 617 on at

Like (0)

Report

RE: High number of sandbox worker processes

Hi!

I have same issue:

community.dynamics.com/.../235861

All my attempts to find out, what is happens fail.

[quote]Someone else with the same problem

social.microsoft.com/.../event-id-17203-invalid-trace-directory[/quote]

This is not the same problem. This errors remove easy.

Was this reply helpful? Yes No
joman 617 on at

Like (0)

Report

RE: High number of sandbox worker processes

[quote]Hi Xavier, have you got an answer to this? I've installed the Dynamics 365 update a month ago and everything has been working fine until today after installing the latest windows updates. Now I get several instances of the sandbox service being spawned and the following error being logged:

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)

I have confirmed that everything related to Tracing is setup correctly including the tracing folder.

Thanks[/quote]

This mistake is easy to remove:

You need run "regedit" on a server. Then go

"HKLM\Software\Microsoft\MSCRM"

There should be keys:

TraceDirectory String "Path_ToTraceLogs"

TraceEnabled DWORD 1

Was this reply helpful? Yes No