Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Migrated GP Server to ...
Finance | Project Operations, Human Resources, ...
Suggested answer

Migrated GP Server to be hosted in Azure. Problems with EConnect service account doesnt authenticate.

(1) ShareShare
ReportReport
Posted on by bdaspider 5

Hi all,

We have migrated our GP SQL into Azure. All clients are connecting fine and have been using the new system. We have a few users with EConnect installed on the GP installs. I can run through the EConnect install on our On Premise older machines but I am unable to get past the first screen when using the same account on the Azure machines. These are all on the same domain.

On premise it goes through to the next screen after entering the service account and domain. 

On Azure user machine trying to install EConnect fails with the same service account and password as on prem. I get told that the credentials are invalid. 

Any ideas as to what is blocking this? I need to go searching through the differences in GPO's between the user machines which im about to do now but figured id reach out here incase anyone has run into something similar. 

Thanks very much, 

Bdaspider

  • ND_Clutch Profile Picture
    ND_Clutch 7 on at
    Migrated GP Server to be hosted in Azure. Problems with EConnect service account doesnt authenticate.
    Hi Bdaspider,
     
    Did you ever find a solution for this issue?  I am in a similar situation with the same error, although my Dynamics server is joined to our on prem AD environment and the workstation that I'm trying to install eConnect is Azure joined only.
     
    We've been using this service account for a couple of years now with the same server, the only difference is our workstations have always been hybrid joined.  So there haven't been any chances to this service account or the server configuration.  The only thing that changed is tyring to get eConnect installed on a Azure joined computer sitting on the same network (subnet.)
     
    From the workstation, I can successfully ping/resolve our on prem domain name and can use the service account to authenticate to the Dynamics server via the administrative share (c$).  Again, this same service accont has already been setup within Dynamics/SQL per Dynamics requirements as it has been working for a couple of years. 
     
    I thought maybe I needed to use the username format "domain\username" instead of just "username".  But that didn't work.  Any suggestions?
  • Suggested answer
    Mike Bufano Profile Picture
    Mike Bufano 1,480 on at
    RE: Migrated GP Server to be hosted in Azure. Problems with EConnect service account doesnt authenticate.

    Did you make sure that the Ecoonect account was included in the capture login script?

    The AD account needs to have DYNGRP rights before you do the install.   During an initial install, the rights are assigned as part of the install.  If you are moving the databases to a new server, the rights for the AD account have to exist on the SQL server...which is accomplished using the Capture login script.

  • Suggested answer
    Beat Bucher GP Geek GPUG All Star Profile Picture
    Beat Bucher GP Gee... 28,031 Super User 2024 Season 1 on at
    RE: Migrated GP Server to be hosted in Azure. Problems with EConnect service account doesnt authenticate.

    Hi Bdaspider,

    Not much to say more than what Derek suggested.. By the books, you should use a valid domain account for the eConnect service account that has local Admin permissions and can 'run as a service' of course.

    Unofficially, I've been able to get eConnect running with a local computer account on an Azure SQL server that wasn't joined to a domain and it worked, but I had to provide the account name in the setup the same way I'd for a domain account, otherwise eConnect setup would not recognize the account (i.e. YouServer\econnect_svc)

    This is not supported, but gets your eConnect services at least up & running.

    As for your issue, I'd start checking simple steps, like try to 'run as' some basic apps in windows with that eConnect domain account and see if Windows can authenticate properly against the AD server. If this basic step fails, then you should start troubleshooting on the AD side first.

  • Suggested answer
    Derek Albaugh Profile Picture
    Derek Albaugh on at
    RE: Migrated GP Server to be hosted in Azure. Problems with EConnect service account doesnt authenticate.

    Installing eConnect for Dynamics GP on an Azure environment really shouldn't be any different than on an on-prem environment, in that we want to make sure we're using a default SQL Server instance and not Azure SQL or SQL as a service which isn't supported, make sure the service account is a domain account  which also must be a member of the DYNGRP role in the Dynamics GP system and company databases.

    Other than that, make sure upper and lower case letters for the account and password are correct as SQL will look at that, make sure the account you're logged on as while doing the install has permissions to the SQL Server as well.

    Maybe some in the Community have run into the same type of issue?

    Thanks

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Congratulations 2024 Spotlight Honorees!

Kudos to all of our 2024 community stars! 🎉

Meet the Top 10 leaders for December!

Congratulations to our December super stars! 🥳

Get Started Blogging in the Community

Hosted or syndicated blogging is available! ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,661 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,379 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans