Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1 Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
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 TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Please suggest a fix or alternative route to fix this problem, if possible. I'm installing the Dynamics GP 2016 Client software on a user's laptop and for some reason it is not installing its ODBC Connector properly during Setup. It keeps throwing me this error: (This is occurring on a Windows 7 Pro x64 bit edition OS) Many thanks in advance!
I've not run into this before. What happens if you manually try to create the 32-bit ODBC on this machine named Dynamics GP 2016?
As an aside, I love your profile picture :)
This is one of the reasons I never have the ODBC created automatically. :-) Once in a while it does something crazy.
Add me to the likes for that profile picture!
I will try this and let you know my results, thanks!! --Mark
P.S.: Yes, I ran across that picture and thought it was fitting! :D
Ok, I manually added the ODBC connector of type "SQL Server Native Client 11.0" to the User DSN and now I can see that 'ServerName' and select it, however when I attempt to logon to it thru GP Utilities for the first time setup, I get this new error:
Make sure that you have setup a 32bit ODBC driver and not the 64bit ODBC driver
Just my two cents - but you stated User DNS - I have always been installing the ODBC in the SYSTEM DSN
Not sure it makes a difference - but I have to say I have never tried it from anywhere else.
Make sure you are using a driver for your exact SQL version. I just had a similar problem with a 11.00.3XXX version of the driver which required manually updating it to version 11.00.6XXX.
Sorry for the Xs. I can't recall the exact build numbers.
This problem turned out to be a corrupt C:\Windows\SysWOW64\ODBCCP32.DLL file in relation to the ODBC Connector with the laptop's OS. I had never seen this happen before now! Thanks for the assistance!!
Wow - in all my years of installing GP, I've never seen that. Thanks for letting us know what it was!
An ODBC connection is like the 'address and driving directions' for the application on your local computer to know how to get to the data on your SQL server UPSers.
Business Applications communities