You’re offline. This is a read only version of the page.
Announcements
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.
Now all the users facing This login failed. Attempt to log in again or contact your system administrator
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.
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.
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.
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
#1
André Arnaud de Cal...
294,101
Super User 2025 Season 1
#2
Martin Dráb
232,866
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (
