In fact I deployed the latest DC update using this method and had no problems.
I'm not sure what has changed - this is the same method I've been using for a long time now to deploy and install Adobe Reader updates and have never seen this problem. A bit of research has told me that msiexec error code 1636 means that the update file cannot be opened. The logs basically reflect the same thing - the install fails with error code 1636. Simple System Center environment - one admin server, one database server, only one site and one distribution point. Fails with Message ID 10006, Description 1636ĥ. Command line: msiexec /p “AdbeRdrUpd11019.msp” /qĤ. Pushing the update out using a package in System Center fails 100%ģ. "Manually" running it via the command line worksģ. However the last Adobe 11 update that was released (11.0.19) is failing out consistently. Generally I thought I had the system down and have been seeing some good results. That seemed off to me.Īny help at all would be appreciated since it is critical that we apply this security patch ASAP to all of our machines here that have Acrobat Pro 9.3.4 installed on them.I've been deploying Adobe Reader updates to my company for over a year now. The media I have been building off of since version 9.0 and the way through 9.3.4 is not a retail version but a volume version.
"User has entered a volume serial number in a retail build. One thing very odd was just before the error line above in the log file there was another line that stated:
I also went and checked my Software License Certificate from Adobe and it was the correct serial #. It doesnt necessarily mean that the code was corrupt in. I checked the mst file just to be sure that it was the correct serial # although it hadn't changed and it was. Runtime Code U44M2P7 happens when Adobe Photoshop fails or crashes whilst its running, hence its name. "Product: Adobe Acrobat 9 Pro - 1118xxx (my volume serial #) error." I looked at the log file that I had created with the msiexec command and it gave the error: However, when I ran it on a test PC (that didn't have Acrobat Pro installed on it) using the msiexec command in a command window it failed. I was able to get the patch to install on my AIP directory. I then tried to apply it to version 9.3.3. Verify that the program to be upgraded exists on your computer and that have the correct upgrade patch." "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. I have not been able to successfully apply the patch either to my version 9.3.4 AIP folder nor trying to just execute the msp file manually on a PC that has Acrobat Pro 9.3.4 installed. It stated on the web site that this patch could be applied to either version 9.3.3 or 9.3.4 If you are importing the Lenovo Catalog to SCUP for synchronization with SCCM, I would suggest you post over in the Enterprise Management Forum. This forum is specifically for the Lenovo Patch product. Today I downloaded (twice just to make sure that there wasn't a problem with the download after I was having problems) the 9.4 patch from the website Re:Failed to install update (s) '0X80246002' & '0x80091007'. Launch the installer and follow the prompts to set up the Creative Cloud app. I am running Windows XP SP3 and all applicable Microsoft patches have been applied. Find CreativeCloudInstaller.dmg in the Chrome download section (bottom of the browser), or find it where you save your downloads. I am using a volume license and had successfully already deployed version 9.3.4 via either Group Policy or using the msiexec command at the command line.