Microsoft Dynamics CRM (Archived)

Is there any way to identify which plugin failed?

(0) Share

Report

Posted on by Seamus

1,577

Hello,

We have a c# console app which imports contacts into CRM (2013 on-premise)

We occasionally/randomly get the following error (caught exception.message)

An error occured while processing this request. inner exception: System.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]: The plug-in execution failed because no Sandbox Worker processes are currently available. Please try again.
System.ServiceModel.CommunicationException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #08BA0CE4 (Fault Detail is equal to Microsoft.Xrm.Sdk.OrganizationServiceFault).

My question is - in order to start troubleshooting....is there any way within exception handling to actually identify which specific plugin the error relates to?

Thanks for any advice,

- Seamus

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (2)

David Jennaway 14,065 on at

Like (0)

Report

As a first step I'd enabled tracing (see https://support.microsoft.com/en-us/help/907490/how-to-enable-tracing-in-microsoft-dynamics-crm) . This will give more information on the trace leading to the error.

However, this error is more a lack of capacity, and may well not be specific to any one plugin

Was this reply helpful? Yes No
Suggested answer

Sreevalli 3,256 on at

Like (0)

Report

Hi,

Try to create a contact manually with the exact same data which leading to error. That should throw plugin error with more details.

Was this reply helpful? Yes No
Seamus 1,577 on at

Like (0)

Report

Thanks David - yes I can do that but the trace output is always a bit overwhelming and like finding a needle in a haystack. When you say a "lack of capacity" what do you mean?

Was this reply helpful? Yes No
Seamus 1,577 on at

Like (0)

Report

Thanks Sreevalli for your suggestion. The error is random and does not seem to be data-related - i.e it won't fail consistently on the same record.

Was this reply helpful? Yes No
Suggested answer

Sreevalli 3,256 on at

Like (1)

Report

It sound like sandbox service/port error, not specific to any plugin. I found this verified post to RC- community.dynamics.com/.../241328

Was this reply helpful? Yes No
Verified answer

Kokulan 18,054 on at

Like (1)

Report

Hi Seamus,

I know the when you enable trace, it logs a lot but i found the trace reader very useful to find the actual errors.

you can filter just to the errors and easily find the actual error message

archive.codeplex.com

To identify your steps, you could use the ITracingService to write to trace

Since you are on-prem, you can take advantage of the remote debugging feature to find out exactly which line fails

https://community.dynamics.com/crm/b/zhongchenzhoustipstricksandportaldevelopment/archive/2012/05/16/dynamics-crm-remote-debugging-step-by-step

Hope this helps

Was this reply helpful? Yes No
Verified answer

David Jennaway 14,065 on at

Like (0)

Report

Re 'lack of capacity', this could be a lack of memory, as that could limited the number of sandbox worker processes that CRM runs. Or it could be CPU or network (if any plugins make external calls), if that causes plugins to run slowly.

Re reading the trace, the tracer reader as above is one option, or if you just search for the specific error message, you'll see the stack trace that caused it (though this may or may not include the plugin information).

I doubt that debugging the plugin will work, as the issue is there is not enough to start the plugin.

This issue only relates to plugins that run in isolation mode. As you have CRM OnPremise, you re-register the plugin assemblies outside of the sandbox. You do this as a diagnostic to selectively move plugins out of the sandbox and see if the error stops (though this may not be a guarantee, as you also reduce the overall load on the sandbox), or as a permanent solution

Was this reply helpful? Yes No
Seamus 1,577 on at

Like (0)

Report

Having looked at the trace logs I am getting (amongst other things) a Principal user (Id=xxxxxxxxxxxxxxxxxxxx, type=8) is missing prvReadadx..... - but the trouble/weird thing is is that the Principal User guid specified in the error message does not exist in the systemuserbase (or Teambase)!???

Was this reply helpful? Yes No