eConnect 2018 "Unable to Add user to SQL"

(0) Share

Report

Posted on by AwalshGA

385

Hi,

Successfully installed GP 2018 on a new SQL 2016 server in preparation for upgrade later this month. Now I'm trying to install eConnect but receive the error noted in subject line. Here's what I've tried:

I am logged into the box using my domain account which is part of a group that has local Administrator rights to the box.
Created domain service account and added it to the local administrators group on my SQL box where I'm trying to install eConnect
Added SQL login for service account, gave it sysadmin role and mapped to all GP company databases and DYNAMICS and added to DYNGRP role
Launched the eConnect install from the MDGP2018_RTM media and accepted the default features by clicking Next
Entered the Domain, User Name (service account created above) and Password as shown in screen shot below:
Entered Server Name (with instance name appended) and select SQL Authentication. I did not click the 'Do not add service user to SQL':
After clicking Next and then Install on the following screen it tries for about 5 seconds and then shows the following message:
When I click OK it shows me a screen indicating the install failed. Event viewer shows this same error but with no additional helpful detail.

Other hopefully helpful points:

I've also tried the above without first adding the Service Account as a SQL login - same result
On the SQL Connection Information page I clicked the 'Do not add service user to SQL' checkbox which blanks out the Server Name and GP System DB name fields. Received the following message:
Created a brand new service account after multiple iterations with initial account and had same results.

I hope I've provided enough details to give someone smarter than me a few clues to try to help me out. Thanks!!

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (1)

Derek Albaugh on at

Like (1)

Report

Looking at what you mentioned here, I'm wondering if it may not be an issue with the account you're trying to use with eConnect, such as having the @ symbol in the user ID name.

The other thing I could think of off the top of my head would be to make sure the password is 15 characters or less, as Dynamics GP and related applications usually only allow 15 or less.

This message usually has to do with the service account that eConnect is attempting to add the SQL Server instance, because this account is used to make the connection between SQL and eConnect.

The eConnect Service User account is used by the eConnect Integration Service, Incoming Service and Outgoing Service. The account must be a member of DYNGRP role in the Dynamics GP system and all company databases, on your SQL Server.

Go to SQL>>Security>>Logins, add the user, give them sysadmin role, then give them access to the system and company GP databases as well as the DYNGRP role to each GP database, then try installing eConnect with this user account.

Thanks

Was this reply helpful? Yes No
Suggested answer

Omar E. Buch Gomez on at

Like (0)

Report

Hi AwalshGA

I would suggest to use SQL Server Profiler (showing only errors) to find out the exact reason for the problem.

Was this reply helpful? Yes No
Verified answer

AwalshGA 385 on at

Like (1)

Report

Derek, thank you for the quick response and detailed suggestions. You gave me a few more things to check. Turns out it was definitely the service account but I'm still not 100% sure what the root cause was. I ended up using a brand new service account (with the FQDN) and a 15 character password (great reminder from you) and was able to install eConnect.

It may have been that the previous service accounts (I tried two others before the last one worked) had a longer password or, for at least one of them, the service account name was truncated when added to my SQL logins. Apparently, SQL uses the pre-Windows 2000 name from the AD account which has a limit of 20 characters. The service account name resolved correctly when I added it as part of the eConnect installation process but the corresponding SQL login name was exactly 20 characters and had chopped a couple of characters from the true FQDN.

Thanks again for your assistance. I'm confident your insights led to the resolution in my case.

Was this reply helpful? Yes No
AwalshGA 385 on at

Like (0)

Report

Hi Omar,

Thanks for the suggestion. I was able to resolve my issue prior to seeing your suggestion but will definitely try that next time. See my response to Derek A's post for a bit more detail on what ended up happening. Thanks again!

Was this reply helpful? Yes No
Derek Albaugh on at

Like (0)

Report

Thanks for the update and I'm glad it helped resolve your issue. I'm sure this will help others as well...…..

Was this reply helpful? Yes No
yoandy 115 on at

Like (0)

Report

Hi i have the same problem how do you solve the issue am sotkc in that part than you

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

Hi Yoandy,

Can you please post a detailed description of the message you get ? maybe a screenshot would help too .. .

Was this reply helpful? Yes No