You’re offline. This is a read only version of the page.
Announcements
385
Dear All,
As I have upgraded successfully with the help of community GP 2015 RTM to GP 2016 R2. It is all working fine on server but once I installed GP 2016 R2 at client machine
It occur product version error:
Failure encountered ON 27/05/2020 at 12:46:56 PM. Error: Product 309 does not support upgrading from version 14.0.524.
Failure encountered ON 27/05/2020 at 12:46:57 PM. Error: Product 309 does not support upgrading from version 14.0.524.
Failure encountered ON 27/05/2020 at 12:46:57 PM. Error: Product 309 does not support upgrading from version 14.0.524.
Failure encountered ON 27/05/2020 at 12:46:57 PM. Error: Product 309 does not support upgrading from version 14.0.524.
Failure encountered ON 27/05/2020 at 12:46:57 PM. Error: Product 309 does not support upgrading from version 14.0.524.
Any help would be appreciated.
Thanks
Thank you Derek,
That worked! After dropping the 2 tables CPY30250 & CPY40205, and clearing DB_Upgrade from the 7131 entry, since there were no records in CPY10100 table, the GPU ran the company upgrade as expected and installed the CPY module in full.
The initial problem came from the fact that the 1st attempt of installing the CPY module created all the tables, but then failed to complete due to the module version which was too low for the current GP core version..
I'm going to document the whole process for future references :-)
First, don't remove anything from DU000010, as we should never need to do so.
When you removed PRODID 7131 for Canadian Payroll from DB_Upgrade, DU000020 and DU000030, but had it installed, thus showing in the .set files when you launched Utilities, it then looked for CPY40205 and CPY30250 in any of the company databases for GP.
If it finds the CPY40205 table, it then looks for the PSupervisor column in CPY10100.
If it finds this column in CPY10100, along with CPY40205 table, it'll write a record into DB_Upgrade for PRODID 7131 and a version of 8.0.0.
If only the CPY40205 but not this column in CPY10100, then it gives a version of 7.50.0 for PRODID 7131.
If it doesn't find the CPY40205 table at all, it deems Canadian Payroll as not having been installed.
So, along with removing PRODID 7131 from the three system tables, you'd also have to drop CPY40205 and CPY30250 from every company database mentioned in the SY01500 table so that, when you launched GP Utilities again with CANPAY installed, it'd install that module anew at the version you're currently at, not attempt to upgrade it.
To upgrade to 18.2.xxxx from GP 2018, you need to be on a minimum of 18.0.0496, which at that build, Canadian Payroll would be at 18.0.0489.
If you were on 18.0.0628, Canadian Payroll would also be at that same build, 18.0.0628, so the "Product 7131 does not support upgrading from version 18.0.628" version error is interesting, as it should be at a valid version enough to upgrade to 18.2.xxxx.
Thanks
I'm trying to add the CPY (7131) on my existing 18.2.1036 US setup.. Since you can't select the module 7131 CPY from the control panel after the setup was done in a non-CA country, I threw the chunk file CANPAY.cnk into the GP folder and started GP.. When running GP Utilities, it complains about not being able to upgrade module 7131:
First I realized that the CANPAY.cnk was of an outdated version 18.0.0376 (I believe), so it would make sense that the upgrade wouldn't work. I then extracted the chunk file from the YE Tax update CAN, which is build 18.2.1058 and copied it into the GP folder..
GPU would complain again :
Failure encountered ON 5/28/2020 at 10:56:52 AM. Error: Product 7131 does not support upgrading from version 18.0.628.
I then wiped out all referenced entries in DU000010, DU000020, DU000030 & DB_Upgrade about 7131, and ran GPU again.. this time it was a much lower version complain:
Failure encountered ON 5/28/2020 at 12:17:08 PM. Error: Product 7131 does not support upgrading from version 8.0.0.
I made a backup of the DU000010 entries for 7131 and can put them back, as it looks like the upgrade path is missing some versions within that table apparently..
I know about the only supported way from MS to add CPY to UPR in an existing GP instance (US) is to setup another GP instance, which I find a little silly.. as many companies are facing this problematic after proceeding with acquisitions and merger. Most time it's the other way around, having a CAN setup that needs to add UPR, which is much easier, but in some cases it's a US company that needs to add a Canadian branch and wants to use Payroll too.
Thank you Derek!
This paper will prove to be very useful, as I've run into this problem more than once :-)
I knew how to deal with the DUxxxx & DB_Upgrade tables, but not the sub-feature tables in the system & company DB's.
This is greatly appreciated.
So, Collections Mgmt, Extender, SmartList Builder and Advanced Go Tos all were taken over by a ISV / third party whether eOne, Partner Advantage, etc.
EFT for RM became a part of the core 'Microsoft Dynamics GP' module beginning in GP 2010.
Dynamics Online Services doesn't exist after GP 2016 and cannot be used anyway, because the functionality behind the scenes was depreciated a couple years ago.
Which leaves PDM, Encumbrance Mgmt and Grant Management, which it looks like they had installed at GP 10.0, but then never installed nor upgraded them after that.
If they wanted to begin using those modules at the new 18.2 version, they could re-initialize them as per this blog:
Thanks
Derek,
a client upgraded from GP2010 to 2018R2 and several months later called for a refresh of a TEST company.
However, I noticed in the DB_Upgrade table that several modules are completely outdated and though they think they use it, it doesn't seem those were upgrade.. I don't have direct access to the system, but was surprised by that content:
db_name PRODID db_verMajor db_verMinor db_verBuild Product
| DYNAMICS | 1157 | 10 | 0 | 18 | Collections Management |
| DYNAMICS | 1472 | 10 | 0 | 1061 | EFT for Receivables Management |
| DYNAMICS | 2150 | 10 | 0 | 1193 | Payment Document Management |
| DYNAMICS | 3107 | 10 | 0 | 51 | Extender |
| DYNAMICS | 3258 | 9 | 0 | 116 | Encumbrance Management |
| DYNAMICS | 3830 | 10 | 0 | 78 | SmartList Builder |
| DYNAMICS | 4421 | 10 | 0 | 1169 | Grant Management |
| DYNAMICS | 4612 | 10 | 0 | 6 | Advanced Go Tos |
| DYNAMICS | 6499 | 14 | 0 | 698 | Dynamics Online Services |
The system version is 18.2.1036 for module 0.
I f you could paste the contents of the DYNAMICS.SET file on the server and the one on the workstation into this thread we could tell you for sure what is the issue.
No, we only get duinstall.log errors if we run into something like the GP client/code is at a lower version than the databases are already showing, or as in the example here where it looks like Fixed Assets is on too low a version/build to upgrade to the current GP version they are on, such as if they've upgraded to GP 18.2 already but Fixed Assets is still showing at GP 2015 (14.0) and there isn't a valid, direct upgrade path between the two versions, we'll get duinstall.log errors as mentioned above.
If the database was returning a version of 0.0.0 for Fixed Assets/309, and the client version/dictionary for Fixed Assets where we're launching Utilities from showed 14.00.xxxx, it would simply prompt you to launch GP Utilities in order to upgrade the databases, it wouldn't throw a version error.
Now, it is possible to get a GP_ErrorLog error if the databases show one version and the GP code/dictionary file shows another, but that is again usually if the database version is already higher than that of the GP code/dictionary file for that feature/module.
Thanks
Derek, agree with your comments - but would the duinstall log file not contain a message that the Database version is ( ZERO ) while the client version is 14.0.524?
Or does that only happen when you have it installed and created on the server and there is a mismatch at the client?
Don't remembers for sure.
#1
André Arnaud de Cal...
291,359
Super User 2024 Season 2
#2
Martin Dráb
230,370
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
