Microsoft Dynamics GP This login failed

We are running Microsoft Great Plains / Dynamics version 10 and have issues with some users not being able to login. They receive this message:
"Microsoft Dynamics GP" "This login failed" "Attempt to log in again or contact your system administrator"
They are able to use the network fine with their passwords and after looking at security on the SQL 2005 box they tend to get locked out. Sometimes I am able to fool the system by disabling the passord policy entirely but today i have a user that is unable to login but was fine yesterday without any isse.

Instant Access to this Solution

Plus...

30 Day FREE access, no risk, no obligation

Collaborate with the world's top tech experts

Unlimited access to our exclusive solution database

Never be left without tech help again

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

"The time we save is the biggest benefit of Experts Exchange to Warner Bros. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange." Mike Kapnisakis, Warner Bros.

"Our team likes having a resource that is more secure than just using Google and most experts using this service really know their stuff. It's nice to look here first versus using Google." Dayna Sellner, Lockheed Martin

"Anytime that I've been stumped with a problem, 9 out of 10 times Experts Exchange has either the accepted solution or an open discussion of the potential solution to the problem." Kenny Red, eBay Inc.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.

Screenshot of Experts Exchange Knowledgebase

Need individual assistance?

Our experts are ready to help.

If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.

Want to learn from the best?

Read articles from industry experts.

Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.

Working on a long term project?

Store your work and research.

Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.

Join the Community

Give a Little. Get a Lot.

Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.

Hi,

There are several possible causes for this issue. Changes in GP 10 increased security with regard to logins to GP, but unfortunately the side effect is that some GP accounts can be prevented from logging in under certain circumstances.

If you have access to Customer Source, lookup KB Article 919345. It has an extensive list of causes and resolutions.

Here are two common ones:

1) Make sure that the DSNs on ALL machines are exactly the same, and that the DSN on the GP SQL Server is exactly the same as well. This includes both the DSN name, and the SQL server / instance name (i.e. don't mix names and IPs, like sql01\instance and 192.168.10.20\instance).

1b) Make sure that all of the DSNs are using the SQL Native Client (SQL 2005) driver. Do not mix the old "SQL Server" driver and the new SQL Native Client driver.

2) The GP user ID is case sensitive, so make sure that the user is typing the login ID properly. I think it is easiest to make all GP IDs all lowercase characters to avoid any confusion.

Others are:

3) If you are on GP 9 (not applicable to you)

4) You upgraded from MSDE 2000 to SQL Express 2005

5) The public group does not have Execute permission on the smDex_Max_Char stored procedure in the master database

6) You are using mandatory profiles together with Terminal Server

7) You are running Small Business Financials (not applicable to you)

8) The SQL Login was deleted for the GP user (sounds like this is not applicable)

Let me know if either #1 or #2 sound like they could be possible causes.

One troubleshooting step is to manually reset the user's password by changing the password for their SQL login directly in SQL Server Management Studio. When the user launches GP and tries to login, they should be prompted to change their password. If they are not prompted, it may be a sign of a more subtle issue. This happened to one of my clients, and it took several hours of troubleshooting with Microsoft support to resolve (strangely, the answer was to switch that one PC to use the older SQL Server driver, which made no sense, but worked).

Thanks,

Steve Endow
Dynamics GP Certified Trainer
Dynamics GP Certified Professional

Question

Microsoft Dynamics GP This login failed

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution