New April Hotfix and more changes for VAT
Check out the latest updates to Microsoft Dynamics GP 2016 and 2018.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
I was having issues with one of my employees computers not being able to log into GP due to the security program. I've changed/deleted that program and now am get the message: "Your attempt to log in to the server failed because an unknown error occurred when the user ID and password were being verified. Attempt to log in again."
I have tried everything I can think of on how to fix this and nothing is working. Any help would be appreciated. Thanks!
Can you log in as 'sa' on this computer? Can you log in as this user into GP on another computer? Can you log into GP as 'sa' and delete this user and recreate this user?
I can log on to the computer as "sa"and log in to GP as "sa" another computers but not this one.
OK, so you can log onto this computer as 'sa' but not as any other user? That mean we have a password hashing issue. What version of SQL on the server are you using? What version of the SQL client on the workstation are you using? Make sure the version of the SQL client matches what the SQL version on the server requires.
Hi, make sure you have same ODBC when you created password and when you want to login.
Example, when you created a password using odbc (computer name), you must using odbc (computer name) too to login. if you are using odbc (ip) to login, you will got an error.
I had this same issue but once I rebooted my computer it stopped.
Kurniawan Hiu is absolutely correct about this one. If you want to be 100% sure you can reset the user password using their GP client and the sa account. They will then be able to login to GP using that client but not others.
Hello, I know it is outdated topic, but I am having the same issue: one of my uses getting "Your attempt to log in to the server failed because an unknown error occurred when the user ID and password were being verified. Attempt to log in again." I do not getting it when people talking about IP vs naming convention. Any help will be appreciated. Thank you
Try going to All Programs > Microsoft SQL Server 2012 > Configuration Tools > SQL Server Configuration Manager >SQL Server services - and make sure they are running. I had this error last week and SQL Server Agent (MSSQLSERVER) was not running - the error went away after I restarted that. Hope this helps.
Thank you Diane. This is not a my case. All my users are running GP just fine except one machine. By machine I mean the same user can logon using her GP credentials on the other computer with no problem. I believe Kurniawan and Kirk is talking about using IP vs named server when you set up ODBC, but when you installing GP it will auto generate ODBC on the client machine. But I could be mistaken.
Got it working. Rebuilding DEX_LOCK and DEX_SESSION in tempdb did a trick. Thank you
Demi, when you have a user locked from a specific computer that is the first place to look. If there is no other reason, always ( in my case ) I have found that either or both of these tables is the cause ( root ) of the problem.
Thank you all.
I did followed all the steps and procedure that are mentioned in this article even then user is not able to login to GP 2016 from local machine whereas same credentials works in server. Is it required for GP 2016 client machine to be part of Domain.
Dynamics GP itself doesn't necessarily require a domain, since it uses SQL logins not Windows Authentication, so it can work in a workgroup environment as well.
Even if users were from a different domain than what Dynamics GP/SQL Server were installed on, it shouldn't matter as long as the ODBC DSNs are connecting to the SQL instance successfully on all machines, as that is what Dynamics GP is using to connect to the SQL instance.
Usually if we see a user can login to GP on one machine, but not on the other machine, the issue is a result of the ODBC DSNs on the different machines not being setup identically, as well as per KB 870416.
Business Applications communities