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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / ODBC not setting up co...
Microsoft Dynamics GP (Archived)

ODBC not setting up correctly when installing GP2013 R2 on client

(0) ShareShare
ReportReport
Posted on by Community Member

Hi all,

I am currently upgrading one of my client's system from GP10 SP5 to GP2013 R2. So far the server and most of the clients have been upgraded/installed successfully. I am having problem with 1 client, where the installation runs successfully - no error message but I was unable to run GP Utilities. On checking further, it seemed like the ODBC was created for Dynamics GP2013 but on SQL Server Native Client. When I try to configure, I get error message that it is an invalid DSN and I am unable to delete or configure it. I found that the SQL server native client 10.0 driver was missing. I tried downloading the driver and installing but I am still not able to reconfigure the ODBC.

What am I missing here?

Thanks.

 

Regards,

Saras

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Community Member Profile Picture
    Community Member on at

    Hmm this is unusual. I assume you have verified that this user has the necessary rights to the Dex.ini file and any shared directories and you ran the install As Administrator.

    You can try uninstalling GP 10.0, Dexterity Shared Components 10.0, GP 2013 R2, Dexterity Shared Components 12.0, deleting everything in the Microsoft Dynamics program files folder, reboot the machine, then run the GP 2013 R2 Client Installation Package again. The client installation package, if you have created one, will reinstall SQL Server Native Client and configure it for GP 2013 R2.

    After this, if you can configure login for the DSN, I would put in the 'sa' credentials instead of SYSTEM. Sometimes that helps it connect.

  • Suggested answer
    Bill Campbell Profile Picture
    Bill Campbell 12 on at

    First question - what user ID are you using to do the installation?  Does the user have ADMIN rights?

    Second Question - did the workstation change? Note there are changes to ODBC from 64bit and 32bit machines and they look the same until you try to run GP against the 64bit version - it does not work - so even on a 64bit machine you need to configure ODBC in 32bit ODBC.  The correct file is found in the SYSWOW64 folder and is called ODBC32.exe

    Comments - I have seen cases where it is often better to 'not allow' the GP2013 installation to create the ODBC and to use the existing ODBC connection from the prior version.  When you launch the GP2013 Utilities what do you see in the ODBC selection box on the login screen?  Is it blank?  If not blank, is it named the same as the other users ODBC DSN file?

    If this helps, please be kind enough to mark as answer.

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

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans