One of the most common errors we see, if not the most common, is the "Problem ascertaining version information" error message when launching Microsoft Dynamics GP Utilities to upgrade the application to a new version.

Using this information from a duinstall.log, we often see the following example:

Failure encountered ON 7/5/2016 at 10:08:40 AM. Error: Product 0 does not support upgrading from version 14.0.983.

Failure encountered ON 7/5/2016 at 10:08:40 AM. Error: Product 258 does not support upgrading from version 14.0.966.

Failure encountered ON 7/5/2016 at 10:08:40 AM. Error: Product 309 does not support upgrading from version 14.0.887.

Failure encountered ON 7/5/2016 at 10:08:40 AM. Error: Product 414 does not support upgrading from version 14.0.965.

Failure encountered ON 7/5/2016 at 10:08:40 AM. Error: Product 949 does not support upgrading from version 14.0.744.

Failure encountered ON 7/5/2016 at 10:08:40 AM. Error: Product 1493 does not support upgrading from version 14.0.782.

Failure encountered ON 7/5/2016 at 10:08:40 AM. Error: Product 3258 does not support upgrading from version 14.0.889.

 


Using this example duinstall.log information, this can mean one of the following causes of this version error:

1) The Microsoft Dynamics GP databases have records in the system tables, DB_Upgrade or DU000020, that are showing features/modules at a higher version than the Microsoft Dynamics GP code and dictionary files that are being used to launch Utilities against them.

    For example, we would get this type of error if the Microsoft Dynamics GP code that we're launching Utilities from is at version 14.00.0725 and the databases are showing a version of 14.00.0983 in the system tables, DB_Upgrade and DU000020.

    Because the databases are showing a higher version for Microsoft Dynamics GP than the code being used to launch Utilities from, it throws this type of error as we cannot 'downgrade' the databases for Microsoft Dynamics GP. If the code was at a higher version than the databases, Utilities would simply prompt to upgrade the databases.

    The resolution to this example would be to download and install the service pack or hotfix needed to get that installation of Microsoft Dynamics GP to be at the exact same version as the databases and system tables are showing, which would be 14.00.0983 for Microsoft Dynamics GP 2015 R2 in this example.

2) The other thing we see cause a duinstall.log version error when launching Dynamics GP Utilities to begin an upgrade is that our GP databases (DB_Upgrade and DU000020 tables) are showing too low a version/build to upgrade to the version of Microsoft Dynamics GP that we're launching Utilities for. This may be for only one database or multiple, but GP Utilities will look at all company databases in the DYNAMICS..SY01500 (Company Master) table, as well as the DYNAMICS system database to get the version information of each.

     For example, if we see this in the duinstall.log:

Failure encountered ON 4/25/2016 at 8:43:09 AM. Error: Product 0 does not support upgrading from version 12.0.2084.

     In this example, we're trying to upgrade to Microsoft Dynamics GP 2015 from Dynamics GP 2013 R2, but there isn't any direct upgrade path from this version to the new version.

     In this case, as per the 'Upgrading to Microsoft Dynamics GP 2015' hot topic, if we're on Dynamics GP 2013 at the 12.00.2084 version/build, we must be upgrading to version/build 14.00.0952 or higher for Dynamics GP 2015 R2.

     Most likely the resolution here is to run a service pack or hotfix for Dynamics GP 2015 R2 to be at or above the required 14.00.0952 version/build, in order to be able to upgrade from Microsoft Dynamics GP 2013 R2.

Hot Topics for upgrading Microsoft Dynamics GP are found here:

Upgrading to Microsoft Dynamics GP 2016

     --https://mbs.microsoft.com/customersource/northamerica/GP/support/hot-topics/HOT_TOPIC_MDGP2016Upgrade

     --https://mbs.microsoft.com/partnersource/northamerica/support/hot-topics/HOT_TOPIC_MDGP2016Upgrade

Upgrading to Microsoft Dynamics GP 2015

     --https://mbs.microsoft.com/customersource/northamerica/GP/support/hot-topics/HOT_TOPIC_MDGP2015Upgrade

     --https://mbs.microsoft.com/partnersource/northamerica/support/hot-topics/HOT_TOPIC_MDGP2015Upgrade

Upgrading to Microsoft Dynamics GP 2013

     --https://mbs.microsoft.com/customersource/northamerica/gp/support/HOT_TOPIC_MDGP2013Upgrade

     --https://mbs.microsoft.com/partnersource/northamerica/support/hot-topics/HOT_TOPIC_MDGP2013Upgrade

Upgrading to Microsoft Dynamics GP 2010

     --https://mbs.microsoft.com/customersource/northamerica/GP/support/hot-topics/hottopic_mdgp2010_update

     --https://mbs.microsoft.com/partnersource/northamerica/support/hot-topics/HOTTOPIC_MDGP2010_Update

Upgrading to Microsoft Dynamics GP 10

     --https://mbs.microsoft.com/customersource/northamerica/GP/support/hot-topics/Hot_Topic_UpdatingMicrosoftDynamicsGP10

     --https://mbs.microsoft.com/partnersource/northamerica/support/hot-topics/Hot_Topic_UpdatingMicrosoftDynamicsGP10


We've also seen this type of error message occur on client workstations and secondary machines when trying to  launch Microsoft Dynamics GP Utilities to complete an installation due to the company databases not having completed a prior upgrade and showing as such in the DB_Upgrade system table, but as far as upgrading Microsoft Dynamics GP goes, the above two causes make up the majority of support cases we see with this error message.

 

Hopefully, with the release of Microsoft Dynamics GP 2016 R2 around the corner and getting near that time of year where a lot of customers are upgrading their Microsoft Dynamics GP environment, this will help resolve any version errors being seen referring to the duinstall.log file. Good luck with all the Microsoft Dynamics GP Upgrades!!