How to bypass SQL Version Errors from Dynamics GP Utilities

Have you ever had to do an upgrade of Microsoft Dynamics GP and the SQL Server has already been upgraded to the latest and greatest, but now when you attempt one of the upgrade steps, you get a SQL Version error for Dynamics Utilities.

The wording of the error message is along these lines:

Your current SQL Server is not a supported version.

Req: Microsoft SQL Server 11.0
Act :Microsoft SQL Server 20XX (RTM) – XX.0.XXXX.XXX

You need to upgrade to SQL Server 11.0 before continuing.

The actual window will look something like this example:

This often happens during upgrades where intermediate steps are required or when trying to create a new company after the server has already been upgraded.

Solution

DISCLAIMER: The method below is not officially supported as it was designed for testing purposes only, but has worked perfectly for the consultants who have used it.

There is a Dex.ini Setting which can be used to override the SQL Server Version check and so get past this window.

The Dex.ini Setting does vary depending on the version of Microsoft Dynamics GP, but it is fairly easy to work out which setting is needed.

Where the screen lists the required version, take that number and remove the decimal point.

For example: Req: Microsoft SQL Server 11.0 gives 110

Use this number in the setting duForceSQLXXXDetection where XXX is the number.

So here are some examples:

• GP 2015 (v14.0) onwards wants duForceSQL110Detection=TRUE
• GP 2013 (v12.0) wants duForceSQL100Detection=TRUE
• GP 2010 (v11.0) wants duForceSQL90Detection=TRUE
• GP v10.0 wants duForceSQL80Detection=TRUE
• GP v9.0 wants duForceSQL70Detection=TRUE

Don’t use the above list as a hard and fast guide as the required versions might have changed with service packs or R2 releases. Best to use the version number from the window to adjust the Dex.ini setting as required

Here are some technical details from the DynUtils.dic source:

The value for the Dex.ini setting is stored as a form level constant:

• • FORCE_DETECT_SQLXXX of form duSQLInstall

It is checked from the form level function:

• • verifyServerVersion() of form duSQLInstall

Which in turn is called from the form procedure:

• • init of form duSQLInstall

If the version is mismatched, the following script displays the error:

• • displayBadServerVersion of form duSQLInstall

Thanks to Larry Ressler and Beat Bucher for encouraging me to research this issue further.

Hope you find this information useful.

David

This article was originally posted on http://www.winthropdc.com/blog.