eConnect for Microsoft Dynamics GP does not roll back transactions when an error occurs during the import


Data being integrated with eConnect is leaving records in Microsoft Dynamics GP tables when there is an error being returned. eConnect should be rolling back the data out of Microsoft Dynamics GP tables.


eConnect uses Microsoft Distributed Transaction Coordinator (DTC) to send the data being imported from the workstation to the SQL Server. When using Distribution Transaction Coordinator if there is an error received during the integration process then DTC will rollback the data from the Microsoft Dynamics GP tables. Now if the eConnect 10 for Microsoft Dynamics GP is set to a value other than Required under the Transaction Support tab then it will not roll back the data.


To check the Transaction Support setting perform the following steps:

  1. Locate Administrative Tools and then Component Services.

  2. Expand the eConnect 10 for Microsoft Dynamics GP.

  3. Expand the Components folder there will be a component called Microsoft.Dynamics.GP.eConnect.eConnectMethods, right-click this and then click Properties.

  4. As soon as you are in the Properties click the Transactions tab.

  5. Make sure that the Transaction Support is set to Required.

If the Transaction Support is not set to Required perform the following steps:

  1. Change the value to be required and then click OK.

  2. You are now in the Component Services window where you will be able to see the eConnect 10 for Microsoft Dynamics GP COM+ package.

  3. Right-click the eConnect 10 for Microsoft Dynamics GP COM+ package and select Shutdown.

  4. Next, right-click the eConnect 10 for Microsoft Dynamics GP COM+ package again and select Start.

  5. This process will restart the com+ package so that changes to the com+ settings will take effect.

David C
Developer Support

Comments (4)

  1. Steve Endow says:

    Thanks for the post David. That’s a pretty obscure setting!

    When troubleshooting a DTC error recently, I found a recommendation to use the "Enlist=False" parameter for the eConnect conn string to get rid of the error.

    But I subsequently read that setting Enlist = False may disable some MS DTC transaction handling mechanisms.

    Can you or the GP developers help shed some light on the impact / usage of the Enlist conn string parameter?

    Here are my two posts on the topic:

  2. Richard says:

    When eConnects return an error?

    It always show the long error list. We need to do a lot of try an error to figure what causing the error.

    The error message also bit technical for user.

    Is there any proper way display more proper error message to the user?

  3. nilotpal cho says:

    hi all,

    when we import data uging eConnect to GP,they will be in a ‘SAVE’status.

    Is it possible to import data directly into GP in ‘POST’ status??

    Because,normally user can change the data imported by eConnect and then post it,-what i need is to block the user access to the imported data.

    let me know if u have any idea.



  4. Steve Endow says:

    Hi Nilotpal,

    After transactions are imported via eConnect, there is no option in eConnect to import them as posted, or post them automatically using eConnect.

    However, you can use a third party product to automatically post the batches after they are imported.  Check out Post Master for Dynamics GP:

    Full disclosure: I now resell Post Master in North America.

    Here is a blog post that I wrote about it before I started to resell it:


    Steve Endow

    Dynamics GP Certified Trainer

    Dynamics GP Certified Professional