*This post is locked for comments
Announcements
*This post is locked for comments
Thanks for checking in on this one Beat. This is an odd one as their domain is on a cloud server and they join the domain via AWS Credentials Manager but only when they need the domain. eConnect is required for Concur eExpense. I will leave it up to them as to how to start the eConnect services once they join the domain. My job is to simply get eConnect installed.
For the records..
I ran into a situation where I had to setup eConnect for GP 2010 on a WorkGroup computer (not joined to a domain) which was a Windows Server 2012R2, and I got the same error about invalid SQL user..
There was no way I could join this system to a domain, as there simply was none. I started by creating a new user account locally with Computer Management > Users & Groups in order to have a valid service account ready.
I then ran the eConnect setup and simply provided as "Domain" name the Host name of the local server, entered the service account & pwd for the 2 other fields, and clicked on Next..On the next screen I simply provided the SQL instance name (HostName\SQL_instance) where the GP DYNAMICS DB was residing, and clicked on Next to proceed with the setup.. which went flawlessly to the end, without complaining.
I checked the SQL security and Windows services, and everything was there as expected.
You may find the following article on installing eConnect in a workgroup environment useful. It does require you to temporarily join the machine to a domain for the actual installation process, but you may be able to get it working in a workgroup by using shadow accounts after that.
The recommended steps to install eConnect for Microsoft Dynamics GP 2010 in a Workgroup Environment that will resolve the “Unable to add user to SQL” error message
support.microsoft.com/.../the-recommended-steps-to-install-econnect-for-microsoft-dynamics-gp-20
I BELIEVE IF YOU PROCEED THE USER NAME WITH .\ the installation will continue.
Almas Mahfooz
3
User Group Leader