web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

This login failed. Attempt to log in again or contact your system administrator

(2) ShareShare
ReportReport
Posted on by 9

Hi 

Recently my company Old Microsoft Dynamics GP windows server 2012 r2 migrated new Server windows server 2016 OS.

 

The GP users are local SQL account users.As per the Microsoft article SQL login and password Transfer logins and passwords between instances of SQL Server.

https://docs.microsoft.com/en-us/troubleshoot/sql/security/transfer-logins-passwords-between-instances

 

Now all the users facing This login failed. Attempt to log in again or contact your system administrator
 8715.gp.png

Categories:
I have the same question (0)
  • Richard Wheeler Profile Picture
    75,852 Moderator on at

    Go into SSMS and make sure the users have security for the DYNAMICS database. Make sure they are assigned the DYNGRP role. After making sure they have security for the DYNAMICS database drop them from all company databases and then go to Tools->Setup->System->User Access and check off the companies.

  • Suggested answer
    Derek Albaugh Profile Picture
    on at

    To add to what has already been mentioned, if even 'sa' cannot login to the GP application, verify that during the migration of the GP databases to a new server, you ran all the scripts from KB 878449, specifically the script to put the tables in the TEMPDB database. Without those, no users including 'sa' would be able to login to GP.

    If 'sa' can login to Dynamics GP but no existing GP users can, that is usually a sign that the login information wasn't migrated from the prior SQL environment to the new SQL environment.

    Majority of time, when transferring GP databases and logins to a new SQL Server, you will need to login to the new GP as 'sa' and reset the users passwords in Dynamics GP, which will re-encrypt them for the new server environment and allow them to login.  

    Let us know..........

    Thanks

  • Daemonk Profile Picture
    5 on at

    The most common cause of this error is that the user has entered the incorrect User ID or Password. It is important to note that both the Dynamics GP User ID and Password are case sensitive. Unfortunately, the GP system error does not indicate which field has been entered incorrectly. It may be the User ID or the Password or Both.

    mcdvoice survey

  • Abubakkar Profile Picture
    9 on at

    Thank . will check,  i will update you.

  • Abubakkar Profile Picture
    9 on at

    No you are wrong. Its not only one users all users around 30 to 40 users. How its possible all users incorrect password.

  • Abubakkar Profile Picture
    9 on at

    You are correct. but as per Microsoft  refer transfer the logins and the passwords between different instances of SQL Server running on Windows.

    docs.microsoft.com/.../transfer-logins-passwords-between-instances

  • Richard Wheeler Profile Picture
    75,852 Moderator on at

    On one of your workstations, login as 'sa' Does this work? If so, set the user's password on this workstation and then try logging into GP as this user. You may have different versions of the ODBC driver so the password get encrypted differently.

  • Abubakkar Profile Picture
    9 on at

    Hi

    i really appreciate your quick response

    yes. I can login any workstation with sql sa account its working fine, If i tried any users account the same error.

  • Richard Wheeler Profile Picture
    75,852 Moderator on at

    The problem is in SQL. How many users are we talking about? Can you delete all the users in GP and then go into SSMS and remove these users from the DYNAMICS and all company databases.Go into GP and add these users back. If this is not possible pick one user and drop that user from DYNAMICS and all company databases. Then add that user back to the DYNAMICS database and then go to Tools->Setup->System->User Access click on each company. Make sure this user has been granted the DYNGRP role.

  • Suggested answer
    Bill Campbell Profile Picture
    12 on at

    As Richard notes the major cause of this can be the ODBC connection. 

    If you are moving from an older ODBC version - problem.  
    If you have the same version - but you create the ODBC Connection with a different NAME - then same problem.

    So you might have 'imported the SQL logins per the script provided, but you may a difference in ODBC.

    If you already covered this - sorry - just jumping in to put my two bits into the conversation.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Season of Giving Solutions is Here!

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Abhilash Warrier Profile Picture

Abhilash Warrier 732 Super User 2025 Season 2

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 413 Super User 2025 Season 2

#3
Martin Dráb Profile Picture

Martin Dráb 289 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans