A common issue many users run into when first trying to run a custom eConnect application looks like the following:
The part of the error message to look out for is the “Could not load file or assembly ‘Microsoft.Dynamics.GP.eConnect.Serialization.” The version number may vary. From a developer’s standpoint, this could be a matter of a missing dll reference in the project; that discussion is beyond the scope of this article. However, from a user’s standpoint, this error often a result of not having the proper eConnect service installed.
To check whether or not eConnect is installed on the user machine, go to Start -> Control Panel -> Administrative Tools -> Services. Then, scroll down and look for the service named “eConnect for Microsoft Dynamics GP [GP version] Integration Service.” If the eConnect service is installed, the user might still be receiving the error because the service has not been started. To verify whether or not the service has been started/is running, look under the “Status” column next to the service and look for “Started.” To start the service, right click the service, and then press “Start.”
Note that even if eConnect is installed, the user might still receive the error above because the user has a different version of eConnect installed than the one the application uses. For example, the user machine might have the service “eConnect for Microsoft Dynamics GP 2010 Integration Service” but the application uses a different eConnect version, such as eConnect runtime for GP2013.
This article was written by Kevin Huynh, Dynamics GP Technical Consultant for Tridea Partners. Tridea is a leading Microsoft Dynamics provider serving CA, AZ, UT, CO and surrounding regions.