Microsoft Dynamics GP (Archived)

Dynamics GP user SA - Your ID has been locked out of the accounting system

(0) Share

Report

Posted on by alsantiago

100

sa at SQL level is fine, the account is not locked.

Environment GP2010.

Message: your User ID has been locked out of the accounting system. contact the system administrator.

Please note this is happening with user ID: sa

Troubleshooting steps:

1) I even tried: ALTER LOGIN sa WITH CHECK_POLICY = OFF; & ALTER LOGIN sa WITH PASSWORD = ’password’ UNLOCK ; Same problem persist when I logon into a company with SA.

*This post is locked for comments

I have the same question (0)

All responses (24)

Answers (2)

Tristan Clores 2,812 on at

Like (0)

Report

Hi,

Have all users log off from GP and run the script below:

delete dynamics..sy00800

delete dynamics..sy00801

delete dynamics..activity

delete tempdb..dex_lock

delete tempdb..dex_session

Once done, try logging back in as SA.

Let me know if you have further questions.

Was this reply helpful? Yes No
alsantiago 100 on at

Like (0)

Report

Thank you for your suggestions, any other Ideas?

I am still receiving the same error message with user SA

Was this reply helpful? Yes No
Suggested answer

Tristan Clores 2,812 on at

Like (0)

Report

Hi,

Any chance you are using Omni Tools?

If you are, check the security settings.

Was this reply helpful? Yes No
Verified answer

Jonathan Fear on at

Like (0)

Report

Are you using advanced password policies in SQL? Sounds like someone tried to login as SA too many times with the wrong password. If you look at the SQL login for SA you should see on the Status tab the box next to login is locked out is checked. Try unchecking that if it is.

Was this reply helpful? Yes No
Verified answer

Mahmoud Saadi 32,738 on at

Like (0)

Report

I do believe that this is related to having your "sa" account locked out. You may need to check the following on your SQL management studio, under security go to your "sa" account properties and check the following;

On the "General" Tab

On the "Status" tab

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Was this ever figured out? I"m getting the same message. I have tried all these suggestions and I still get the error for a user

Was this reply helpful? Yes No
Derek Albaugh on at

Like (0)

Report

Can you login to SQL Server Mgmt Studio as 'sa'?

If not, then you may want to enter this question in the Microsoft SQL Server forums, as it would be more an issue on that side.

The only time we really see this type of message for 'sa', is when you logon to Dynamics GP as 'sa' in Company A on one machine, then leave it open, then go to another machine and log 'sa' into the same Company A.....during the login, it'll state that 'sa' is already logged into that company, if you delete the login so you're then able to login on the second machine, if you go back to the first machine, 'sa' will still be logged into Dynamics GP, but technically the account has been removed, hence you'll get a message as mentioned on this forum.

When it mentions the 'Accounting System', it just means Dynamics GP.

If you're experiencing SQL connectivity issues, where the connection between Dynamics GP and SQL is being dropped at all, that could potentially cause error messages such as this but would be more intermittent and random in nature.

Thanks

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Yes I can log in as sa. It's only one user I'm having the problem with

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

The account is not a sa account and the account is not locked out. The error is in our test company on a different server. It works fine in our live environment

Was this reply helpful? Yes No
Derek Albaugh on at

Like (0)

Report

Ok, thanks for the clarification. This post was originally including 'sa' as well.

If it is only one user that is having the issue with logging in, login to Dynamics GP as 'sa' and reset this user's GP login password, which will re-encrypt the password for that server, then have the user attempt to login to Dynamics GP on that machine.

If it is only one user, it seems like it would be more encryption on the user's GP login password than anything else.

Also, make sure the ODBC DSNs on all machines that Dynamics GP is installed onto, that are being used with GP, are setup identically as per KB 870416, especially the server name for the SQL instance, as the password encryption is based on this setup.

Thanks

Was this reply helpful? Yes No