Copy link to clipboard
Copied
I am trying to patch my existing admin install point of Adobe Reader 9.1.1 to 9.1.2 but get this error:
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 yoru computer and that you have the correct upgrade patch.
I get the same error on my PC when I double click the msp file
This is the msi log from when I tried to patch the existing admin install of 9.1.1:
MSI (c) (00:58) [16:18:02:876]: Final Patch Application Order:
MSI (c) (00:58) [16:18:02:876]: Other Patches:
MSI (c) (00:58) [16:18:02:876]: Unknown\Absent: {AC76BA86-7AD7-0000-2550-7A8C40000912} - C:\CustomInstalls\AdobeReader\patches\adobe912.msp
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 an
d that you have the correct upgrade patch.
C:\CustomInstalls\AdobeReader\acroread.msi
MSI (c) (00:58) [16:18:02:876]: Product: Adobe Reader 9.1.1 - Update '{AC76BA86-7AD7-0000-2550-7A8C40000912}' could not be installed. Error code 1642. Additional information is available in the log file c:\adobe.log.
MSI (c) (00:58) [16:18:02:923]: Product: Adobe Reader 9.1.1 -- Installation failed.
Any help is greatly appreciated.
Copy link to clipboard
Copied
There was a previous post about inserting some registry keys using Adobe Customization Wizard.
It's not just Adobe Reader. Acrobat Professional has the same quirks when attempting to install via GPO.
Rob Landon, A, Net & MCP
PC Support Specialist
Clipper Magazine
Copy link to clipboard
Copied
Guys, there's a solution posted on http://kb2.adobe.com/cps/498/cpsid_49880.html
Copy link to clipboard
Copied
I'm not sure that’s a solution or not. It really explains well why it is happening.
I'm going to try scripting this:
Workaound for User installations, which were deployed from an AIP containing a Security update as the last update applied
In order to successfully deploy a Quarterly update onto these User systems, the Msiexec.exe "v" option must be added to the commandline. An example syntax is as follows:
msiexec /i <path of msi on AIP> REINSTALL=ALL REINSTALLMODE=vomus
Using the above command line with the option "vomus" present will cause the MSI to run from the source AIP and re-cache the User's local MSI for future changes or repair. This is the most trustworthy method for deploying updates of this nature.
And then patch to 9.1.2. Still a royal pain though.
Rob Landon
PC Support Specialist
Clipper Magazine
Copy link to clipboard
Copied
Am I the only person who reads a lot of Corporate BS coming off this adobe KB article.
"The patch types are different"...yeh I get that
"Different patch types can't be applied together"...ok, a little off but...
"Note, Attempting to create an AIP using the last configuration shown above will fail. The failure, however, serves to prevent a usage of updates which is not recommended by Adobe"...WHAT! this just douns like an excuse to broken patching, be it 9.1.1 or 9.1.2
Don't release the patch as an incremental unless it actually is. Unless they changed it *runs off to check* WHICH THEY HAVEN'T!
"NOTE: This update can be applied either to Adobe Reader version 9.1 or to version 9.1.1"
then this is a cop out.
Either way, i got mine sorted out but no less angry with Adobe for this shoddy patching cycle.
Copy link to clipboard
Copied
It does make you wonder why they would need to differentiate their patches, so you do have to wade through some BS.
The script mentioned: msiexec /i REINSTALL=ALL REINSTALLMODE=vomus
Only recaches the installation. I believe the user has to run the msp file.
At this point I'm just going to rebuild my AIP to match what adobe says is the best practice.
Rob Landon, A, Net & MCP
PC Support Specialist
Clipper Magazine
Copy link to clipboard
Copied
Has anyone heard of any plans by Adobe to release the msp file in a form that works properly? As mentioned earlier, I'm not sure how well these fixes are going to work for remote machines.
Copy link to clipboard
Copied
Not sure if you guys need this anymore but here was my fix.
went through motions of installing AdbeRdr910_en_US.exe. before the installation starts i took five adobe files out of the %userprofile%/local settings/application data/adobe/setup files directory and placed them in a folder called adobe912 on C:.
place 9.1.1 and 9.1.2 in C:\adobe912 directory as well.
in CLI typed the following.
msiexec /a C:\adobe912\AcroRead.msi /p C:\adobe912\AdeRdrUpd911_all_incr.msp;C:\adobe912\AdeRdrUpd912_all_incr.msp
although I could not verify if 9.1.1 actually installed, i am assuming it did since i received 0 errors. If anyone could verify it for me that would be terrific.
Good Luck and I hope this helps.
Copy link to clipboard
Copied
I'm going to try your solution today.
rasczak wrote:
Not sure if you guys need this anymore but here was my fix.
went through motions of installing AdbeRdr910_en_US.exe. before the installation starts i took five adobe files out of the %userprofile%/local settings/application data/adobe/setup files directory and placed them in a folder called adobe912 on C:.
place 9.1.1 and 9.1.2 in C:\adobe912 directory as well.
in CLI typed the following.
msiexec /a C:\adobe912\AcroRead.msi /p C:\adobe912\AdeRdrUpd911_all_incr.msp;C:\adobe912\AdeRdrUpd912_all_incr.msp
although I could not verify if 9.1.1 actually installed, i am assuming it did since i received 0 errors. If anyone could verify it for me that would be terrific.
Good Luck and I hope this helps.
Has anyone tried this:
http://www.microsoft.com/technet/scriptcenter/scripts/sus/server/default.mspx?mfr=true
This is not the first time an msp file from adobe has made things difficult. I am thinking of changing my strategy in the future.
Copy link to clipboard
Copied
rob,
I didn't need to go through WSUS (WSUS is a pain although that's another site and forum altogether ) Once I completed the referenced steps, I added the msi package to a GPO un computer settings > software installation. I refreshed the policy and restarted the computers. During the reboot adobe started to install. Worked flawlessly.
Good luck with that.
Joe
Copy link to clipboard
Copied
Good Info.
Copy link to clipboard
Copied
Thanks. I've had to do so many updates to Acrobat I was just hoping to find a different way to handle the updates without reworking the admin install point.
Rob Landon, A, Net & MCP
PC Support Specialist
Clipper Magazine
Copy link to clipboard
Copied
Disregard, my post is in regards to invalid serial number on Pro/Standard after 9.1.2 to existing admin point. Wrong forum.
Copy link to clipboard
Copied
I don't even know why I continue to use adobe products. Adobe software development is a joke. So are their UIs.
First, this forum crashed my FireFox 3.0.10 browser, twice. The second time, I figured out it was Adobe's fault. Why doesn't Adobe learn to script AJAX properly so it doesn't crash browsers? So here I am in IE8 typing a reply.
All of you guys were beating around the bush in regards to the "solution" to this problem. I have found a way to apply the patch and use an MST generated by the Adobe Customization Wizard. Granted, it would be much better if Adobe would just generate their patches correctly to begin with.
As you all have found out, you cannot create an MST using the ACW (Adobe Customization Wizard) and then use the following command
msiexec /i AcroRead.msi /p AdbeRdrUpd912_all_incr.msp /t
This will cause the aforementioned problem. Below is the proper sequence of events:
At this point, you should have an MSI and MST. If you want, you can use ORCA to merge the MST into the MSI. If you're using Setup.exe, you're going to have to change th Setup.ini file.
To test that everything works, you can copy the files to a test directory and perform the following command: msiexec /a <AdobeReader.msi> [/t <Your_transform.mst>]
Replace with the name of your MSI file and optionally, pass in your transform (definitely do this if you made a separate MST!). If all goes well, the installation should go well, too. During sequencing, you will still get an MSI installer error (actually, 2), number 1406, about not being able to write to two registry keys. These were the registry keys we added in the steps above. This does not happen on normal installatons.
Please also note that I don't know whether the roaming user profile problem menioned in http://kb2.adobe.com/cps/404/kb404597.html is fixed in version 9.1.2. It was not fixed as of 9.1.0.163. This is all posted AS-IS. YMMV.
UPDATE:
In case you don't know, I will share a bit of enlightenment I had with my procedure above. This specifically relates to application virtualization and sequencing Adobe Reader for MS App-V.
In step 4, I had you install Adobe Reader on a clean machine and obtain some registry information because otherwise, the installation may not be successful for virtualization. These steps are unneccessary. Here's why: you cannot "patch/upgrade" vitualized applications within the application itself. To patch/upgrade a virtual application, you have to use (in the case of MS App-V) the Application Virtualization Sequencing MMC to load the virtualized app, then run the upgrade/patch so that MS App-V can detect the changes and properly update the package. So what does this mean? Two things. First, whenever I use the ACW, under the Online and Acrobat.com Features section I always uncheck <b>Disable all updates</b>. However, checking this does not necessarily mean Adobe Reader does not install the Adobe Update Manager (AUM); in fact, it does install AUM, which is the feature that contains the component that attempts to write those registry entries and therefore, which is causing the error.
Therefore, the solution (and what should be step 4) is to disable the installation of AUM. Now some have posted at various sites how to disable the installation of AUM by deleting a whole bunch of stuff in the MSI. This is not necessary. The steps are outlined in the new step 4 above. This should resolve sequencing issues.
UPDATE 10 July 2009 12:00:00 EST (GMT-05:00) - Pertains to virtualizing Adobe Reader only.
This doesn't work for virtualizing the application. When importing the application into MS App-V Server Management Console, the application version is still 9.1.0.163 even though the splash screen says 9.1.2. I think that my assessment is correct because of two reasons: 1) I still got the MS VC++ Runtime error when using a normal user with a roaming profile which Adobe said the latest 9.1.1 release fixed (and hence 9.1.2) (the AppData folder included) and for which Adobe's solution is a joke; 2) When I installed my "patched" Reader (as a normal install) with AUM and proceeded to go to Help->Check for Updates, the 9.1.2 update appeared in the list of updates (again, even though the splash screen said it was version 9.1.2). Adobe has got to get their patchng correct!!!
For application virtualization, I'm going to recommend that you sequence the 9.1.0 version through to completion. Then, save the sequence and close it. Then re-open the sequence project for upgrade and applythe 9.1.2 patch. Whether you can use an ACW transform on the 9.1.0 installation and then patch, that's debatable. I sure hope so. If not, perhaps there's a way I can fudge it, namely, create an MST via ACW. Then, manually create an MST with the pertinent settings via ORCA and see if that works, instead.
Having said all that, I seriously doubt this works at all even for GPSI deployment. Sorry all. Will post again when I finally get this application to sequence. Hopefully, the same principles will apply to GPSI deployment.
Message was edited by: TTEConline on 10 July 2009 12:00:00 EST (GMT-05:00)
Copy link to clipboard
Copied
TTECOnline - thanks for post #37 which got me going in the right direction. Blogged here:
http://blogs.mcbsys.com/mark/post/Patching-Adobe-Reader.aspx
Mark
Copy link to clipboard
Copied
Well I added this registry key in the customization wizard to fix the viewing in browser problem i was having and it worked
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\SOFTWARE\Adobe\Acrobat\Exe]
@="\"C:\\Program Files\\Adobe\\Reader 9.0\\Reader\\AcroRd32.exe\""
Ran the transform again and re-ran the adminstrative install. I applied the 9.1.2 patch to the administrative install and I think it Finnaly is working so I can distributie it to the rest of the organization.
So when is the next security vulnerability going to be out so I can do this all over again..................................