This is a common error I have run across and can be solved by making a change on the client’s machine eConnect config file. This post is a reminder for me if I see this on a new image of a machine using eConnect.