Solved

updating adobe reader .msi with .msp file

Posted on 2011-03-17
12
3,791 Views
Last Modified: 2013-11-14
I just recently started work at a new organization and I am trying to update an adobe
reader x 10.0.0. .msi file with  the 10.0.01 adobe reader x .msp update that was released for it.
I put the .msp file in the same directory that the .msi file was in.  I then went to a command line
and ran:

msiexec /a <msi directory and file> /p <msp file and directory>  

I get an error that says No valid sequence could be found for the set of patches.

I looked up the error and reviewed this article:

http://support.microsoft.com/kb/913754

According to the chart, the registry keys for c_867 and c_868 are missing, so I added them but the files
also were not present in the System32 directory.  I took a look at some of the other servers in our environment
as well as some workstations and they do not have them either.  Are these files even necessary?

At the end of the day, I'm just trying to get this .msi updated so I can redeploy this package.  Reader
10.0.0 seems pretty bad, the Finance department is less than happy with the issues they are having with it.
If anyone can help I would really appreciate it!

Thank you in advance
0
Comment
Question by:ameravi75
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 5
12 Comments
 
LVL 40

Expert Comment

by:Vadim Rapp
ID: 35158345
Did you make administrative installation before you applied the patch?

The installation of Reader has been traditionally so bad in so many ways that we simply repackage each one to fully compliant MSI. So then, for example, extension .pdf becomes advertised and thus reader can be installed or upgraded on demand (adobe forcibly removes that because for them it's more important to offer the choice of handling .pdf by Acrobat or by Reader to those few who have both).
0
 

Author Comment

by:ameravi75
ID: 35158386
No, I simply took the .msi file which had already been made, and tried to apply the .msp directly to it.  
0
 
LVL 40

Expert Comment

by:Vadim Rapp
ID: 35158425
You can only apply patch to administrative installation.

http://msdn.microsoft.com/en-us/library/aa367988%28v=vs.85%29.aspx , option /p:

"To apply a patch to an installed administrative image you must combine the following options:
/p <PatchPackage>[;patchPackage2…] /a <Package>"
0
MIM Survival Guide for Service Desk Managers

Major incidents can send mastered service desk processes into disorder. Systems and tools produce the data needed to resolve these incidents, but your challenge is getting that information to the right people fast. Check out the Survival Guide and begin bringing order to chaos.

 

Author Comment

by:ameravi75
ID: 35158949
Is the [patchPackage2...] required or is that optional if you have a second package.  Just tried to add it again and logged, still got the sequence error:


=== Verbose logging started: 3/17/2011  13:52:21  Build type: SHIP UNICODE 3.01.4000.4042  Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (F0:94) [13:52:21:822]: Resetting cached policy values
MSI (c) (F0:94) [13:52:21:822]: Machine policy value 'Debug' is 0
MSI (c) (F0:94) [13:52:21:822]: ******* RunEngine:
           ******* Product: e:\intranet\is\software\adobereaderx1\AdbeRdr1000_en_US.msi
           ******* Action: ADMIN
           ******* CommandLine: **********
MSI (c) (F0:94) [13:52:21:885]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (F0:94) [13:52:22:916]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'e:\intranet\is\software\adobereaderx1\AdbeRdr1000_en_US.msi' against software restriction policy
MSI (c) (F0:94) [13:52:22:916]: SOFTWARE RESTRICTION POLICY: e:\intranet\is\software\adobereaderx1\AdbeRdr1000_en_US.msi has a digital signature
MSI (c) (F0:94) [13:52:22:916]: SOFTWARE RESTRICTION POLICY: e:\intranet\is\software\adobereaderx1\AdbeRdr1000_en_US.msi is permitted to run at the 'unrestricted' authorization level.
MSI (c) (F0:94) [13:52:22:994]: Cloaking enabled.
MSI (c) (F0:94) [13:52:22:994]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (F0:94) [13:52:23:010]: End dialog not enabled
MSI (c) (F0:94) [13:52:23:010]: Original package ==> e:\intranet\is\software\adobereaderx1\AdbeRdr1000_en_US.msi
MSI (c) (F0:94) [13:52:23:010]: Package we're running from ==> C:\DOCUME~1\Andrew\LOCALS~1\Temp\1\c1d2c8b1.msi
MSI (c) (F0:94) [13:52:23:010]: APPCOMPAT: looking for appcompat database entry with ProductCode '{AC76BA86-7AD7-1033-7B44-AA0000000001}'.
MSI (c) (F0:94) [13:52:23:010]: APPCOMPAT: no matching ProductCode found in database.
MSI (c) (F0:94) [13:52:23:010]: MSCOREE not loaded loading copy from system32
MSI (c) (F0:94) [13:52:23:025]: Machine policy value 'TransformsSecure' is 1
MSI (c) (F0:94) [13:52:23:400]: Original patch ==> e:\intranet\is\software\adobereaderx1\Adobe_10.0.0.1.msp
MSI (c) (F0:94) [13:52:23:400]: Patch we're running from ==> C:\DOCUME~1\Andrew\LOCALS~1\Temp\1\c1d2c8b2.msp
MSI (c) (F0:94) [13:52:23:416]: SOFTWARE RESTRICTION POLICY: Verifying patch --> 'e:\intranet\is\software\adobereaderx1\Adobe_10.0.0.1.msp' against software restriction policy
MSI (c) (F0:94) [13:52:23:416]: SOFTWARE RESTRICTION POLICY: e:\intranet\is\software\adobereaderx1\Adobe_10.0.0.1.msp has a digital signature
MSI (c) (F0:94) [13:52:23:416]: SOFTWARE RESTRICTION POLICY: e:\intranet\is\software\adobereaderx1\Adobe_10.0.0.1.msp is permitted to run at the 'unrestricted' authorization level.
MSI (c) (F0:94) [13:52:23:416]: SequencePatches starts. Product code: {AC76BA86-7AD7-1033-7B44-AA0000000001}, Product version: 10.0.0, Upgrade code: {A6EADE66-0000-0000-484E-7E8A45000000}, Product language 1033
MSI (c) (F0:94) [13:52:23:416]: Note: 1: 2263 2: SummaryInformation 3: -2147024882
MSI (c) (F0:94) [13:52:23:416]: PATCH SEQUENCER ERROR: failed to open summary info from storage for TGT_2ToUPG_2 transform in e:\intranet\is\software\adobereaderx1\Adobe_10.0.0.1.msp patch! (1: 2263 2: SummaryInformation 3: -2147024882 )
MSI (c) (F0:94) [13:52:23:416]: SequencePatches returns error 1648.
No valid sequence could be found for the set of patches.
e:\intranet\is\software\adobereaderx1\AdbeRdr1000_en_US.msi
MSI (c) (F0:94) [13:52:23:416]: Product: Adobe Reader X - Update '{45466C95-4890-4681-9B84-B790C8373C71}' could not be installed. Error code 1648. Additional information is available in the log file e:\intranet\is\Software\AdobeReaderx1\log1.txt.

MSI (c) (F0:94) [13:52:23:416]: Note: 1: 1708
MSI (c) (F0:94) [13:52:23:416]: Note: 1: 2729
MSI (c) (F0:94) [13:52:23:416]: Note: 1: 2729
MSI (c) (F0:94) [13:52:23:416]: Product: Adobe Reader X -- Installation failed.

MSI (c) (F0:94) [13:52:23:416]: Attempting to delete file C:\DOCUME~1\Andrew\LOCALS~1\Temp\1\c1d2c8b2.msp
MSI (c) (F0:94) [13:52:24:025]: MainEngineThread is returning 1648
=== Verbose logging stopped: 3/17/2011  13:52:24 ===
0
 
LVL 40

Accepted Solution

by:
Vadim Rapp earned 500 total points
ID: 35159124
Optional. First, you create administrative installation from 10.0.0:

msiexec /a "AdbeRdr1000_en_US.msi" targetdir=c:\areader10

Now you have AdbeRdr1000_en_US.msi under c:\areader10

Then you apply the patch
msiexec /p AdbeRdrUpd1001_Tier1.msp /a c:\areader10\AdbeRdr1000_en_US.msi

By the way, the patch should be named exactly like above, with tier. Where did you get yours? or have you renamed the patch?

Finally, you can simply extract the msi from AdbeRdr1001_en_US.exe
0
 
LVL 40

Expert Comment

by:Vadim Rapp
ID: 35159130
correction: "Finally, you can simply extract the msi from AdbeRdr1001_en_US.exe" - no, scratch that, it's the same 10.0.0  in fact.
0
 

Author Comment

by:ameravi75
ID: 35159403
I followed your lead, created administrative installation from the 10.0.0 MSI, in step two I still get the sequence error.  I have the log file attached.  It looks like there may be a problem with the actual .msp file.  

Also, why would you go ahead and extract the .exe after adding the patch to the msi, wouldn't you deploy the .msi that you already just updated?
adobe-log.txt
0
 
LVL 40

Expert Comment

by:Vadim Rapp
ID: 35159464
> It looks like there may be a problem with the actual .msp file.  

Probably. Where did you get it?  I actually tried it all and it all works. Main msi from ftp://ftp.adobe.com/pub/adobe/reader/win/10.x/10.0.0/en_US/ and update tier 1 from ftp://ftp.adobe.com/pub/adobe/reader/win/10.x/10.0.1/misc/

> why would you go ahead and extract the .exe after

I said exactly the opposite: not exe from msi, but msi from exe. Adobe has AdbeRdr1001_en_US.exe so I thought inside there would be AdbeRdr1001_en_US.msi accordingly. But in fact inside there's the same 10.0.0 .
0
 

Author Comment

by:ameravi75
ID: 35162019
Thanks for sticking around and helping me out.  It must have been a bad msp file initially because after I downloaded the files again from your links it did work fine.  At least the two steps of creating the administrative msi, and then updating it.   I am somewhat unclear on your last step, of finalizing the .msi so I can re-deploy the software via group policy and update clients.    

Thanks!  Andrew
0
 
LVL 40

Expert Comment

by:Vadim Rapp
ID: 35162124
> I am somewhat unclear on your last step, of finalizing the .msi so I can re-deploy the software via group policy and update clients.    

Actually, my last step was updating administrative installation with the patch.

To upgrade clients, assign the msi and specify that it upgrades the previous one. Feel free to ask for more clarification if you need.

With my repackaged MSI, I don't need to assign it. Since extension .pdf is advertised, I only publish the package, so the upgrade kicks in on demand when the user next time opens pdf file. You can read my article "Assigning packages without assignment" if interested.
0
 
LVL 40

Expert Comment

by:Vadim Rapp
ID: 35162129
clarification:

specify that it upgrades the previous one - meaning, the previous version of Reader, probably 9.
0
 

Author Comment

by:ameravi75
ID: 35164335
In this case, Reader 10.0.0 was already assigned to clients through GPO before I got there, so I will try to re-deploy the package with the updated MSI.  Thanks alot for all the help and the link to the article, I will definitely check that out.  Hopefully I will close out this question and accept a solution sometime this morning,
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article outlines the process to identify and resolve account lockout in an Active Directory environment.
This article shows the method of using the Resultant Set of Policy Tool to locate Group Policy that applies a particular setting.
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …
This video shows how to use Hyena, from SystemTools Software, to update 100 user accounts from an external text file. View in 1080p for best video quality.

751 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question