Open Forum

Expand all | Collapse all

eConnect Service account issues

  • 1.  eConnect Service account issues

    Posted 15 days ago
    OK, this is a little out of the norm, but I figure someone on here must have run across this or similar...

    Upgrading GP 2015 to GP 2018.
    Build a new server
    Copy DB's and upgrade
    Install eConnect and Smart Connect on server (using old service account and password - everything works)
    Create a workstation (client install on a surface pro - using old service account and password for eConnect etc... everything works)
    Pass instructions to IT team to duplicate

    IT team is unable to install eConnect receiving an invalid credentials error.

    Re-try on same workstation I get same error.

    Re-update db's now server will not re-install eConnect and update etc...
    Try to create a new service account and cannot install eConnect receives same invalid credentials error.

    How do you test your eConnect service accounts?  Open to suggestions!


    Justin Ross
    TD Carpenter & Associates, Inc.
    Casa Grande Az

  • 2.  RE: eConnect Service account issues

    Posted 14 days ago
    Hi Justin,

    I remember back when we removed local admin privileges to most of our users' account.  I had to make the service account that runs eConnect a local admin.

    I hope this helps!

    John Arnold
    Senior Software Engineer
    US Digital
    Vancouver WA

  • 3.  RE: eConnect Service account issues

    Posted 14 days ago
    To piggyback on @John Arnold, also make sure that the individual running the install does the Run As... Administrator to perform the install.  I haven't had any problems if I make sure to do that.​

    Another thing you can try is creating a service account for eConnect to run under.

    Blair Christensen
    Database Administrator
    Oppenheimer Companies, Inc.
    Boise Idaho GPUG Chapter Leader

  • 4.  RE: eConnect Service account issues

    Posted 14 days ago
    Hi @Justin Ross

    @Blair Christensen and @John Arnold are right.

    I'd like to add that the service user needs to have Local Admin Rights, the password should not expire AND they will need SQL Active Directory Users that have permissions to the DBs​​​.  Server Role can be Public, but the mappings have to give them rights to the GP DBs with DYNGRP permissions.

    You should also run them as admin during the installation and use the 'sa' login as the connection to the DB unless you have a named user with essentially the same rights as the 'sa'.



  • 5.  RE: eConnect Service account issues

    Posted 14 days ago
    The steps provided in the old 2012 eConnect installation guide are still valid today..  and it depends largely on where you plan to setup your eConnect services to run from.

    Unfortunately that part of the setup is completly missing from the actual Dynamics GP docs online..

    Beat Bucher
    Business Analyst, Dynamics GP SME
    Montreal QC/Canada
    Montreal QC GPUG Chapter Leader
    MBS MVP (2015-2018)
    All-Star 2013

If you've found this thread useful, dive deeper into User Group community content by role