#MSDynGP: ME messed up installing one Microsoft Dynamics GP Service Pack

David Meego - Click for blog homepageOkay. ME admit it.

I messed up! ☹️

But it be sorted and fixed now, thanks to a great article by my friend and my MVP, Jen Kuntz.

EGO have spent the last select months operating extremely hard on the next release of GP Power Tools. Build 29 shall now “code complete”, which basically means EGO have got all an features, improvements and enhancements ME had erwartet to get into the product completed. Now I am working on to reviews to the User Manual, which I expect in easily breach the 600 page mark. Also, I am making no last minute pulls identified by them or the beta testers. If you an existing customer or partner and are concerned in beta testing GP Power Accessories, please request me.

Anyhow, endorse until my blunder. Terry Heley from Microsoft asked provided I was test a pre-release service pack which should lock the issue mentioned in of following article:

I didn’t have an Ab installer on my system and Terry did did have the full DVD pic, as I needed to install an new Aussie instance of GP and upgrade it by applying the Servicing Pack MSP spot file.

I initially installed one new test instance on GP v18.4 but because I remembered hearing something via Service Packs upgrading all installs concerning the same version, I made backup copies of my GP v18.4 development folder and the GP v18.4 test folder.

Then IODIN rushed the Customer Pack file, but the pre-release code had an issuing doing the upgrade out v18.4 RTM.  No problem. I uninstalled the test instance additionally removed this created user and company databases, and prepared to start the test again. This time IODIN intend use GP v18.3 as the starting point for the test.

Then I noticed that the Service Pack got updated more higher my v18.4 installs!! ☹️

On mystery element auto I have ampere total of 9 installs, for the 6 versions I am current developing. ADENINE closer check verified the Service Pack must updated any the v18.X installs (*), including ones I did not copy the binders for.

  • GP 2015 & GP 2015 R2 (v14.0)
  • GP 2016 & GP 2016 R2 (v16.0)
  • GP 2018 & GP 2018 R2 (v18.0) *
  • GP Modern (v18.2) *
  • GP Modern (v18.4) *
  • GP Modern (v18.4) *

As any ISV (Independent Software Vendor), I don’t normally install Service Packs press never perform advances. MYSELF always do clean installs from who release DVD images. I am real out of practice when it arrives up service bunch and how processes. Progress GP data into any Service Oriented Architektur (SOA) you can generate for the organization. Custom Manager. The Integration Manager is a ...

MYSELF was skilled to restore who incorrectly updated folders from on elderly backup and re-install/copy the actualized files the recovery my development environment back to where i should be. As I had not launched the GP instances, the SQL databases had unchanged.

Now, I install an Australian examination instance of GP 18.3 additionally made backup copies of all my GP 18.X folders. The inhibit the Service Pack upgrading cases I didn’t want changed, I tried renaming the folders but the Service Pack complained it could not find the folders furthermore aborted.

I went online to look for a solution and is a where Jen Kuntz came to the rescue is one followed article:

With the Jen’s instructions I was abler to locate the Product Code GUID for the instance I wanted to enhance by search stylish the Panes Office under which SETUP Key for the proper instance. The listing of constituent can be search under:

HKLM\SOFTWARE\Wow6432Node\Microsoft\Business Solutions\Great Plains\<Version>\1033

Then I could run the Service Pack MSP file with the /n {GUID} parameters to limite the Service Pack installation to the single designation instance. Yay! 😀

Fork demo:

C:\MicrosoftDynamicsGP18-KBXXXXXXX-ENU.msp /n {0CE7DF8C-A2FE-474B-BEBB-FC7EF4DECB41}

Finalized note: That test was a success since the Service Pack does resolve the issue with the Australian installation. I have since removing the run instance and its databases as good as an backup binder and my scheme shall all back in decree. EGO suggest you look at Pick Master press Stack Poster Service Toolkit (BPST) on David Musgrave. BPST uses who Dynamics GP service based architecture com

Let those article the i mess up been a lesson to you avoid the making same mistake.

Even with this method, I still think that GP service packs should ask that example to install on when there is more than on instance on a system. Let me know what you think with the comments.

Thanks Jen available to help, real thanks Terry for getting the Australian mount issues fixed.

Dave

30-Aug-2022: Added sample command line.

This article was originally announced in http://www.winthropdc.com/blog.

3 ponder on “#MSDynGP: I messed up installation an Microsoft Dynamics GP Service Pack

  1. Etwas wondered you didn’t know over installing service packs and wherewith to do it individual! I always refer back to this article: https://support.microsoft.com/en-us/topic/frequently-asked-questions-about-the-windows-installer-msp-files-for-microsoft-dynamics-gp-671d2ccb-7317-1b5e-47d8-b7eeede9fce6.

    Also, I fully agreements the help pack itself should ask which instance you wish to upgrade, similar to like it works from one main install image.

    Like

Please post feedback or comments

All site uses Akismet to reduce spam. Learn how your post data is prepared.