jaetex.blogg.se

1. #Acropro.msi adobe acrobat 8 professional install
2. #Acropro.msi adobe acrobat 8 professional Patch
3. #Acropro.msi adobe acrobat 8 professional license
4. #Acropro.msi adobe acrobat 8 professional windows

The file was actually in program files\Adobe\Acrobat 8.0\Acrobat\Settings, so I copied the files in this folder to the previous folder and clicked Retry and it completed the install.

#Acropro.msi adobe acrobat 8 professional install

I ran a test install and came up with a error 1308 when attempting to copy a file from CommonAppData\Adobe\Adobe PDF\Settings in the administrative install point. It now pulls files from the administrative install point instead of DATA1.CAB. Ok, I opened the acropro.msi using Orca (didn't see the option in Wise) and the options were not correct, so I toggled them and saved. Is there an overriding reason you decided not to use the Customization wizard and just do a str8 MSI installation? That does sound like a lot of work, much more than doing it in a supported way.more importantly, it doesn't sound real stable. Launching install directly using the ADOBE_SETUP=1 and UPGRADINGPRODUCTCODE=1 in the transform. This component condition can be deleted in this instance ie. This is usually found in the adobe transform file of any adobe product (even the sub msi calls from the innstall). This has prevented some components from installing and the product will fail to function. One more thing, we have noticed that if you bypass the setup.exe of any Adobe product you'll find that some of the components have a condition associated with them called Adobe. The updated versioning is usually stored in the exe which is identified when adobe product is launched. It sounds like a lot of work but once you get started it flows pretty easily. Just make sure you keep the updated system using a vm snapshot or backup, until you are sure your updated package is functioning. We have done 2 Adobe suites successfully this way.

#Acropro.msi adobe acrobat 8 professional license

We also make sure that the license files after the patches are added are also updated in the transform. All our packages use uncompressed additional files. There might be 30-70 files which are changed so we then integrate those files into our base transform and remove the older versioned files.

#Acropro.msi adobe acrobat 8 professional Patch

With all our Adobe products we have successfully added the upgrade patches by simply installing our customised install of whatever adobe product (customised being the operative word here) and simply doing a snapshot of the patch installs. MSI (s) (34:84) : Source for file 'MAGAZINE_Ad_2006_JPN.jobopti' is compressed MSI (s) (34:84) : File: C:\8.1.2\CommonAppData\Adobe\Adobe PDF\Extras\MAGAZINE Ad 2006 JPN.joboptions To be installed Won't patch No existing file MSI (s) (34:84) : Executing op: FileCopy(SourceName=MAGAZI~1.JOB|MAGAZINE Ad 2006 JPN.joboptions,SourceCabKey=MAGAZINE_Ad_2006_JPN.jobopti,DestName=MAGAZINE Ad 2006 JPN.joboptions,Attributes=16385,FileSize=20094,PerTick=32768,VerifyMedia=1,CheckCRC=0,InstallMode=58982400,) MSI (s) (34:84) : Executing op: SetSourceFolder(Folder=1\Common~1\Adobe\Adobe~2\Extras\|CommonAppData\Adobe\Adobe PDF\Extras\) MSI (s) (34:84) : Executing op: SetTargetFolder(Folder=C:\8.1.2\CommonAppData\Adobe\Adobe PDF\Extras\) I also downloaded the 8.1.2 patch file again, but same error. So, do I have a bad copy of DATA1.CAB? The file size is 472,011,998 bytes and is timestamped 6:02 AM. I also opened up DATA1.CAB and verified that the file is, in fact, not there. It does not appear to tell us much more than the actual error message.

#Acropro.msi adobe acrobat 8 professional windows

Windows Installer 3.0 is required to apply multiple patches.ĭo you have WI 2.0 or 3.0? If only 2.0, you can't specify multiple patches.īelow is the last several lines of the log file, just before it receives the error. Windows Installer 2.0: Multiple patches are not supported. If you follow the link for the PATCH property on that MS page is takes you here (VS.85).aspx where the crucial sentence, for the example you show, anyway, is " I've always used the /P switch to apply patches. I have never seen used, nor even been aware of, the PATCH property.

Why doesn't stuff just work like it should? This just goes to show that you really do learn something every day. I get the error "This patch package could not be opened." as if the patch file does not exist, even though it does exist.

The only problem is that it doesn't work. Msiexec /i AcroPro.msi PATCH=AcrobatUpd810_efgj_incr.msp AcrobatUpd811_all_incr.msp AcrobatUpd812_all_incr.msp TRANSFORMS=AcroPro.mst /qb Looking at the last example in the article at it would appear you could execute the below command to perform a new install and include all three patches. I am also struggling with the same problem as gmouse.