Error message when you try to log on to Microsoft Dynamics GP: "This login failed. Attempt to log in again or contact your system administrator"

Symptoms
When you try to log on to Microsoft Dynamics GP, you may receive the following error message:
This login failed. Attempt to log in again or contact your system administrator
Cause
Cause 1
This problem may occur if the password is changed at another computer. If the password is changed at another computer, the user cannot log on to Microsoft Dynamics GP at the user's computer. This situation occurs because the way in which the server name is set up in the Data Source (ODBC) differs from the way in which the server name is set up on the computer where the password is encrypted.

See Resolution 1 in the "Resolution" section.
Cause 2
This problem may occur if the user logs on by using the incorrect case for the user ID or for the encrypted password. In this case, the error message is received at the next logon.

See Resolution 2 in the "Resolution" section.
Cause 3
This problem may occur if the following conditions are true:

• You are running Microsoft Dynamics GP 9.0.
• A new user is created.
• The new user cannot log on.

See Resolution 3 in the "Resolution" section.
Cause 4
This problem may occur if the Advanced Password Policies check boxes are selected in the User Setup window when you update from Microsoft SQL Server Desktop Engine (MSDE) 2000 to Microsoft SQL Server 2005 Express.

See Resolution 4 in the "Resolution" section.
Cause 5
This problem may occur if the public group does not have the Execute permission on the smDex_Max_Char stored procedure in the master database.

See Resolution 5 in the "Resolution" section.
Cause 6
This problem may occur if you are using mandatory profiles together with Terminal Server.

See Resolution 6 in the "Resolution" section.
Cause 7
This problem may occur if the following conditions are true:

• You are running Microsoft Small Business Financials.
• Not every new user can log on. Specifically, only the sa user can log on.

See Resolution 7 in the "Resolution" section.
Cause 8
This problem may occur if the SQL login for the user is no longer present.

See Resolution 8 in the "Resolution" section.
Resolution
Resolution 1
To resolve this problem, verify the Data Source (ODBC) that you use for Microsoft Dynamics GP at the computer at which you receive the error message. To verify the Data Source (ODBC), click Start, click Administrative Tools, click Data Sources (ODBC), and then double-click the DSN connection. In the list that appears, you should see one of the following things:

• The name of the computer that is running Microsoft SQL Server
• The TCP/IP address of the computer that is running SQL Server. This address appears in the Servername box.

If you know neither the name of the computer that is running SQL Server nor the TCP/IP address of the computer that is running SQL Server, you can verify the Data Source (ODBC) on a working computer.For more information about an ODBC setup, click the following article number to view the article in the Microsoft Knowledge Base:


870416 How to set up an ODBC Data Source on SQL Server for Microsoft Dynamics GP


Resolution 2
The logon User ID field is now case-sensitive in Microsoft Dynamics GP. To resolve this problem, you must encrypt the user's password by using the correct case for the user ID. To do this, follow these steps:

1. Log on to Microsoft Dynamics GP as the sa user.
2. Click Tools, point to Setup, point to System, and then click User if you use Microsoft Dynamics GP 9.0, or click Microsoft Dynamics GP, click Tools, point to Setup, point to System and then click User if you use Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010.
3. In the User ID box, click the lookup button, and then click the user who cannot log on.
4. In the Password box and in the Confirm Password box, type a new password.
   
   Note If you are using Microsoft SQL Server 2005 or Microsoft SQL Server 2008 and Windows Server 2003 or Windows Server 2008 and are in a Windows Server 2003 or Windows Server 2008 domain, you can click to select the Change Password at Next Login check box in the User Setup window. For this feature to work correctly, the client computers must use SQL Native Client for the DSN connections that they use for Microsoft Dynamics GP.

Resolution 3
To resolve this problem, obtain the latest service pack for Microsoft Dynamics GP. For more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer.

Partners
https://mbs.microsoft.com/partnersource/products/GreatPlains/downloads/servicepackCustomers
https://mbs.microsoft.com/customersource/support/downloads/servicepacks
Resolution 4
To resolve this problem, follow these steps:

1. Log on as the sa user.
2. On the Tools menu, click Setup, click System, and then click User.
3. Click the user who is experiencing the problem.
4. Click to clear the following check boxes:
   • Change Password Next Login
   • Enforce Password Policy
   • Enforce Password Expiration
5. In the Password box and then in the Confirm Password box, type the user's password, and then click OK.
6. Have the user log on to see whether the problem still occurs.

For Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010, follow these steps:

1. Log on as the sa user.
2. On the Microsoft Dynamics GP menu, click Tools, point to Setup, point to System, and then click User.
3. Click the user who is experiencing the problem.
4. Click to clear the following check boxes:
   • Change Password Next Login
   • Enforce Password Policy
   • Enforce Password Expiration
5. In the Password box and then in the Confirm Password box, type the user's password, and then click OK.
6. Have the user log on to see whether the problem still occurs.

Resolution 5
To resolve this problem, follow these steps, depending on the version of SQL Server that you are using.
SQL Server 2005 or SQL Server 2008

1. Click Start, point to Programs, point to Microsoft SQL Server 2005 or to Microsoft SQL Server 2008, and then click SQL Server Management Studio.
2. Log on as the sa user.
3. Under the server that is running SQL Server and Microsoft Dynamics GP, expand Databases, expand System Databases, expand Master, expand Programmability, and then expand Stored Procedures.
4. Right-click smDex_Max_Char, and then click Properties.
5. On the Permissions tab, click the ADD button under Users or roles.
6. In the "Select Users or Roles" window, click the Browse button.
7. Click to select the Public check box, and then click OK two times.
8. On the Permissions tab, verify that Public appears under Users or roles.
9. Click to select the Execute/Grant check box, and then click OK.

SQL Server 2000

1. Click Start, point to Programs, point to Microsoft SQL Server, and then click Enterprise Manager.
2. Log on as the sa user.
3. Under the server that is running SQL Server and Microsoft Dynamics GP, expand Databases, expand Master, and then expand Stored Procedures.
4. Right-click smDex_Max_Char, and then click Properties.
5. Click the Permissions button.
6. Click to select the EXEC check box next to the Public user, click Apply, and then click OK two times.

Resolution 6
To resolve this problem, take one of the following actions, depending on the version of Microsoft Dynamics GP that you are using.
Microsoft Dynamics GP 2010 or Microsoft Dynamics GP 10.0
Have the system administrator remove the mandatory profile.
Microsoft Dynamics GP 9.0
Obtain hotfix 947362 or the latest update. For more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer.

Partners
https://mbs.microsoft.com/partnersource/products/greatplains/downloads/servicepack/microsoftdynamicsgp90_mspreleases.htm?printpage=falseCustomers
https://mbs.microsoft.com/customersource/support/downloads/servicepacks/MicrosoftDynamicsGP90_MSPReleases.htm
Resolution 7
To resolve this problem, obtain the Microsoft Small Business Financials 9.0 logon hotfix. For more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer.

Partners
https://mbs.microsoft.com/partnersource/products/sbm/downloads/hotfixes/microsoftsbf90hotfixes.htm?printpage=false Customers
https://mbs.microsoft.com/customersource/support/downloads/hotfixes/MicrosoftSBF90Hotfixes.htm
Resolution 8
To resolve this problem, verify that the SQL login exists. If the SQL login does not exist, remove the user ID from the Microsoft Dynamics GP database, and then re-create the SQL login. To do this, follow these steps.
Step 1: Verify that the SQL login exists
To verify that the SQL login exists, follow these steps, depending on the version of SQL Server that you are using.
SQL Server 2008

1. Click Start, point to All Programs, point to Microsoft SQL Server 2008, and then click SQL Server Management Studio.
2. In the "Connect to Server" window, follow these steps:
   1. In the Server name box, type name of the SQL Server.
   2. In the Authentication box, click SQL Authentication.
   3. In the Login box, type sa.
   4. In the Password box, type the password for the sa user, and then click Connect.
3. Click New Query, and then paste the following script into the blank query window:

SELECT name FROM master.sys.sql_logins

4. On the File menu, click Execute.
5. In the list of SQL logins, verify that the SQL login that is experiencing the problem exists.

SQL Server 2005

1. Click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
2. In the "Connect to Server" window, follow these steps:
   1. In the Server name box, type name of the SQL Server.
   2. In the Authentication box, click SQL Authentication.
   3. In the Login box, type sa.
   4. In the Password box, type the password for the sa user, and then click Connect.
3. Click New Query, and then paste the following script into the blank query window:

SELECT name FROM master.sys.sql_logins

4. On the File menu, click Execute.
5. In the list of SQL logins, verify that the SQL login that is experiencing the problem exists.

SQL Server 2000

1. Click Start, point to All Programs, point to Microsoft SQL Server, and then click Query Analyzer.
2. In the "Connect to SQL Server" window, follow these steps:
   1. In the SQL Server box, type the name of the SQL Server.
   2. In the Connect using area, click SQL Server Authentication.
   3. In the Login name box, type sa.
   4. In the Password box, type the password for the sa user, and then click OK.
3. Click New Query, and then paste the following script into the blank query window:

SELECT name FROM master..syslogins

4. On the File menu, click Execute.
5. In the list of SQL logins, verify that the SQL login that is experiencing the problem exists.

Step 2: If the SQL login does not exist, remove the user ID from the Microsoft Dynamics GP database
To remove the user ID from the Microsoft Dynamics GP database, take one of the following actions, depending on the version of SQL Server that you are using.
SQL Server 2008 or SQL Server 2005
Run the following script against the DYNAMICS database and against all company databases:
DROP USER  '<XXX>'
Note In this script, the placeholder <XXX> represents the actual login ID of the user.


SQL Server 2000
Run the following script against the DYNAMICS database and against all company databases:
sp_dropuser  '<XXX>'
Note In this script, the placeholder <XXX> represents the actual login ID of the user.
Step 3: Re-create the SQL login and the user ID in the Microsoft Dynamics GP database
To re-create the SQL login and the user ID in the Microsoft Dynamics GP database, follow these steps:

1. Log on to Microsoft Dynamics GP as the sa user.
2. Open the User Setup window. To do this, take one of the following actions, depending on the version of Microsoft Dynamics GP that you are using.
   
   Microsoft Dynamics GP 2010 or Microsoft Dynamics GP 10.0
   
   On the Microsoft Dynamics GP menu, point to Tools, point to Setup, point to System, and then click User.
   
   Microsoft Dynamics GP 9.0
   
   On the Tools menu, point to Setup, point to System, and then click User.
3. In the User Setup window, follow these steps:
   1. In the User ID box, click the Lookup button, and then click the user account.
   2. If the SQL login for the user does not exist, you receive the following error message:

This user does not have a corresponding SQL Login. To create a SQL Login, enter a password and choose save.

3. 3. Click OK.
   4. Re-create the SQL login for the user. To do this, change the password in the Password box, and then click Save.
   5. Close the User Setup window.
4. Open the User Access Setup window. To do this, take one of the following actions, depending on the version of Microsoft Dynamics GP that you are using.
   
   Microsoft Dynamics GP 2010 or Microsoft Dynamics GP 10.0
   
   On the Microsoft Dynamics GP menu, point to Tools, point to Setup, point to System, and then click User Access.
   
   Microsoft Dynamics GP 9.0
   
   On the Tools menu, point to Setup, point to System, and then click User Access.
5. Re-create the user ID for the company databases. To do this, select the user, click to clear the Access check box for all the companies that are selected, and then click to select the Access check box again for the companies to which you want the user to have access.
6. Click OK to close the User Access Setup window.