Skip to main content
T
TonyHeslington
Participating Frequently
October 17, 2017
Question

Creative Cloud Packager & SCCM - Acrobat DC - Package install starts but quits.

  • October 17, 2017
  • 2 replies
  • 4952 views

Hello,

I have the task of packaging Adobe CC applications in my environment.

W10 64bit - v1606

SCCM - v1606

Adobe Acrobat Reader 2015 - Normally on machines by the time a CC user comes along.

All other packages have been created and installed successfully.

The Adobe DC application is proving to be challenging.

I have repeated the packing process twice with the same result.

The Job via SCCM completes.  (Exit code 0) however no icons for the product show up.

I manually run the .MSI package and it attempts the install only getting so far... suddenly the install progress indicator goes backward and quits.


Any idea what is going on?


Thank you,Tony H.

This topic has been closed for replies.

2 replies

L
licensingm39260983
Participant
October 19, 2017

i have the exact same problem.  Can't seem to find an answer anywhere.  I guess my only solution is to try and bundle Acrobat DC alongside some of the other packages and hope that it works.

pensionc16073137
pensionc16073137
Participant
October 19, 2017

I have the exact same problem.

I've narrowed it down to the Visual Studio 2013 C++ redistributable that Adobe is expecting.

I'm running Windows 10, and it auto installs version 12.0.406....

However Adobe doesn't recognise this as being installed and is prompting for an "ok" or "cancel" to continue installing.

You can't install the run bundled with Acrobat, as it's an older version.

So we're stuck being unable to deploy the application as it's expecting a response so throws an error.

S
Adobe Employee
Steve Cordero
Adobe Employee
October 19, 2017

penishonc16073137 - Can you provide the verbose MSI logs for the installation that show this behavior to the Forum?

S
Adobe Employee
Steve Cordero
Adobe Employee
October 18, 2017

You will want to get a verbose installation log.  Here is the Microsoft KB on enabling this Windows Installer feature.

https://support.microsoft.com/en-us/help/223300/how-to-enable-windows-installer-logging

After you have the log, then you can look at the error(s) that may be causing the installation problem.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices