Application startup loop Acrobat Pro 11.0.11

[Kheleth]

Hi.

I am building a package to deploy Acrobat 11.0.0 with an .msi and .mst file.

After that I install 11.0.11 .msp file.

All seems to go fine, but when I try to start up Acrobat, it starts up acrobat.exe and Pdapp.exe then immediately crashes them, starts them up again, crashes again etc.

Anyone have an idea what is going on?

[EnterpriseHelp]

Try to narrow down the issue.

1. Install the vanilla 11.0 and see if there's a problem.
2. If not, on a clean machine install 11.0 plus the update and see if there's a problem.

Now you know whether the mst, chaining method, or cmd line you used with the mst is the issue.

pdapp is associated with licensing.

Ben

[Kheleth]

The problem is that I can't recreate the problem manually, it only comes when doing silent install from SCCM.

I ran the same installations steps manually, then it worked fine:

Execute-MSI -Action Install -Path "$dirFiles\Adobe_Acrobat_11.0.0_MUI.msi" -Transform "$dirFiles\Adobe_Acrobat_11.0.0_MUI.mst"

Copy-Item -Path "$dirFiles\Adobe_Acrobat_11.0.0_MUI" -Destination "C:\Program Files (x86)\Adobe\Acrobat 11.0\Setup Files\{AC76BA86-1033-FFFF-BA7E-000000000006}\" -Force

Execute-MSI -Action Patch -Path "$dirFiles\AcrobatUpd11011.msp"

I'm thinking that maybe I need to put a pause before it installs the .msp package, maybe it needs a little time before the 11.0.0 is actually finishing some abckground process or something.

The problem doesn't arise when I only apply the update from SCCM, i.e to clients that already have acrobat 11.0.10 installed since before, the problem only comes for complete installlations...

[Kheleth]

Solved the problem.

I had to put in a pause step between the base installation and the update installation, probably some background process hadn't finished before trying to apply the update.