Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
OK, so we are working on a web site that uses eConnect. We first tried using the eConnect assemblies in our Visual Studio solution which worked great. Except when we we put it outside of the fierwall. We are getting a login failed. Well we found out that econnect is passing the domain user to SQL and SQL is denying it. Makes sense because the webserver is not on the domain. Its on the other side of the firewall.
We found the article below:
We thought OK we can use the service and pass the credentials in so we tried to make a reference in Visual Studio using this:
But we kept getting this error:
"Metadata contains a reference that cannot be resolved: 'net.pipe://10.1.1.72/Microsoft/Dynamics/GP/eConnect'.
There was no endpoint listening at net.pipe://10.1.1.72/Microsoft/Dynamics/GP/eConnect that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
The pipe endpoint 'net.pipe://10.1.1.72/Microsoft/Dynamics/GP/eConnect' could not be found on your local machine.
If the service is defined in the current solution, try building the solution and adding the service reference again."
We also looked at this post as well:
What we are trying to accomplish is this: we have a webserver off the network behind the firewall. We want to call the eConnect Integration Service which is on another machine on the network. Can anyone point us in the right direction?
What about if you create web service using eConnect into your web application. That may resolve your problem.
The eConnect WCF Service is designed to handle requests from the local machine only. Net.pipe will not route over a network (even from one server to the next on the same sub-net). This WCF service is not really intended for public use. It is an internal service for use by the SDK.
Also, as you discovered when using the .NET SDK, the user security in the request must be on the same domain as the database server. So that won't work for you either as you (understandably) have the web server in a DMZ.
What you are looking for is a completely separate add on called Web Services for for Microsoft Dynamics GP. This has an extra security layer and tool set so that trusted servers and users can communicate across different domains. However, installing and configuring it is not exactly trivial.
If you have the development resources in house, the easiest solution might be to create and host your own web service in the back end which calls eConnect. You could only allow connections from your trusted web server. The interface could ask for and return only the specific information needed in your application.
Business Applications communities