1,340
Good afternoon,
I have a new install of GP 2015. From the server, I can create users, log in as the user and change the password. The users cannot change their password from the local client.
I have deleted the users and re-added them to no avail.
Need a little help.
Thank you,
Jason
*This post is locked for comments
If a GP user can login on one machine but not another, it normally means that the ODBC DSNs are not setup exactly the same on all machines.
GP login's passwords are encrypted based partially on the machine itself and the ODBC DSN used to connect to Dynamics GP.
If the ODBC DSNs are not setup identically on all machines, i.e. name of the ODBC, SQL Server name, etc. (also as per KB 870416), then a user will be able to login on one machine but not the others.
If you were to go to another machine, have 'sa' reset that user's GP login password within Dynamics GP, then that user would be able to login successfully on machine #2, but if they went back to the current machine they are able to login on, most likely they would see that they now are not able to login on that machine.
I would recommend first removing the 'Enforce Password Policy' option from the user to test they can login on all machines, then once you accomplish that, then you can add back the 'Enforce Password Policy' option and test again.
Thanks
Thanks,
I found that after changing the password from GP, Administration, Setup the checkbox (Change Password Next Login) automatically changed. Before changing the password it was greyed out, and I thought we cant use the checkbox once the user changes the password for the first time.
I have one more question which is related to GP 2015 password policy.
How can I change the password policy, so that an employee can log in from different computers? Right now whichever computer that they change their password for the first time can be used. If they exit and try to log in from a different computer their login doesn't work.
Hello Edrees,
You can login to Dynamics GP as 'sa' and in the User Setup window, change that user's password for them.
When you're attempting to mark the 'Change Password Next Login' option, are you referring to the User Setup window in Dynamics GP? If so, are you logged on as 'sa' or 'DYNSA' when doing so?
In regards to the 'Enforce Password Policy' options, those settings are actually enforced by SQL Server working with Active Directory, there isn't any real settings in Dynamics GP for that, other than we allow you to also use those policies with the GP logins to go along with the Windows AD accounts.
I'd be curious if you login to the SQL Server Mgmt Studio, then under Security > Logins, right-click on any GP login (not sa) and go into Properties. On the 'General' page of the login's Properties window, do you have the option to mark 'Enforce Password Policy' or is it disabled here as well?
If disabled in SQL as well, even when using the 'sa' login, then there is something not setup correctly either on the SQL or Active Directory side. In prior versions of Dynamics GP, we used to require certain versions of SQL, but with Dynamics GP 2015 you should be ok with that, so I would also maybe check your SQL Native Client driver being used for the ODBC DSN connections with Dynamics GP.
Thanks
Hi
I have GP 2015. I cant tick (Change Password Next Login) as it's greyed out. I would have to change users password on their own computer from SA then they will be able to use that password. How can I reset the password if a user forgot their GP password?
Thanks,
Edrees Rohina
Quick update on this issue. I was able to unmark the enforce SQL password policy for the users and now they are able to change their passwords.
There must be a setting in SQL that is preventing this. If I find more, I will post.
This is mostly an ODBC issue. Try deleting the current ODBC and create a new one with using the SQL Native client with the sa user
Your feedback is highly appreciated,
Jason, is this a 'migration' to a new server? Did you have GP running before? If you did, then the passwords are encrypted by the other server name.
How did you create the user ODBC connection on the workstation? Try with the USER ID and then try with SA and see if there is a difference.
The users are getting the error message 'password change failed for an unknown reason - please use your old password to log in next time'
I can log onto the server, log into GP as the user and change the password. When the user logs in on their workstation, they cannot change their password.
Hello Jason
Would you please elaborate further on the point of not having them able to change their password, any errors ?
Your feedback is highly appreciated,
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,235
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (