Understanding the Login Failure Error when Importing Data into Dynamics GP using SmartConnect

While running a SmartConnect integration to Microsoft Dynamics GP, the integration failed and returned the below error.

Error: Login failed for user ‘domain\user’.

To fix the error, you need to understand how SmartConnect and Microsoft Dynamics GP connect.

To understand how the SmartConnect GP connection works:

SmartConnect 21 SmartConnect 2018

For SmartConnect 21: On GP Connection, Under the Connections Tab:

For SmartConnect 18: On Setup on the Setup tab >> Double click on the SmartConnect Dynamics GP Connector

Information:

• Take a look at the Ignore Proxy Service (Y/N) section :
  • If marked (Y), it uses the local account to run eConnect services.
    For Example: C:\Windows\System32>whoami 
  • If unmarked (N), it uses the eConnect service account to run eConnect services. (i.e., account used under Services >> eConnect for Microsoft Dynamics GP) 
• Service Account: Whichever account is applicable for the above two options, there is no need for sysadmin access in SQL security. DYNGRP permissions are sufficient to execute eConnect procedures against the company database.
• GP Connection: Uses ‘sa,’ which has sysadmin privileges. This is sufficient to retrieve company details, get the next numbering, and prepare mapping data on the Dynamics GP destination node/schema ONLY.  This account is not used to push data into GP directly. Data insertion is handled by the eConnect services.

Using “Ignore Proxy = N,” is the recommended approach to ensure that the service account is used for authentication instead of the local user account. If you select the option “Ignore Proxy = Y”, you must add the integration user account to SQL Security (the account running the integration).

Note: If it shows the error below, then you need to give DYNGRP permission for a given account.

Cannot open database “NEWCOM” requested by the login.
The login failed. Login failed for user ‘domain\eConnectSvc’.
The EXECUTE permission was denied on the object ‘xxxxxxxxxxx’, database ‘NEWCOM’, schema ‘dbo’.

Ensure that the eConnect user account has DYNGRP permissions on all SQL databases, including the DYNAMICS database.

Resolution

Now that you understand how the SmartConnect GP connection works, you are better equipped to fix the issue. Start by reinstalling the GP Connector on SmartConnect 21 or run system maintenance on SmartConnect 18.

If the issue persists, we have several resources available to help you troubleshoot, including step-by-step instructions on how to fix the login error on one machine, and information regarding not having permissions to the GP company database.

=============================================================================
Have a question? Please reach out to us at support@eonesolutions.com