Tuesday, July 24, 2012 6:33 PM
I'm working on a plugin for dynamics crm, and appear to have wedged myself good and hard. I'm using CRM online, and have done the following:
1) Registered my plugin using the plugin registration tool that comes with the SDK.
2) Registered a step for the plugin's invocation on the Create event for an email (again, using the SDK's registration tool).
3) Attempted to create a new contact (preparing to create an email) via the web interface. When I pressed "Save and Close", an error occurred.
4) Thinking that I had perhaps botched the registration, I un-registered my plugin.
Sadly, this does not appear to have corrected the error; I am still unable to create a contact via the web interface, nor am I able to create any other entity.
After logging out of CRM online and disconnecting the plugin tool, then re-connecting, the plugin is not shown as present, but the problem still occurs. Repeatedly logging out and back in of the web interface also doesn't seem to help.
The text of the error log is below. Any thoughts on how to straighten this out?
Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=184.108.40.206, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: An error occurred. Contact a system administrator or refer to the Microsoft Dynamics CRM SDK troubleshooting guide.Detail:
<OrganizationServiceFault xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/xrm/2011/Contracts">
<d2p1:value xmlns:d4p1="http://www.w3.org/2001/XMLSchema" i:type="d4p1:string">0</d2p1:value>
<Message>An error occurred. Contact a system administrator or refer to the Microsoft Dynamics CRM SDK troubleshooting guide.</Message>
<InnerFault i:nil="true" />
[ef4cba3f-b1d5-e111-8c41-78e3b5108e61: ActivityFeeds.Plugins.ActivityClose: Create of any Entity]
Tuesday, July 24, 2012 8:25 PMAnswerer
The last part of the error mentions Activity Feeds. You could try deleting the activity feeds solution to see if that helps. You can always download and import the activity feeds solution again afterwards. The Activity Feeds solution is installed by default for CRMOnline.
Failing that, you need to raise a Microsoft support ticket.
Microsoft Certified Technology Specialist (CRM) GAP Consulting Ltd Microsoft Community Contributor Award 2011
Wednesday, July 25, 2012 2:41 PM
A thoroughly plausible idea. Unfortunately, I'm unable to report on whether it works or not, because CRM online won't let me unregister the Activity Feeds solution. *sigh*.
Off to Microsoft support.
Thursday, August 02, 2012 2:46 PM
Hi there John,
Same thing just happened to me! I registered a plugin and all of a sudden this error started showing up with exactly the same message.
Did you get any feedback yet?
Thursday, August 02, 2012 8:50 PM
I managed to figure out what happened. I still don't know why it happended, since it seems to be some automatic process by the Activity Feed solution that messed things up.
First of all, you need to go to your solution and deactivate the "new ActivityFeeds.Plugins.ActivityClose: Create of any Entity" that was added by the Activity Feeds solution.
What I suspect, is that during the Plugin registration, something probably went wrong because a new step was added to the ActivityClose plugin of the Activity Feeds but I suspect it didn't complete correctly and then .. BANG. This message would fire on EACH creation of every single entity.
- Proposed As Answer by Paulo Alexandre Sebastião Thursday, August 02, 2012 8:50 PM
Friday, August 03, 2012 9:17 AMIn the activity feeds Configuration & Rules deactivate all the process related to the new entity.
Friday, August 03, 2012 9:52 AM
That isn't enough. Tried that too. Only when deactivated the SDK.Message for the event did it work.
Best Regards, Paulo Sebastião
Wednesday, August 15, 2012 6:13 AM
I got the same issue by interacting with the PluginRegistrationTool. After I have disabled the step "new ActivityFeeds.Plugins.ActivityClose: Create of any Entity", our CRM Online @ Office 365 came back working. Thanks for your posting.