I figured I would write a new post for this instead of piggybacking another - I am having a problem with using eConnect on my local machine pulling data from the GP server.  I basically have taken the sample code and modified the connection string - and it all works great when I run it on the GP server directly.  If I take the code and run it from my local machine, it hangs/locks up on the New eConnectMethods object instantiation:Dim requester As New eConnectMethods()  I don't see anything getting logged when this occurs.

Do I need to install something locally for this to work?  I thought I could just reference the 3 dlls per the documentation and all would be good.

Any help would be greatly appreciated.  Thanks in advance!

Sounds like you have the DCOM issue. Carefully read the install doc for the DCOM setup.

• Is GP 10 installed on your local machine?
• Did you configure MSDTC security on your server and local machine?
• If your eConnect 10 COM+ object Identity set to run using the eConnect user account you setup?

 Like Steve, I would recommend reading the installation instructions--everything you need to get it working is in there.

Looks like all I had to do was increase the timeout on the MyComputer properties to 900 and right click the eConnect Com+ and hit start (all on the GP server).  Not sure if the timeout setting actually did anything for this case, but I guess the Com+ component wasn't started - even though eConnect was working if I ran the app on the GP server directly? 

 Anyway, I am now past that line of code and on to the next error with the eConnect_Requester call not finding the Microsoft.Dynamics.GP.eConnect assembly... back to the docs!!! :-)

Thanks for the replies!

On an XP machine, I fixed this by configuring DTC and installing Message Queueing.