web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / eConnect 9.0 Error Pos...
Microsoft Dynamics GP (Archived)

eConnect 9.0 Error Possibly MS DTC Configuration?

(0) ShareShare
ReportReport
Posted on by Community Member

Attempting to push POP invoice documents to Dynamics GP via eConnect 9.0 I am receiving the following error:

Version=9.0.0.0
Unique MessageId =
Error Number = -2147168246
Error Description = New transaction cannot enlist in the specified transaction coordinator.
Error Source = Microsoft OLE DB Provider for SQL Server 
Line Number=1480

It sounds like a Microsoft Distributed Transaction Coordinator configuration issue, but I've successfully verified the MS DTC configuration using DTC Ping.  I've also checked to make sure there is no firewall interference occurring.

Most notable about the error I'm getting is that the database server involved was working just fine with equivalent documents as a physical server.  The difference now is that this database server has been virtualized.  Otherwise, all of its characteristics (name, ip address, memory, etc.) are the same.  The server on which Dynamics GP and eConnect are running has not changed.  I've looked at everything I can think of.  Any suggestions from anybody out there?

TIA, John

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    Community Member on at

    Note that I mis-identified the documents of concern as POP invoices.  That should have been SOP invoices.

    John

  • Community Member Profile Picture
    Community Member on at

    Please take a look on this KB if you haven't done this already

    support.microsoft.com/.../922430

  • Community Member Profile Picture
    Community Member on at

    In pursuing Francisco's suggestion I've identified that the root issue seems to be a different message issued by the first transaction attempted:

    "The transaction has already been implicitly or explicitly committed or aborted (Exception from HRESULT: 0x8004D00E)"

    After that, all attempts to push a document through eConnect are met with the message originally mentioned in this thread.  I think those "New transaction cannot enlist in the specified transaction coordinator." messages are probably are direct consequence of this initial problem.

    Does anyone have any experience with this message?

    John

  • Verified answer
    Community Member Profile Picture
    Community Member on at

    I'm sure this is not technically the best solution, but I found that if I completely open up MS DTC security on both servers things start flowing again.  Since these servers are completely internal, I'm going to let things run as they are for now.  Here are the specific settings I have in play for both the application and the database server now (these are both virtualized Windows Server 2003 R2 sp2 machines):

    Allow Network DTC Access

    Allow Remote Clients

    Allow Remote Administration

    Allow Inbound

    Allow Outbound

    No Authentication Required

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans