Skip to main content
This topic has been closed for replies.

4 replies

T
Test Screen Name
Legend
March 23, 2018

No, the MSP will be going to the Windiows Installer database to find an installed package with a particular ID. WIndows patches aren't just a list of files to copy, they are a detailed reference to an earlier package, and what to change in it. But systems for deploying software sometimes bypass Windows Installer and just copy files. Fixing this would be very difficult indeed, except by reference to the original install package. You might usefully ask what provision they made for updates? Maybe they expect to apply the latest update and push it again, this is common practice.

T
Test Screen Name
Legend
March 23, 2018

They may have made a modified packaging of Acrobat. Probably best to refer this to them, because what you did sounds perfect for an I modified install.

    timh30140974
    timh30140974Author
    Participating Frequently
    March 23, 2018

    OK, thank you.  I sent my last question before I saw your response. 

    T
    Test Screen Name
    Legend
    March 23, 2018

    That should be the product stream to which this patch applies. What can you tell us about its previous history (original installation, further updates etc.)?

      timh30140974
      timh30140974Author
      Participating Frequently
      March 23, 2018

      The original installation was installed September of last year.  It was an install package created by our software packaging team. It have not been updated since it was installed.

      timh30140974
      timh30140974Author
      Participating Frequently
      March 23, 2018

      Could it be that the msp is looking for the default installation path and our package did not use the default path?  I have reached out to the person who did the original installation to find the install path used.  If it is different from the default installation path how do I point the msp to the path used by our install package?

      T
      Test Screen Name
      Legend
      March 23, 2018

      It should be like all the other updates. What particular difficulty do you face?

      timh30140974
      timh30140974Author
      Participating Frequently
      March 23, 2018

      I am running Adobe Acrobat Pro 2017 version 2017.011.30059.  I downloaded  version 17.011.30078 from here: 17.011.30078 Planned update, February 13, 2018 — Release Notes for Acrobat DC Products.  When I right click the .msp file and select "Apply" I get a message stating: "The upgrade patch cannot be installed by the Windows installer service because the program to be upgraded may be missing or the upgrade patch may update a different version of the program.  Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch."  I also tried version 17.011.30068, but received the same error.

      timh30140974
      timh30140974Author
      Participating Frequently
      March 23, 2018

      The screenshot below shows the exact version I am running.  Does the 17.011.30078 update in the link I previously posted apply to this version, or is there a different update I need to download?

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices