Tech Tuesday: Steps for Installing eConnect using the Microsoft Installation Media
This week's Tech Tuesday is from our support guru, David Youngquist, who has included steps for installing eConnect using the Microsoft Dynamics GP 2013 installer instead of installing it from the SmartConnect media below:
1. If you prefer to install eConnect using the Microsoft Dynamics GP installation media, the eConnect installer can be found in the following folder(s)
If you are on a 32 bit machine, the installer is in the AdProd\eConnect\x86 folder.
If you are on a 64 bit machine, the installer is in the AdProde\Connect\x64 folder.
The file you want to run is named econnect.exe
2. When installing from the GP installation media, the only required component is the eConnect Runtime, the other options are not required for SmartConnect. Make sure eConnect Runtime Services is selected then click the Next button.
3. This screen is asking for a Windows login account. This is not a SQL account, this needs to be a domain user. In my screenshot my Domain is EONEDEMO, my username is eConnect. The eConnect install will grant access to the DYNAMICS db and each GP company db and add them to the DYNGRP role in SQL.
4. On this screen you need to type in the Dynamics GP SQL server name instance. On eConnect 2013 it will ask for your Dynamics database name. On 2010 and prior it assumes it is named DYNAMICS. You should type in the sa username and password on this screen. It will connect to SQL and add your eConnect user to the DYNGRP. In this screenshot, my GP server is named EONE-2014, and my SQL instance is named EONE. My Dynamics database name for this particular installation is DYN2013.
5. On this final screen hit the Install button.
6. Once eConnect finishes installing, go to Start – Run and type in “services.msc”. In the services window, look for the service named “eConnect for Microsoft Dynamics GP 20XX Integration Service”. If you see the service there and the status says Running, then eConnect has been successfully installed.
Do you have any questions? If you have a topic you'd like to be included in a future Tech Tuesday please comment below or email email@example.com!
Leave a Comment
Integrate & Automate without Any Code.
SmartList Data has Never Been Faster.
The Easiest Way to Report on GP Data.
Is econnect a required tool for integrating GP with other databases or is does it simply provide a more user friendly way of doing that? We have GP integrated with other databases using Visual Studio to design integration packages that move data to and from GP to other databases and it works pretty well.
eConnect isn’t “required” as SmartConnect will let you write to your own stored procedures or any table as you like.
However that makes you responsible for any business logic for that data (ie validation, etc).
There are many touchpoints that eConnect does not cover so you do have to resort to your own coding – but I would recommend that you use eConnect where possible since MSFT would have the domain knowledge for that endpoint.
I’ve an issue where a client is running maps from the SmartConnect console on a remote workstation and it gets the error about not being able to load the eConnect assembly files !! however, on the GP server, eConnect is installed along the SmartConnect services and the same map runs just fine.. I’ve never seen that eConnect was required on the workstations where the SC console would be setup ??