Setting users passwords on GP2018

(0) Share

Report

Posted on by Hernan Batista

930

Good afternoon

I'm the sysadmin here in the office and in my PC (in forward WS1) I set the passwords for each GP user but when he will login in his PC (in forward WS2) the password doesn't work. So, I need to login in GP with my poweruser on his WS2 and set the password directly in WS2 to be fine to work. But this is not desirable.

Do you have any clue about why if I set a GP user password (using my poweruser or 'sa' ) in my PC (WS1) it doesn't work in user's PC (WS2) ??

thanks in advance

I have the same question (0)

All responses (6)

Answers (0)

Richard Wheeler 75,848 Moderator on at

Like (1)

Report

RE: Setting users passwords on GP2018

There are different versions of the SQL Data Client being used. Check your ODBC connections.

Was this reply helpful? Yes No
Derek Albaugh on at

Like (2)

Report

RE: Setting users passwords on GP2018

Richard is correct. Also, if the ODBC DSNs on all machines are not setup identically, what will happen is the GP user's passwords will be encrypted differently, thus, if you reset the user's password on workstation #1, that user will be able to login to GP on that workstation but maybe not workstation #2.

Resetting the user's GP password on workstation #2, then breaks the user from being able to login to GP on workstation #1.

The ODBC DSN is looked at when encrypting user's passwords, so if they're not setup identically, they'll cause the above behavior to occur.

Thanks

Was this reply helpful? Yes No
Hernan Batista 930 on at

Like (0)

Report

RE: Setting users passwords on GP2018

woao, ok, in my case, we are using on workstations a "DNS alias" but in the Server's OBDC we use the hostname directly, this different may cause this bevahior?

Was this reply helpful? Yes No
Bill Campbell 12 on at

Like (1)

Report

RE: Setting users passwords on GP2018

Based on the comments from both Richard and Derek I would agree that the difference in these ODBC connections will cause a problem with the hashing of the Password. I have found that missing a 'space' or having an extra 'space' in the name of the ODBC can lead to this behavior.

This was especially true with Integration Manager and or Management Reporter - I have been sure to keep the ODBC the same on all machines for many years now.

Was this reply helpful? Yes No
Derek Albaugh on at

Like (2)

Report

RE: Setting users passwords on GP2018

It is possible, yes.

Specifically, the encryption of GP user passwords is setup per the server name in the DSN, so if they are different on two machines, such as your server and PC, it can cause this to not work.

Again, to verify this, reset the user's password in Dynamics GP on the server and verify they can login. If they can, have them then attempt to login on the PC.

If they cannot login to the PC, but can login on the server, reset their password in Dynamics GP on the PC, then verify they can now login to GP on this PC. If they can, have them try logging into GP back on the server again.

If they now cannot login to GP on the server, then it's most likely what you're running into.

Was this reply helpful? Yes No
Nattis 487 on at

Like (0)

Report

RE: Setting users passwords on GP2018

As Mentioned by others, Server name ODBC's DSN should be same as Client machines.

If its different, you can login only with sa. other users will face login issue.

Was this reply helpful? Yes No