Good Morning Community!

Every time you launch Microsoft Dynamics GP Utilities a version check is run.  This is how Utilities knows that you’ve applied a service pack/hotfix/compliance update or new version of Microsoft Dynamics GP and that the databases need to be upgraded.  Utilities will use the Dynutils.set file to figure out which products you have installed and where the DU*.DIC files are located.  It then compares the versions listed in the DYNAMICS database with the dictionary versions to make sure that they match.  It even goes a step further and checks several different tables for the module in the company databases to make sure the version matches.

If the versions of the dictionaries do not match the versions found in the databases, Utilities assumes an upgrade needs to be run.  It verifies that you are on a supported upgrade path and then kicks off the upgrade.  If Utilities finds any kind of problem during this process it will throw a version check error.

“There was a problem ascertaining product version information.  Microsoft Dynamics GP Utilities will now exit.  Please check the duinstall.log file for more information.”

You will find the duinstall.log file in the \Data folder of your GP code folder.  This is typically found at C:\Program Files(x86)\Microsoft Dynamics\GP2016\Data (C:\Program Files on 32-bit operating systems).  You can find various errors in here which will give you a pretty good idea of why you are running into a problem.  Some examples are:

Error:  Product 0 does not support upgrading from version 11.0.####
Error: You are attempting to configure an older version of product 0.  Database 14.0.#### Code 12.0.####

The duinstall.log will usually have several of the above errors listed over and over again.  This is because it is giving you an error for each product ID in each company it is checking against.  You could have a lot of errors at the end of the duinstall.log file.  I will go over some of the most common reasons you will run into these errors below and the steps you can take to resolve them.

Old Company Data

One of the most common problems we see is also the easiest to resolve.  If you have data from an old company in the DYNAMICS database you may run into errors when attempting to upgrade.  This problem will usually manifest itself as a bunch of errors in the duinstall.log file showing old versions of modules you use.  You can download the Clear Companies.sql script from the following link to clean this up.  If you have not already previously run this script it should be your first step in troubleshooting this error. (Note – This script will remove data for any companies that exist in DYNAMICS. but do not have a corresponding company database in SQL). **Make a backup of the DYNAMICS database prior to running the script.**

Clear Companies.sql

Unsupported Upgrade Path

Another common problem is that you are simply not upgrading along a supported upgrade path.  We have every supported upgrade path for Microsoft Dynamics GP 2016 listed at the following site: GP 2016 Upgrade Hot Topic

You should already be very familiar with this site if you are performing an upgrade since we list all of the known upgrade problems that you may run into.  Make sure that you are taking note of the version listed in both the ‘Updating From’ column as well as the ‘Patch Requirement…’ column.  You can’t upgrade from the RTM version of GP 2015 to the RTM version of GP 2016 for example.  The far right column of this table also contains links to each GP versions respective KB download page so that you can upgrade as needed.

Specific Product\Module Version Issue

Error:  Product 309 does not support upgrading from version ##.#.####
Let’s say that you are getting an error in the duinstall.log file indicating that Product 309 does not support upgrading from its current version.  It can be any product or even multiple product ID’s but I’m using 309 for this example.  You look in the Dynamics.set file and find that Product 309 is Fixed assets.  The main question here is whether or not this module is actually used in this GP environment.  If it is not a module that is being used then you should uninstall it using ‘Control Panel’ > ‘Programs and Features’ (add\remove programs) so that it is removed from the .set files.  Then you can launch Utilities again and it shouldn’t attempt to upgrade that product.

If it is a module that you are using or you would like to begin using you will need to open a support case. 

If you are still running into problems after checking on the above common problems you can also open a support case.

Continue to check back with our Microsoft Dynamics GP 2016 Upgrade Blog Series Schedule to learn more about the Microsoft Dynamics GP 2016 Upgrade!