New April Hotfix and more changes for VAT
Check out the latest updates to Microsoft Dynamics GP 2016 and 2018.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
A frequent error seen when attempting to install Microsoft Dynamics GP, install a new feature to an existing Microsoft Dynamics GP environment, or run an upgrade of an existing Microsoft Dynamics GP environment, is the following error in Utilities:
From this message, we go into the 'Data' folder located within our Microsoft Dynamics GP directory (i.e. C:\Program Files (x86)\Microsoft Dynamics\GP####\Data) and find the duinstall.log referenced in the error message. Looking at the duisntall.log, it shows something like this example at the end of the log file:
"Product 0 does not support upgrading from version 16.0.716"
"Product 1045 does not support from version 11.0.1234"
These type of version error messages, when we see them, usually means that one of two things is happening to cause the error or both:
1. If doing an install of a new feature to an existing Microsoft Dynamics GP environment, there is remnants of a prior install of that feature, and it is at a version to low to install/upgrade to your current version/build of Microsoft Dynamics GP.
2. If doing an upgrade of Microsoft Dynamics GP, these types of errors are indicative of either not being at a high enough version/build on your current Microsoft Dynamics GP environment to upgrade to the version/build of Microsoft Dynamics GP that you're attempting to upgrade to and/or you're not upgrading to a high enough version/build of Microsoft Dynamics GP based on the current version/build of Microsoft Dynamics GP that you're starting from.
For the upgrade version errors, it is important to look at the 'Upgrading to Microsoft Dynamics GP ####' hot topics on PartnerSource or CustomerSource, that we have for all versions of Microsoft Dynamics GP, so you can verify that you're currently on a required version/build of Microsoft Dynamics GP that can upgrade directly to the version of Dynamics GP that you're looking to upgrade to, and what the minimum version/build of Microsoft Dynamics GP is that you must be upgrading to, based on your current version/build.
For the install version errors, we usually have a couple different options, depending on the version error.
For example, let's say I'm getting the "Product 1045 does not support from version 11.0.1234" version error when attempting to install the Revenue/Expense Deferrals feature for Microsoft Dynamics GP 2016.
In this example, because there is no direct upgrade path from Microsoft Dynamics GP 2010 (11.0.xxxx) to Microsoft Dynamics GP 2016, I wouldn't have the option of upgrading this feature, so the only option we would have is to re-initialize this feature via the system tables, so that instead of attempting to upgrade this feature, GP Utilities would install it like a brand, new feature, thus getting past the version error.
**NOTE: If the client had just upgraded from Microsoft Dynamics GP 2010 to Dynamics GP 2013 and then to Dynamics GP 2016, then they would have the other option of restoring back to Dynamics GP 2013 in order to upgrade this Revenue/Expense Deferrals feature from Dynamics GP 2010 to Dynamics GP 2013, so they could then upgrade it to Dynamics GP 2016 successfully.
To re-initialize a feature so that GP Utilities will install it at the current version that you're launching GP Utilities from, we would use these steps and scripts:
A. First, we would need to remove the feature from the system tables, using these script examples:
1. Delete DB_Upgrade where PRODID = 1045
2. Delete DU000020 where PRODID = 1045
3. Delete DU000030 where PRODID = 1045
B. Next, along with removing the feature records from the three system tables, we would also need to remove that feature's sub-feature tables, which is what Dynamics GP Utilities also looks at to determine whether a feature has been installed or not, when it doesn't find the records in the system tables, but the feature is mentioned installed (existing in the Dynamics.set and DynUtils.set files).
The list of sub-feature tables are as follows and I'll also attach the New SubFeature Guide.docx, so you can download that as well to have readily available as needed. Some features have sub-feature tables in the system database and company databases, but some only have them in the company databases:
Tables checked in DYNAMICS database
Tables checked in COMPANY database
SUSPREF HR2APP06 AAX10130
Revenue Expense Deferrals
CN90000 CN04000 CN00100
CB200011 CB100003 CB100000
ME142820 (new table)
SY90200 (where PRODID = 1493) DU000020 (where PRODID = 1493)
Cash Flow Management
HRM Solutions Series
APR000020 (where PRODID = 1911
Payment Document Management
Business Activity Statement
Purchase Order Enhancements
Control Account Management
Enhanced Commitment Management
SY90200 (where PRODID = 3104) DU000020 (where PRODID = 3104)
Payroll Integration to Payable
APR000020 (where PRODID = 4522
PIP40100 and APR_PIP40100
Advanced Go Tos
APR000020 (where PRODID = 4933
Employee Health and Wellness
APR000020 (where PRODID = 4955
Dynamics Online Services
Date Effective Tax Rates
Direct Debits and Refunds
Using the sub-feature table information above, in our example with the Revenue/Expense Deferrals feature (product 1045), there isn't any tables I would need to drop from the Dynamics GP system database, but I do need to drop the PP000001 table from all company databases that exist. (You can use the SY01500 system table for a list of company databases you need to drop the tables from.)
***NOTE: This re-initialization process can also be done on a per company database basis as well, by adding a 'where db_name = 'xxxx'' clause to the DB_Upgrade table, a 'where companyID = #' clause to the DU000020 and DU000030 scripts, and only dropping the sub-feature table(s) from that specific company database, not the system or any other company databases.
Once the product 1045 records have been removed from the DB_Upgrade, DU000020 and DU000030 tables, as well as the PP000001table dropped from all GP company databases, I would then be able to launch Microsoft Dynamics GP Utilities with Revenue/Expense Deferrals installed (i.e. present in the .set files) and install this feature anew at the current version/build of the GP application.
***NOTE: When the re-initialization of a feature is performed, all SQL objects in the databases are dropped and re-created for that feature, which means the tables are also dropped and re-created, so when deciding whether or not to perform this process, you'll want to make sure that the feature was never used or there isn't any data for the feature that needs to be kept in Dynamics GP before moving forward with this process.
We've seen this type of error enough so that we wanted to put this information out where it's easy to find, as we've had bits and pieces of this information in other documents and pages, but not so much by itself where it can be bookmarked and kept for future usage. Hopefully this will help when you run into these type of version errors. Thanks.
This is very useful information as it happens quite often that a client upgrade fails due to an old module reference, no longer existing.. In a case I came across, the Date Effective Tax Rate (6831) module was installed in GP 2010.. Upgrade was done all the way thru 2018, but the DETR module isn't available from the installer anymore in GP setup.. so how do you get the dictionaries into the .SET files ??
Business Applications communities