Microsoft Dynamics GP 2018 RTM has now been released and I am in the middle of a series of Hands On posts.
As part of that series, I am about to cover the installation of the eConnect additional product on a server configured for receiving messages via the MSMQ. However, there are two prerequisites which need to be dealt with before eConnect can be installed on the server.
Usually, when doing Hands On posts, I only cover the core installs and only mentioned prerequisites such as this, referring back to old posts were necessary, but it appears I’ve only made references previously to what you have to do, without actually blogging about it.
So, this series on the eConnect prerequisites, is going to be a brief diversion from the Hands On series, which will resume tomorrow.
| eConnect 18 Prerequisites |
|---|
| Set Service Account as Local Administrator |
| Install MSMQ Triggers |
What should we write about next?
If there is a topic which fits the typical ones of this site, which you would like to see me write about, please use the form, below, to submit your idea.
Perhaps my question is not e-connect 18 related, but we recently started deploying the connection between Connectwise and GP. For some users, I’m getting the following error message: “Unit Cost Calculation does not match out to Extended Cost”.
I’ve tried looking for the AUTOCOST option on CW, but they don’t use it, and I’m running out of options in terms of what could be causing it.
I’ve not used Connectwise, but most integration tools sit on top of eConnect (or GP Web Services which in turn themselves sit on top of eConnect); I have seen error messages like this and the error has always ben because the sum of the unit costs does not match the supplied extended cost.