Microsoft Dynamics CRM (Archived)

Plugin Not firing also not giving any error

(0) Share

Report

Posted on by windyMill

437

Hi guys ,

I have written a plugin on "oppurtunity" but it is not firing at all so I am not getting what problem might be.

I have done following things --

1) Added a custoum field in oppurtunity but it schema name got created like new_myfieldname , it not taken cog_myfieldname

2) I deactivated all workflow on oppurtunity.

3) I am firing it on update of a description field of oppurtunity entitiy.

4) It is a synchronous plugin.

5) Can I debug the plugin for which there is no any error or no error log file.

Please suggest regarding this.

*This post is locked for comments

I have the same question (0)

All responses (11)

Answers (1)

Suggested answer

Divyang Shukla 355 on at

Like (0)

Report

Please refer https://msdn.microsoft.com/en-us/library/gg328574.aspx to debug plugin.

Was this reply helpful? Yes No
Suggested answer

tw0sh3ds 5,600 on at

Like (0)

Report

If this is on-premise deployment simply attach your debugger to w3sp process (or sandbox process if you have your plugins in a sandbox)

Was this reply helpful? Yes No
windyMill 437 on at

Like (0)

Report

To attach with process I also need error log file. I m not getting any thing.

Was this reply helpful? Yes No
Suggested answer

Rajkumar Rajaraman on at

Like (0)

Report

Use Plugin Profiler. Refer this:

community.dynamics.com/.../how-to-debug-plugins-using-profiler

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Hi WindyMill,

Sometimes restarting the Async services on the server helps for plugins that don't seem to have registered.

other than that try throwing an invalidpluginexception in the first line in your plugin.

Just to narrow down that its not escaping the plugin somewhere you don't expect.

Hope this helps,

David Levins

Was this reply helpful? Yes No
Gopalan Bhuvanesh 11,401 on at

Like (0)

Report

Would you please send me the code, if possible, so that I can find out the bug.

Was this reply helpful? Yes No
Verified answer

Patrick O'Gorman 166 on at

Like (0)

Report

Hi windyMill, there are a lot of correct answers in this thread, but I thought I would add a bit more, starting with a question. Maybe I missed something but where is this being deployed and how are you registering it, e.g. locally, in code, with the plugin reg tool? Similarly, and this may be obvious by your answer to the first question, but what are you using to debug this? Are you able to attach to the w3wp process and actually set a breakpoint?

You said this is a sync plugin. If being deployed on-prem, you might want to try an iisreset after deploying the new plugin, assuming you are doing this on a dedicated box.

Good luck, keep us posted.

Was this reply helpful? Yes No
Patrick O'Gorman 166 on at

Like (0)

Report

Why do you need the error log file to attach to the process? The process is the IIS worker process for a sync plugin, you should be able to attach to it. Whether or not the updated DLL for the plugin is being deployed is another story (see my other comment).

Was this reply helpful? Yes No
Hameed Hussain 250 on at

Like (0)

Report

If you have registered the plugin and the step, the plugin will fire. Synchronous plugin throws error in the dialog box, but if you fail provide a catch statement, it won't.

Do this:

1. In the plugin registration tool, install the profiler

2. On the plugin step, right click and select 'start profiling'.

3. Trigger the action (update your description field, and click save).

4. A dialog pops up, download the Error file.

5. Stop profiling on the step.

6. Add a break point in your code, and attach the plugin code to the PluginRegistration.exe (under Debug->Attach to Process in VS)

7. On the plugin registration tool, click on Debug, upload your plugin dll, and your downloaded file

8. The plugin should hit the debug point now.

If this doesn't work, unregister and register the plugin again.

Was this reply helpful? Yes No
Suggested answer

SCV 1,004 on at

Like (0)

Report

Hi,

For the point #2 reason it did not take your prefix is that you have not created the field within your solution. It has been created in side the default solution. You should have opened your solution and then created the field there. Then it would have created your field name as cog_myfieldname assuming cog is the prefix you have given in the publisher.

To see what's happening in the plugin you can enable and use tracing which is but easier than debugging. Check here:

http://sacconsulting.blogspot.com.au/2017/03/tracing-in-plugins-and-custom-workflow.html

Thanks

Was this reply helpful? Yes No