Dynamics GP 2018 Client Install - The login failed. Attempt to log in again or contact your system administrator

(1) Share

Report

Posted on by Yamanote235

I'm attempting to set up the client on a local machine (rather than having users log into an RDP session. I know the user exists in GP but on the SQL server, I get this error message:

Any help would be greatly appreciated.

SQL Server 2016 running on Windows Server 2016

The Main GP installation is also running on Windows Server 2016

I am attempting to run this from my workstation (Windows 10, v1909).

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (9)

Answers (0)

Sort by

Joseph Markovich 4,005 on at

Like (2)

Report
Copy link

Link copied!

Is the ODBC connection name for GP the same on the Windows 10 workstation as it is on the RDP server (or wherever you logged into GP successfully before?)

Joe

Was this reply helpful? Yes No
Yamanote235 10 on at

Like (0)

Report
Copy link

Link copied!

Hi Joe,

I should have made note of that. That's correct. I've set up the ODBC System DSN name the exact same as what I see in the RDP session.

RDP Session

My workstation

Was this reply helpful? Yes No
Joseph Markovich 4,005 on at

Like (0)

Report
Copy link

Link copied!

Are the SQL Server names the same?

Joe

Was this reply helpful? Yes No
Suggested answer

Pablito 225 on at

Like (0)

Report
Copy link

Link copied!

When you say "...but on the SQL Server, I get...", are you trying to log into SQL Server (via Management Studio) using a GP user account? If so, that won't work as GP hashes the passwords before storing them in SQL Server. Installing a GP client on a new machine shouldn't require you to login to SSMS per say. If I have the wrong idea, could you clarify the scenario?

Was this reply helpful? Yes No
Yamanote235 10 on at

Like (0)

Report
Copy link

Link copied!

@Joe - Correct, the server names are the same.

@Paul - apologies, there's probably some confusion since I am new to GP deployments and all of the moving parts. When I look at the SQL Server event logs, there is an event created that shows that information about the login --

"Login failed for user 'username'. Reason: Password did not match that for the login provided. [CLIENT: x.x.x.x] (my workstation).

Was this reply helpful? Yes No
Richard Wheeler 75,852 Moderator on at

Like (0)

Report
Copy link

Link copied!

Try logging in 'sa' on the server and set the user password and set it to expire. Then have this user login on the server and set the password. It most likely will work. I bet when this user goes back to his/her workstation the login will fail. This is because there are different versions of the SQL native client. You need to have them both be the same.

Was this reply helpful? Yes No
Suggested answer

Bill Campbell 12 on at

Like (1)

Report
Copy link

Link copied!

So if the version of the SQL Client on each machine is different that can be one of the reason - Richard I agree. The other issue may be the ODBC - and the name / description used in the saving of the ODBC.

I have found that the name, description and the server name all have to be the same from machine to machine.

Just poking my two bits in.

Hope it helps.

Was this reply helpful? Yes No
David Musgrave MVP ... 14,149 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Make sure ODBC and Server name are the same... Case sensitive. Also enter the User ID in same case.

This is because these values are used in the encryption algorithm for passwords and must match.

Regards

David

Was this reply helpful? Yes No
Yamanote235 10 on at

Like (0)

Report
Copy link

Link copied!

Hey everyone,

Thanks for your replies. With everything going on I hadn't had the chance to revisit this issue but you were all right on the money with the name, description, and server name needing to be exactly the same. I was finally able to log in using the locally installed client on my computer.

However, I'm now having another issue when I log in but I'm not sure what the cause could be. Once I click login it takes an incredibly inordinate amount of time to get to the home screen and the last time I launched it, the application eventually hung. I tried to let it sit for about 10 minutes or so but it wasn't responding. What could the issue be?

Was this reply helpful? Yes No