I created a .NET 4.5 web application in VB. This app generates sales orders in GP 2010 with eConnect 11.0. I accomplished this by adding references (NOT service references) to the API DLLs. The programming works. I have successfully generated sales orders from my local machine and from a standalone web server.
However, when I deploy the same application to a web farm made up of 2 ARR servers, 2 SQL servers, and 2 web servers, the application fails to generate a sales order. In this configuration the web application content is located in a share. The exact error messages I receive are:
The pipe name could not be obtained for net.pipe://localhost/Microsoft/Dynamics/GP/eConnect/EntityOperations.
The pipe name could not be obtained for the pipe URI: Access is denied. (5, 0x5)
I have done an exboritant amount of research on this. I have installed eConnect on the web servers and the SQL cluster servers. I have verified the service is running on all servers. I have verified the service is set to automatically start. I believe I have pinpointed the issue, but I just don't know how to resolve.
Apparently, netNamedPipeBinding is for single machine use only. Because this is a web farm, it won't work. I've confirmed this by moving the content directly onto each web server instead of the share. When I do that, it works. Once I move the content back to the share, it fails again. I don't know much about these binding/endpoint options, so I don't know how or if I can reconfigure the eConnect service to accept a different method such as netTcpBinding. Thoughts?
