4,887
I have a client that when SQL was installed - created the 'sa' account with a 22 character password. The GP login screen only provides 15 character spaces.
Therefore, they can not perform the exclusive 'sa' type activities.
Has anyone encountered this problem?
If I create a new user and assign to 'sysadmin' role will GP let the new user create users, companies, etc????
Any Guidance is appreciated......
*This post is locked for comments
Glad to know you were able to resolve your issue and keep in mind that the reason we come to these forums is to provide our unbiased assistance to those who seek help.
Hi Bron,
Thank you for saying it 'out loud'. The Dynamics Community is a very generous community. I'm proud to be part of it. I always tell new people to reach out for help on the forums. Help is readily available. We may not always know the answer, but we try!
Kind regards,
Leslie
Thanks everybody - case closed.
This is a great forum.......I always try to educate my clients on how to use customer source, these types of forums and the fabulous blogs that exist around MBS.
Personally, the strength Great Plains MBS is not in it's software - it's in the willingness of all concerned to knowledge share and assist those that need it........
Everyone wants everyone to succeed and prosper. If only nations could act like GP users..........
Take a look at my article Microsoft Dynamics GP 10 POWERUSER role vs Microsoft SQL Server sysadmin role. As Leslie stated before, except for some add-ons and third party products that do require 'sa', you should be golden.
I love this forum. Lots of great valuable advice. The idea of changing sa on temporary basis is definitely a viable option - the utilization of DYNSA instead of sa is also viable.
However, in my initial posting I asked - "if I create a user in GP and then assign to 'sysadmin' will that user be able to do everything 'sa' can do..........
I tested this on my workstation and I think answer is yes.
I created a brand new user (did not enforce SQL policy) - assigned to power user role - granted access to companies.
Exited GP - went into SQL under login properties - assign the new user to the 'sysadmin' server role (in addition to 'public') and voila..........my new user is able to create users, backup databases, create business alerts, etc......seems to work just like 'sa'. I did not test Professional Tools........
Thoughts?
Any reason not to advice my client to simply alter an existing login by adding the login to the sysadmin server role?
Thanks...........
If u want to change ur DYNSA password then go to SQL and edit DYNSA Login property and set password as blank.It will give warning. U accept that warning and set blank password to DYNSA. Now u login GP using DYNSA. GP will ask "It is blank password u want to change?" Now you click ok and set the new password
regards
Jeganeedhi
How about telling your customer to set the password to a temporary, short, and manageable value until you complete what you need to do, then reset it to their favorite 22-char value once you complete your changes. Just saying...
Okay - now we're getting close to a solution.
The question will now be - Can we use SQL to reset the DYNSA Password?
I'm confident my client has never used the DYNSA account and therefore will not know the DYNSA password.
Since they can't login as 'SA' to reset user password - is there a table in SQL that can be altered to 'reset' user password.
I know that the system password can be reset to blank by writing a sql script (been there done that)........is there one for a user password?
Thanks everyone for your assistance.......
#1
André Arnaud de Cal...
291,431
Super User 2024 Season 2
#2
Martin Dráb
230,503
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
