yersterday, Adobe published AcrobatUpd1010.msp.
Today we wanted to update our AIP (10.0.3), but wrong package is noticed (although package should be cummulative)
So we´'ve updated major package 10.0.0 -> AIP update process finished successfully.
But rollout via GPO has crashed. Manual installation shows error 1334 "...acrord32.dll...not found in data1.cab...".
We've changed AIP-sourcefiles, but no success.
I have verified that Acrobat 10.1 installation is happening properly using both GPO and manual installation from 10.1 AIP. I cannot see a crash through GPO or 1334 error when doing manual installation through AIP.
Can you pls. list out OS and language you are seeing this on. I would also like you to check once the steps with which you are creating AIP for 10.1
First you need to create an AIP using 10.0 and then patching it with 10.1 msp Following are the steps: 1. msiexec /a <path of AcroPro.msi for 10.0> TARGETDIR <path where you want to create AIP> 2. cd to the AIP folder 3. msiexec /a <AcroPro.msi> /p <path of .msp file (AcrobatUpd1010.msp)>
First you need to create an AIP using 10.0 and then patching it with 10.1 msp
Following are the steps:
1. msiexec /a <path of AcroPro.msi for 10.0> TARGETDIR <path where you want to create AIP>
2. cd to the AIP folder
3. msiexec /a <AcroPro.msi> /p <path of .msp file (AcrobatUpd1010.msp)>
This should create an AIP for 10.1 and this can be used for push through GPO.
As described in another forum, Acrobat 10.1 update is a cummulative update and will not patch up any earlier 10.0.x AIPs correctly. So the correct way is to patch the 10.0 AIP with 10.1 only.
Thanks for all answers.
Resolution: AIP for 10.0.0 was not uncompressed by msiexec /a...
This was not recogniced immediatly, because patching with .msp-file has worked successfully.
Now everything works fine.
Let me clarify, if it is not uncompressed using msiexec /a, it is not called an AIP. If you are only using the 10.0 installer as it is without using the msiexec /a option, then you are not creating an AIP. In that case, it is just an installer copied on the network share for users. Patching this with subsequent .msp will give abnormal behaviours.
Please see the following links for details: