Back in the now distant year of 2010, I wrote a post about an eConnect error: There was no endpoint listening at net.pipe.
That has been one of the most frequently accessed posts on my blog.
Well today I encountered a strange variant at a client. I had upgraded an existing integration from GP 2010 to GP 2015, and the new GP 2015 integration was installed on the same workstation where the 2010 version had been installed.
When the client ran the integration, she received this error: