Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Jesus Lopez]

We cannot reset passwords in GP and we keep getting this error message. We’ve tried to reset passwords in the SQL server and it does not work. We think its because Dynamics GP encrypts passwords differently then in SQL. If anyone can help we could appreciate it. 

[Kerry Hataley]

Hi Jessie,

The Error tells me you have Rockton Software ToolBox installed…

So you need to start there and see what you have setup.
To get moving you can simply ‘UNCHECK’ the ‘Enable Password Policy’ from Rockton to adjust.

——————————
Kerry Hataley
CEO & President
Nanook Software, Inc
——————————
——————————————-

[Jesus Lopez]

Hello Kerry,

Thanks for the reply!

We made sure that setting is unchecked; should we reinstall GP without any add-ons and then try to reset password?

——————————
Jesus Lopez
APC
Raleigh NC
——————————
——————————————-

[Kerry Hataley]

A couple of things to try…

1. Are you trying this as ‘SA’?

I have seen something like this before (Not Rockton) where the ODBC DNS name has been changed and/or are different on the systems.

Are you on the server doing this?

Need more info on the environment you are accessing from.

This is also an SQL hack to force the user to create a new password…Dynamics will force the user to enter a new password when it is <blank>.
If you are comfortable with SQL, you could run this script on the user with this issue…

ALTER LOGIN [ <SQLUserID> ] WITH PASSWORD = ”

——————————
Kerry Hataley
CEO & President
Nanook Software, Inc
——————————
——————————————-

[Luc St-Yves]

I have seen something similar to this before, and the cause was that GP client was installed without the third party.

If you go under Microsoft Dynamics / Tools / Customize / Customization Status, do you see Rockton Software third installed and Activated ?

——————————
Luc St-Yves
Business Analyst
Co-Leader GPUG – Montreal chapter
Humanware Technologies
Drummondville QC
——————————
——————————————-

[Jesus Lopez]

Yes i do see rockton Dynamics GP Toolbox.——————————————-

[Jesus Lopez]

Yes i am logged in as the SA and I’m on the server; I’ll try to run the script in SQL and let you know——————————————-

[Jesus Lopez]

Hello Kerry,

We’ve tried the SQL password reset command and it does not work; anything else you can recommend. (BTW we recently did a GP upgrade from 2016 to 2018)——————————————-

[Luc St-Yves]

I would recommend 2 avenues to initiate :
1) Place a call at Rockton or at your GP VAR since it seem to be a problem related to the third party
2) If the SQL did not work, open SSMS, connect to your database and open the logins.  Double-click the faulting login and blank the password, then save.  It will gives you a warning since you are blanking the password, confirm that is what you want.  Then ask the user to login GP, leaving his password blank.  It should prompt him to resume his password.

Good luck !

——————————
Luc St-Yves
Business Analyst
Co-Leader GPUG – Montreal chapter
Humanware Technologies
Drummondville QC
——————————
——————————————-

[Jesus Lopez]

Hello,

I’ll go head and place a call to Rockton and ask them to take a look at the issue. I;ll let you guys know what happens.

Thanks to Kerry Hataley, Luc St-Yves, Charles Ray for all the help!——————————————-

[Kerry Hataley]

In case Rockton, doesn’t get back to you quickly I couple more questions / comments.

1. I don’t know how the SQL Alter didn’t work – Unless you tried to reset password from Dynamics GP after this. The step should be:
     a. Run the Alter SQL script
     b. From a Dynamics GP system, have the user login with there user ID, as that point it will tell them there password is blank and will require them to enter a new

This should fix the first issue, with them access the system.

Now you mentioned that you have done an update, is the version of Rockton Toolbar at the correct version?

Also, after you updated the Rockton, did you run the required scripts to finish the update  – sometime required as ‘Admin’ depending how the Dynamics GP was installed. (Run Dynamics GP as Admin – right click on Dynamics GP)

You could also run the Install/Upgrade toolbox again… and re-run… look for errors

——————————
Kerry Hataley
CEO & President
Nanook Software, Inc
——————————
——————————————-

[Jesus Lopez]

This is the SQL command we had to run;
ALTER LOGIN userid WITH CHECK_POLICY = OFF
GO
ALTER LOGIN userid WITH PASSWORD = ”; 

After this the the users password was blank! we just had to update the users password and they were able to log in!
(I also reinstalled GP without any add on’s and we were also able to reset user passwords in GP it’s self.)

I need to call Rockton and ask then why GP Tool Box is creating this issue.——————————————-

[Charles Ray]

You are correct in that GP encrypts passwords, therefore any user adds and password changes must be done in GP.  It is also essential that the ODBC ‘Server’ connection on the login window is identically named since the ODBC connector name is part of the encryption algorithm.
For troubleshooting:
1. Log into GP on the server as ‘sa’ or ‘DYNSA’.  Note the ‘Server’ name (Default for your version is ‘Dynamics GP 2018’.
2. Change the user’s password in the User Setup window.
3. Switch user in GP, logging on as that user with the reset password.
4. If that works, have the user try logging in on their own client, making sure the Server name is identical – ‘Dynamics GP 2018’ and ‘Dynamics GP 2018 (New)’ are not the same.
5. If that does not solve the problem, consider creating a new user – the record may be corrupted.
6. Check the 32-bit ODBC System DSN and make certain it was not modified – ANSI flags must be off, and the login must be SQL, not Integrated Windows.
Since you are using HR, are you also using Greenshades?  If so, there was an issue with Greenshades Center throwing a password-related error due to the increased length of the GP password field from 15 to 21 characters.  It did allow you to log in, however, so I don’t see that being the cause – just food for thought.
As always, contact your VAR for additional assistance.

——————————
Charles Ray
Senior Systems Specialist
CAL Business Solutions, Inc.
Harwinton CT
——————————
——————————————-

[Luc St-Yves]

Just to clarify, and also to confirm my thinking… ? your comments about the ODBC name connection, I think, are wrong,

I have other terminal servers having clients where the ODBC name is not exactly the same, but which point the same sql server.  No problem with the password.  They work everywhere.

You are right thus, the password encryption is “sql server” dependant, but it is rather the SQL server name itself that is part of the encryption, not the ODBC.

Cheers

——————————
Luc St-Yves
Business Analyst
Co-Leader GPUG – Montreal chapter
Humanware Technologies
Drummondville QC
——————————
——————————————-

[Beat Bucher]

I agree with ,
It’s the SQL server name that’s key to the password encryption.. not the ODBC link name..
To avoid problems when moving/upgrading SQL server?s in the past, I’ve always used an ALIAS for the DNS entry of the GP / SQL server and given it a generic name like “DYNAMICSGP” and my SQL instance was always called DYNAMICSGP too, which makes the server name in connection strings very easy to remember : DYNAMICSGPDYNAMICSGP
The name of the ODBC connection doesn’t matter at all, and that’s why most people run into issues, because the GP client wasn’t deployed in a consistent matter. Sometime it was the full server name that was used, sometime it was an IP Address. that works as long as the user doesn’t change client workstation to login into GP..

——————————
Beat Bucher
Business Analyst, Dynamics GP SME
Montreal QC/Canada
@GP_Beat http://www.gp-geek.com
Montreal QC GPUG Chapter Leader
MBS MVP (2015-2018)

——————————
——————————————-

[Charles Ray]

Thanks for the correction and clarification!

——————————
Charles Ray
Senior Systems Specialist
CAL Business Solutions, Inc.
Harwinton CT
——————————
——————————————-

[David Musgrave]

FYI: I wrote an article on 2008 on the password encryption model.

https://blogs.msdn.microsoft.com/developingfordynamicsgp/2008/10/01/why-does-microsoft-dynamics-gp-encrypt-passwords/

Regards

David

——————————
David Musgrave MVP, GPUG All-Star

Managing Director
Winthrop Development Consultants

Perth, Western Australia

http://www.winthropdc.com
——————————
——————————————-

[Charles Ray]

Thanks, David.  I can never remember where I read that originally.  I’m going to bookmark it for future reference.

——————————
Charles Ray
Senior Systems Specialist
CAL Business Solutions, Inc.
Harwinton CT
——————————
——————————————-

[David Musgrave]

Also, don’t forget that GP Power Tools, Database Validation tool includes functionality to do a bulk reset of user’s passwords ( and keeps the encryption).

GP Power Tools Portal: http://WinthropDC.com/GPPT

Regards

David?

——————————
David Musgrave MVP, GPUG All-Star

Managing Director
Winthrop Development Consultants

Perth, Western Australia

http://www.winthropdc.com
——————————
——————————————-