“There is no active transaction. This error is usually caused by custom plug-ins that ignore errors from service calls and continue processing” Error

“There is no active transaction. This error is usually caused by custom plug-ins that ignore errors from service calls and continue processing” is a frequent error generated while attempting to create a new record (Account or Contact in most cases).

This is a bug that you can fix by deactivating the “ActivityFeeds plugin” regarding the entity that generated the error.

First navigate to Customizations then open Sdk Message Processing Steps, select the right plugin and click deactivate

custo

plugin-error

 

The example given here is the Contact entity. You can follow the same process if you have a similar issue with other entities.

 

 

 

.

 

2 thoughts on ““There is no active transaction. This error is usually caused by custom plug-ins that ignore errors from service calls and continue processing” Error

  1. Thanks its works for me!!

    But i didn’t understand why its happening in only one organisation.
    I have tested on same server for different organisation and same user privileges its working fine without deactivation activity feed plugin.

    anyone have any idea about same?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s