You’re offline. This is a read only version of the page.
285
Hey guys,
I'm new to the forums and to eConnect (version 11) for that matter. I've gotten most of my integrations to work just fine (invoices, receipts, returns, etc, both on the server and remotely), but I'm having issues dealing with customers and vendors...I'm attempting to pass to econnect more than one customer/vendor at a time since it's a business requirement for my company, and when I attempt to run the integration on the server it works fine, but when I try and run it from a remote computer that has the runtime installed it gives me the following error:
"The operation is not valid for the state of the transaction"
I thought this might have something to do with a distributed transaction, but I can't figure out how my configuration is incorrect if it is. I wasn't sure if anyone else had run into this issue before or if I was alone in it. My MSDTC settings are to allow remote incoming and outgoing connections, no authentication, and the network service account is the login. Any ideas?
Any advice would be great, Thank you!
Aj
*This post is locked for comments
Hi,I am getting the same error, but it is weird. I was able to insert and then two days after it started giving this error. I have not changed any of my code. Any thoughts?
It turns out that you must have MSDTC configured on both the server and desktop and that the desktop should also be set to accept incoming transactions and a user who has sql server priveleges...I used a service account that has domain admin priveleges to be on the safe side. As soon as I properly configured the MSDTC on the client, it started to work as expected.
Hope this helps anyone else,
Aj
Thank you for the link, unfortunately it's one I've already found...but since I'm on eConnect 11 and that article was written for eConnect 10, it's sufficiently different where the few items I could apply from the article did not help my issue. I posted on that link hoping for some updates to the article.
With the above said - my transactions do not at all fit the description of the article...I'm trying to integrate 2 vendors each with two addresses and email addresses...I can't imagine why two records with only a handful of child nodes would cause a timeout...that's why I was thinking it had to do with MSDTC...but I'm at a loss.
Any help would be great,
Aj
Developing for Dynamics GP blog has posted an article about this error, please take a look into the below post:
blogs.msdn.com/.../web-services-configuration-settings-for-integrating-large-transactions.aspx
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (