As of Friday, May 1st, 2020 the client configuration of GP2015 was as follows
|
Verified Date
|
GP Version
|
Version ID
|
CPY Version
|
Dexterity Version
|
|
3/3/2020
|
GP 2015
|
14.00.1230
|
14.00.1254
|
14.00.0085.000
|
So now according to Terry H’s posting
https://community.dynamics.com/gp/b/dynamicsgp/posts/the-2019-canadian-payroll-year-end-update-released
This is the version we were on :
Microsoft Dynamics GP 2015 (version 14.00.1230)
(Includes US 2019 Year-End Update, and all prior patches)
Canadian Payroll - 14.00.1240
Found in : MicrosoftDynamicsGP14- KB4533805-ENU.msp
To the best of my recollection this is what version I was on when I last checked on March 3rd, 2020 when we had to fix a problem with the Box 24 and 26 on the CRA Electronic file of the 2019 T4 documents.
The past Friday, May 1st, I started to do the update to GP (18.2.1036)
After downloading the code file to the server, backups completed and the current GP2015 code saved, I started the update to the latest version of GP. Only to have it fail after the installation stating that PROD 0 and PROD 7131 could not be updated from 14.00.1230 and 14.00.1254 respectively.
Well that confused me. I was sure I was following the path provided. But after two attempts I decided that maybe the best option was to update to GP2016 ( short hop along the way ) as it is a trusted and known migration.
So knowing that I need to be version and subversion smart I referenced back to Terry and decided that
Microsoft Dynamics GP 2016 (version 16.00.0814)
(Includes US 2019 Year-End Update, and all prior patches)
Canadian Payroll - 16.00.0822
Found in : MicrosoftDynamicsGP16- KB4533807-ENU.msp
was the best option to select. So, proceeded to download the GP2016 R2 RTM DVD from Microsoft site, then downloaded the Service Patch (see above) and installed GP2016 and expected to land at 16.00.0814 and 16.00.0822 – however and I did not know this at the time, I was not there – but hey why spoil the fun – keep reading.
Like all good consultants I make a backup after waiting 7 hours for 39 databases to update – at least we have a backup at GP2016 that works.
Now, push on to the GP2018 update. Code is already downloaded, as that was the first thing I did – now over 9 hours ago.
Reference back to Terry’s posting and I did the following verification as I was running the GP Utilities
Microsoft Dynamics GP (version 18.2.1036)
(Includes October release 18.2, US 2019 Year-End Update, and all prior patches)
Canadian Payroll - 18.2.1046
Found in : MicrosoftDynamicsGP18- KB4533809-ENU.msp
Now we are ready for the main event and the final 7 hours of computer cycle time to move to the final version.
Run GP Utilities – no number on the spash screen – so the right one is running.
The Validation screen runs to the end – almost and errors – read the duinstall error log and discover that PROD 6449 was not removed from the DynUtil.set file – it was from the GP2015 one 9.5 hours ago – so "sue me" I forgot.
Before proceeding I also purged the content of the DU000030 file in the DYNAMICS db per the conversation with Richard and Derek :
Error: Product 0 does not support upgrading from version 18.2.1036
( https://community.dynamics.com/gp/f/microsoft-dynamics-gp-forum/388097/error-product-0-does-not-support-upgrading-from-version-18-2-1036 )
Then I removed the PROD 6449 from DynUtil and start Utilities again – again the Validation screen runs, really slowly and this has me concerned. After 10 minutes the Validation screen fails and so I open the duinstall log file and find a message
PROD 7131 does not support upgrading from version 16.00.0836
Now hold on a minute and no I did not include a type-O - I should be on 16.00.0822
Back to GP2016 and I look to the version I downloaded and confirm that it should have landed me with 16.00.0822 – yup that is what I thought.
Open up the GP2016 client, open up Canadian Payroll – look at the Control window and there it is – 16.00.0836 – WT*(& ??
So, I look at the patch I downloaded, it says 16.00.0822 – So I think maybe I forgot the patch – so I re-apply the patch – same version. (PS for the keener here you know if failed)
Now I have been around long enough I know the next step is to uninstall GP2016 and the associated patch and start again this time install the right patch.
Hold on – problem – I have already updated the databases ( 39 of them ) and as we all know – you can not DOWNGRADE GP
So now my only option appears to be to restore the databases to GP2015 version as they were on Friday May 1st and start over again.
So before I do that I test my thought that the patch was wrong and removed the current client of GP2016 and installed fresh and made sure I only had the KB4533807 – did the installation and applied the patch – but I could not tell any difference, as the system opened, displayed the ABOUT with the expected version 16.00.0814 but no matter what I did I could only ever get it to show me CPY Version 16.00.0836
I also made sure to examine the posting from Beat B on https://community.dynamics.com/gp/f/microsoft-dynamics-gp-forum/382012/error-upgrading-from-gp-2015-14-00-1230-to-gp-18-00-0672-following-supported-upgrade-path
That is very good in discussing the topic – but did not solve my issue – thanks for the mail on weekend Beat, much apricated.
So, really long story, now what do I need.
REQUEST :
I need to know if there is a way to update from GP2015 14.00.1230 CPY 14.00.1254 directly to GP (18.2.xxxx) I have now wasted 15 plus hours and I can not bill any of it as it is not the clients challenge that the updates are not in sync – that is my challenge and partly Microsoft (right???)
If not, I have to update to GP2016 and before I do that I need to get my hands on the 16.00.0822 version of the patch – the one I have may or may not work – and I don’t have a test server and 9 more hours to learn if it works or not.
So, thanks for reading and thanks for your assistance.
