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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Bypassing SQL Version ...
Finance | Project Operations, Human Resources, ...
Suggested Answer

Bypassing SQL Version Errors from Dynamics GP Utilities

(1) ShareShare
ReportReport
Posted on by CindyFromIndy 34
Hi David!
 
It's been a long time.  I hope you are thriving!
 
I'm pretty tired trying to log into GPO Utilities after a 5-hop update for a client. So I was excited to see what I perceived as a solution.  However it didn't work for me.
 
The error we're getting
 
 
I tried all of the below, but the none of them worked.  What am I missing?
duForceSQL188Detection=TRUE
duForceSQL180Detection=TRUE
duForceSQL170Detection=TRUE
duForceSQL110Detection=TRUE
 
Thanks in advance for your consideration!
Categories:
Microsoft Dynamics GP
I have the same question (0)
  • Suggested answer
    Lisa at AonC.com Profile Picture
    Lisa at AonC.com 1,111 Super User 2026 Season 1 on at
    I don't recognize all the versions in your list.

    Here's the critical blog post from David Musgrave:

    How to bypass SQL Version Errors from Dynamics GP Utilities | Winthrop Development Consultants Blog

    These are the options he shows:
     
    duForceSQL70Detection=TRUE
    duForceSQL80Detection=TRUE
    duForceSQL90Detection=TRUE
    duForceSQL100Detection=TRUE
    duForceSQL110Detection=TRUE

    [For example, I'm working on a GP 2016 > GP 18.8 upgrade and I used the last one.]
  • Suggested answer
    David Musgrave MVP GPUG All Star Legend Moderator Profile Picture
    David Musgrave MVP ... 14,143 Most Valuable Professional on at
    As Lisa mentions my article provides all the details you need, however, there is a potential bug in the Dynamics Utilities which I have reported to Microsoft support.
     
    You will probably need to use duForceSQL110Detection=TRUE (which is the current Dex.ini setting for any GP version from GP 2015 (v14.0) or later).  Make sure the setting is added to the dex.ini file in the Data folder and is in the [General] section.
     
    Looking at the Dynamics Utilities source code, I think that it will only identify SQL versions 11.0 to 16.0 at this stage so you will need to use the dex.ini override setting for SQL 17.0 or later.
     
    I have updated my article to mention the issue with SQL 17.0.
     
     
    Good luck 
     
    David
  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 304,688 Super User 2026 Season 1 on at
    Added the Dynamics GP category to this question.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

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

#1
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 622

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 553 Super User 2026 Season 1

#3
CP04-islander Profile Picture

CP04-islander 430

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP
License usage reporting (in-app and PPAC) with Entra dynamic groups

Product updates

Dynamics 365 release plans