Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics GP forum
Answered

PROD 7131 Does not Update

Posted on by 22,647

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.

  • Bill Campbell Profile Picture
    Bill Campbell 22,647 on at
    RE: PROD 7131 Does not Update

    Yes, the conversion completed successfully and encountered no errors.  Much thanks to your advice over the prep and execution of the migration.

  • Beat Bucher  GP Geek  GPUG All Star Profile Picture
    Beat Bucher GP Gee... 28,021 Moderator on at
    RE: PROD 7131 Does not Update

    Good morning Bill,

    Did you managed to get your 2016 all upgraded ?

    What about the parallel upgrade I mentioned in my previous reply ? when having that many companies to upgrade, it can save you some time to run the upgrade from 2-4 different GP clients..

  • Bill Campbell Profile Picture
    Bill Campbell 22,647 on at
    RE: PROD 7131 Does not Update

    Once again, Beat you are spot on - after my message I dug deeper into the GP2016 update and did find the patch reference you gave.

    I am in the middle of the 7 hour update to GP2016 16.00.0836

    From there we are going to sit and wait for the client to get a new SQL Server - update SQL to SQL2019 and then use that to move to GP (18.x.xxxx) and recover some of my sanity as well.

    Thanks. for all your assistance.

  • Suggested answer
    Beat Bucher  GP Geek  GPUG All Star Profile Picture
    Beat Bucher GP Gee... 28,021 Moderator on at
    RE: PROD 7131 Does not Update

    I don't remember where this KB4536492 came from.. but the Microsoft Service pack list (Excel) has KB4536494 as the latest CPR R2 listed from 1/5/2020..

    I can send you that one if you can't find it ..

    The KB4536496 you're talking about is the 18.2.1036 upgrade.. don't install that one !

    PS: KB4536492 is the CPR YE 2019/2020 R2 fix for GP 2015 released on 1/15/2020. It bring GP 2015 to 14.0.1230.

    PPS: this might help too: https://community.dynamics.com/gp/b/dynamicsgp/posts/microsoft-dynamics-gp-year-end-update-2019-canadian-payroll

    And this is the full GP 2015 MSP versions list : https://mbs.microsoft.com/Files/customer/GP/Downloads/ServicePacks/MDGP2015_MSPVersionlist.xlsx

    And GP 2016: https://mbs.microsoft.com/Files/customer/GP/Downloads/ServicePacks/MDGP2016_MSPVersionlist.xlsx

  • Bill Campbell Profile Picture
    Bill Campbell 22,647 on at
    RE: PROD 7131 Does not Update

    I think you are right - GP2016 is what I will aim for tonight - no sense trying to push over to much.  I will get there and be happy for a while - then a new server will be the reason for the next push.

    Again, thanks.  Now I go to sleep for 3 hours and get back here to be at it tonight.

  • Bill Campbell Profile Picture
    Bill Campbell 22,647 on at
    RE: PROD 7131 Does not Update

    Beat, sorry but I can not find KB4536492 - When I search 18.2.1036 / 18.02.1058 that comes up with KB4536496 from mbs.microsoft.com/.../cagptuye2018

    Trust me - you did more to get me to this than you might know - I was about to work on a way to manually move table data from the 16 version to the 15 for those 3 companies.  That would have been days and money I did not have to spend.

    Thanks - I will suggest we include you on the "Pub Crawl - Fargo 2021" in honour of Derek and the Tech Support - but we need to include the MVP's Beat and Richard for all the assistance.

  • Beat Bucher  GP Geek  GPUG All Star Profile Picture
    Beat Bucher GP Gee... 28,021 Moderator on at
    RE: PROD 7131 Does not Update

    Bill,

    I feel that you're running out of time here..  Get them updated to 16.0.0814/0836 and let them run this version for a few weeks. If it takes a whole 7-8 hrs to get 1 upgrade applied, you're not going to make it to 18.2.1036.

    Have you thought about splitting the upgrade ? running parallel from 2-3 different GP clients ?

    Once you've that stable running GP2016, I'd run another TEST upgrade to jump to 18.2.1036 and make sure everything is aligned right.

  • Bill Campbell Profile Picture
    Bill Campbell 22,647 on at
    RE: PROD 7131 Does not Update

    I feel like I am banging my head on the wall - but I need to be sure - I have one night - tonight - to make this happen and I can not make a mistake.

    So, from what I am reading here - Beat you are saying that from the current GP2015 - 14.00.1230 - CPY 14.00.1254 and 3 companies at 16.00.0814 - CPY 16.00.0836

    That I can update to GP ( 18.2.1036 - CPY 18.02.1058 ) all in one step???  Or would you bring everyone to GP2016 16.00.0814 / 0836 and leave it there for now?

    Last one, promise - have to start update prep soon to get the 7 or 8 hours of computer proceessing time in tonight.

    Thanks

  • Verified answer
    Beat Bucher  GP Geek  GPUG All Star Profile Picture
    Beat Bucher GP Gee... 28,021 Moderator on at
    RE: PROD 7131 Does not Update

    Gotcha,

    That CPY build 16.0.0841 has actually 3 different CPY builds, depending on release date:

    16.0.0800 (US YE 2019), 16.0.0822 (CPR YE 2019) or 16.0.0836 (CPR YE R2 2020)

    you'll have no other choice than upgrading those other companies to the same build before going to 18.2.1036, which is KB4536492 CPR R2 1/9/2020  18.02.1058 (CPY)

  • Bill Campbell Profile Picture
    Bill Campbell 22,647 on at
    RE: PROD 7131 Does not Update

    Beat, the challenge here is that all 36 companies are on GP2015 only these three on GP2016

    So, now only choice is to move to GP2016 and make all of them match.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Anton Venter – Community Spotlight

Kudos to our October Community Star of the month!

Announcing Our 2024 Season 2 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Dynamics 365 Community Newsletter - September 2024

Check out the latest community news

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 290,537 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 228,520 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,148

Leaderboard

Product updates

Dynamics 365 release plans