sa password is too long

(0) Share

Report

Posted on by Bron

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

I have the same question (0)

All responses (14)

Answers (0)

Sort by

Jeganeedhi Krishnan 2,500 on at

Like
a
(0)

Report
Copy link

Link copied!

Bron,

we also face the same issue.But now we are using the 'DYNSA' username instead of 'sa' .we can do all activities using DYNSA

Was this reply helpful? Yes No
Bron 4 on at

Like
a
(0)

Report
Copy link

Link copied!

Thank you for reply.

Is there any activities that you know of - where 'sa' is exclusively needed?

How about -

Change user password?

Check links?

Create users?

Create Company?

Log into Utilities?

GP Maintenance?

Thank you - I will research further - sounds like this works for your company? Did you do anything to the role/rights for DYNSA?

Was this reply helpful? Yes No
Jeganeedhi Krishnan 2,500 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi,
This is for your reference.
What are the primary differences between SA and DYNSA users in GP?

1. SA is the SQL database system administrator and has full access to all databases on the SQL Server, including non-GP databases. DYNSA is the GP database administrator and has access to all GP databases only.

2. SA and DYNSA are both granted Power User roles automatically in GP Security.

3. SA is required for certain tasks such as initial system installation, payroll updates, and to administer some 3rd party applications. Generally speaking though, DYNSA can perform most of the security and maintenance tasks in GP that SA can.

4. From a SQL database security perspective, DYNSA should be used by your GP administrator for day-to-day administrative duties. SA use should be reserved for SQL administrators where possible to reduce the possibility of tampering in non-GP databases.

Regards
Jeganeedhi

Was this reply helpful? Yes No
L Vail 65,271 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Bron,

You cannot use any of the PSTL tools if you are not logged in as 'sa'. Also, you must be logged in as 'sa' in order to create or change Business Alerts.

Do you have any 3rd party products loaded? Many of those products are 'hard coded' so that only 'sa' can perform administrative tasks.

Kind regards,

Leslie

Was this reply helpful? Yes No
Bron 4 on at

Like
a
(0)

Report
Copy link

Link copied!

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.......

Was this reply helpful? Yes No
MG-16101311-0 26,225 on at

Like
a
(0)

Report
Copy link

Link copied!

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...

Was this reply helpful? Yes No
Jeganeedhi Krishnan 2,500 on at

Like
a
(0)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

The sa Account password is the one db account in GP that is not encrypted so they can change it (unless they have any other applications that rely on the sa account) Otherwise get them to change the DYNSA password. Unless they have a password policy in place on their SQL Server, GP will first try the encrypted version of the password followed by the unencrypted version.

Was this reply helpful? Yes No
Bron 4 on at

Like
a
(0)

Report
Copy link

Link copied!

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...........

Was this reply helpful? Yes No
MG-16101311-0 26,225 on at

Like
a
(0)

Report
Copy link

Link copied!

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.

Was this reply helpful? Yes No