I recently stated getting this error message after being locked out of CRM for exceeding storage capacity. It errors out when users try to create an opportunity and/or case.
Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=126.96.36.199, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: There is no active transaction. This error is usually caused by custom plug-ins that ignore errors from service calls and continue processing.Detail: <OrganizationServiceFault xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/xrm/2011/Contracts"> <ErrorCode>-2147220911</ErrorCode> <ErrorDetails xmlns:d2p1="http://schemas.datacontract.org/2004/07/System.Collections.Generic" /> <Message>There is no active transaction. This error is usually caused by custom plug-ins that ignore errors from service calls and continue processing.</Message> <Timestamp>2014-08-26T13:28:59.3038691Z</Timestamp> <InnerFault i:nil="true" /> <TraceText i:nil="true" /></OrganizationServiceFault>
Any ideas on how to fix this?
Plugin objects are created once, and then used multiple times. So you open yourself up to race conditions if you are storing plugin context at the member level. If I have a plugin that fires for an Update of Lead X, and before it finishes, another plugin fires on Lead Y, and now the context for Lead X will be lost and any interaction with the thread processing Lead X will be processing under Lead Y.
Thanks for the explanation Daryl, makes perfect sense!
Hi Josh, were you ever able to figure this out? I'm running into the exact same issue and cannot figure why I'm unable to capture the error from the plugin in the workflow.
I've seen this with customers that have had duplicate Activity Feed solution SDK Message Processing Steps. This prevented things like completion of Activities due to the duplicate SDK Message Processing Steps. We simply deactivated the duplicate SDK Message Processing steps, which then fixed the error and allowed the activities to be completed.
I just ran in to this error today. Ours was self inflicted with field level security. Here was our solution:
If your plugin is updating or creating a field, that you have a field security profile for, then you need to ensure that the "Update" and "Create" privileges on the security profile are set to yes. If the plugin is run in the context of the current user, the team that user is on would then need to have that field security profile assigned to it.
Can you check if your users have the correct permissions on the entities which trigger the error message ?
I had the same error in the past and the read/write access were missing on the roles.
Business Applications communities